Bitcoin Forum
December 09, 2016, 09:21:40 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 [490] 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2033777 times)
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
July 24, 2014, 11:15:17 PM
 #9781

Hey guys.... Curious,
As I am sure we are all seeing,
the hash rate keeps going up and down like a yo-yo.

My question, does this effect our block chances?

Is it bad , good , or indifferent?


I don't think the hash rate is varying *that* much.

There's no way, to my knowledge, that p2pool can know what the true hashrate is.  It has to guess.  It guesses by how quickly shares of a given size are being submitted.  Since that's going to vary by luck, the hashrate going to look like a yo-yo on speed.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
1481318500
Hero Member
*
Offline Offline

Posts: 1481318500

View Profile Personal Message (Offline)

Ignore
1481318500
Reply with quote  #2

1481318500
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481318500
Hero Member
*
Offline Offline

Posts: 1481318500

View Profile Personal Message (Offline)

Ignore
1481318500
Reply with quote  #2

1481318500
Report to moderator
1481318500
Hero Member
*
Offline Offline

Posts: 1481318500

View Profile Personal Message (Offline)

Ignore
1481318500
Reply with quote  #2

1481318500
Report to moderator
SpAcEDeViL
Hero Member
*****
Offline Offline

Activity: 706


View Profile WWW
July 25, 2014, 04:01:00 PM
 #9782

Hy,

i have run a p2pool on http://miner-control.de

I have test it and make with round about 500 GHs few "node" Shares over 340k
Best Share was 1.55M in my cgminer.

But no Share was counted, what is wrong here? Can anybody Helps?

http://miner-control.de/bitcoin_p2pool/

windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
July 25, 2014, 04:20:03 PM
 #9783

Hy,

i have run a p2pool on http://miner-control.de

I have test it and make with round about 500 GHs few "node" Shares over 340k
Best Share was 1.55M in my cgminer.

But no Share was counted, what is wrong here? Can anybody Helps?

http://miner-control.de/bitcoin_p2pool/

Minimum share difficulty for the pool is currently ~4MM, you did not have any valid shares yet...

Expected time to share should be somewhere around 12 hours at 500GH/s

SpAcEDeViL
Hero Member
*****
Offline Offline

Activity: 706


View Profile WWW
July 25, 2014, 04:31:20 PM
 #9784

Thx.

Where can i see, or show on the page, what the miner needed for a Pool Share. So i can reject the question before they come Wink


windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
July 25, 2014, 05:19:36 PM
 #9785

Thx.

Where can i see, or show on the page, what the miner needed for a Pool Share. So i can reject the question before they come Wink



With the front end your using its in the right column under "Share Difficulty"

jonnybravo0311
Legendary
*
Online Online

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
July 26, 2014, 03:56:02 AM
 #9786

S3s on p2pool... flashed the new firmware this morning and edited the cgminer script to set:
Code:
--queue 0 --expiry 1 --scan-time 1
First S3 hashing happily away at 440:


Second S3 hashing away at 427 (this one absolutely refuses to even hash at stock clocks without a smattering of "x" and "-":


Check out those hardware error rates... it's practically non-existent.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
rav3n_pl
Legendary
*
Offline Offline

Activity: 1320


Don`t panic! Organize!


View Profile
July 26, 2014, 09:27:18 AM
 #9787

S3s on p2pool... flashed the new firmware this morning and edited the cgminer script to set:
Code:
--queue 0 --expiry 1 --scan-time 1
It is REALLY BAD because you are forcing miner to drop work after 1 sec and get new one.
queue=0 is good idea, but scantime should be at least 10s (P2pool share is every 30s) and expiry to max 30 (but expiry means to drop work in queue).

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
My SatoshDice bot https://bitcointalk.org/index.php?topic=897685
jonnybravo0311
Legendary
*
Online Online

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
July 26, 2014, 02:37:38 PM
 #9788

S3s on p2pool... flashed the new firmware this morning and edited the cgminer script to set:
Code:
--queue 0 --expiry 1 --scan-time 1
It is REALLY BAD because you are forcing miner to drop work after 1 sec and get new one.
queue=0 is good idea, but scantime should be at least 10s (P2pool share is every 30s) and expiry to max 30 (but expiry means to drop work in queue).

That's an interesting point, and I probably should have considered the ramifications of setting it so low before just believing what I read as a recommendation.  I'm actually tearing down my S3s today, cleaning them completely of the messy thermal compound Bitmain used and putting AS5 on the chips.  I'll restart them with the updated scan time value of 10.

Thanks for the help.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
July 26, 2014, 02:39:26 PM
 #9789

Don't adjust scan or expiry, they're unhelpful. Don't drop queue lower than 1 on hardware that fast as it can impair its performance.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
jonnybravo0311
Legendary
*
Online Online

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
July 26, 2014, 02:43:10 PM
 #9790

Don't adjust scan or expiry, they're unhelpful. Don't drop queue lower than 1 on hardware that fast as it can impair its performance.
If you don't explicitly set scan/expiry parameters, what do they default to in cgminer?

EDIT: there are recommendations all over the board (bother literally and figuratively) regarding the best and/or most valuable tweaks to make.  Since you wrote the mining software, and I presume are at least conversationally familiar with Bitmain's hardware, what values would you recommend for the S3?  Should we leave it alone at Bitmain's setting of 4096?  Also, is Bitmain really using version 3.1.2 of cgminer, or have they number versions their own way because they've customized the software?  If yes, do you know the version of cgminer on which they based the one in the S3?

Thanks again!

EDIT2: Rather than just a straight up recommendation, is there some kind of formula to calculate the "best" setting for queue depth with a given hash rate and/or mining hardware?

EDIT3: Sorry!  I'm full of questions this morning... would setting the queue depth values be dependent on not only hash rate, but also the pool itself?  For example, would a miner on p2pool wish to have a value of X with hardware Y, but a miner on BTCGuild would want a value of Z for that same hardware Y.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
July 26, 2014, 02:56:32 PM
 #9791

I don't know what they did in their driver that needs such a large queue. I'd recommend a queue of 1 for every piece of hardware, always, on p2pool, unless there is some unique issue with the device that really needs it larger. S3 might fall into that category. Scan and expiry do nothing useful on today's hardware, today's stratum mining or with p2pool. All recommendations you may read are misguided. Bitmain really is using an older cgminer; they just kept working with the codebase they forked when they first created their own cgminer driver fork for S1.

EDIT: Virtually all manipulations of queue are also misguided, even if for other pools; the default is best there.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
jonnybravo0311
Legendary
*
Online Online

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
July 26, 2014, 03:12:56 PM
 #9792

I don't know what they did in their driver that needs such a large queue. I'd recommend a queue of 1 for every piece of hardware, always, on p2pool, unless there is some unique issue with the device that really needs it larger. S3 might fall into that category. Scan and expiry do nothing useful on today's hardware, today's stratum mining or with p2pool. All recommendations you may read are misguided. Bitmain really is using an older cgminer; they just kept working with the codebase they forked when they first created their own cgminer driver fork for S1.

EDIT: Virtually all manipulations of queue are also misguided, even if for other pools; the default is best there.

Thanks for your help.  If I understand you correctly, the following are your recommendations:
  • For p2pool, queue depth of 1.
  • Certain hardware that uses their own customized fork of cgminer may have different queue depth requirements due to driver implementation
  • Scan time and expiry settings are pointless on modern mining hardware

Your guidance is much appreciated.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
July 26, 2014, 03:14:43 PM
 #9793

Yes, that's the summary.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
July 26, 2014, 03:18:43 PM
 #9794

I don't know what they did in their driver that needs such a large queue. I'd recommend a queue of 1 for every piece of hardware, always, on p2pool, unless there is some unique issue with the device that really needs it larger. S3 might fall into that category. Scan and expiry do nothing useful on today's hardware, today's stratum mining or with p2pool. All recommendations you may read are misguided. Bitmain really is using an older cgminer; they just kept working with the codebase they forked when they first created their own cgminer driver fork for S1.

EDIT: Virtually all manipulations of queue are also misguided, even if for other pools; the default is best there.

Thanks for your help.  If I understand you correctly, the following are your recommendations:
  • For p2pool, queue depth of 1.
  • Certain hardware that uses their own customized fork of cgminer may have different queue depth requirements due to driver implementation
  • Scan time and expiry settings are pointless on modern mining hardware

Your guidance is much appreciated.

Note that you can set most of these temporarily via API through SSH.  That'll allow you to test the changes before you make them permanent.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
zvs
Legendary
*
Offline Offline

Activity: 1386



View Profile WWW
July 27, 2014, 12:01:54 AM
 #9795

I don't know what they did in their driver that needs such a large queue. I'd recommend a queue of 1 for every piece of hardware, always, on p2pool, unless there is some unique issue with the device that really needs it larger. S3 might fall into that category. Scan and expiry do nothing useful on today's hardware, today's stratum mining or with p2pool. All recommendations you may read are misguided. Bitmain really is using an older cgminer; they just kept working with the codebase they forked when they first created their own cgminer driver fork for S1.

EDIT: Virtually all manipulations of queue are also misguided, even if for other pools; the default is best there.

Thanks for your help.  If I understand you correctly, the following are your recommendations:
  • For p2pool, queue depth of 1.
  • Certain hardware that uses their own customized fork of cgminer may have different queue depth requirements due to driver implementation
  • Scan time and expiry settings are pointless on modern mining hardware

Your guidance is much appreciated.

They're pointless, but if you set expiry to 1 you may have some issues.

Was scan-time set to 1 and expiry set to 1 *ever* good?  I just did a quick google search and it looks like a lot of these GPU miner guides actually recommend that crap.  I always used a scan time of 30, expiry of 60 and queue of 1.  Was I wrong that whole time?  haha

Dacentec, best deals for US dedicated servers. They regularly restock $20-$25 Opterons with 8-16GB RAM & 2x1-2TB HDD's (ofc, usually lots of other good stuff to choose from).  I did a Serverbear benchmark of one of my $20/mo Opteron (June last year), it's here.  Have had about a half dozen different servers with Dacentec, & none have failed to sustain at least 40MB/s (burst higher). My favorite is a 12-month rent-to-own ZT Systems 2XL5520 16GB 2x2TB SATA for $40/month (got lucky with the 'off-brand', haven't seen a RTO 2xL5520 for under $50/mo since -- at least for monthly contracts).  wholesaleinternet.com has some ancient 2-core intel CPUs @ $10/mo sometimes (I got an Intel Core 2 6300 @ 1.86GHz, with a 250GB HDD with 46000 hours on it, LOL. $20 @ Dacentec is much better, if you can grab one). joesdatacenter.com (same location as Wholesale Internet) also occasionally has specials (or if you don't want to wait, it has an AMD Opteron 170 @ $16/mo).
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
July 27, 2014, 12:11:33 AM
 #9796

They're pointless, but if you set expiry to 1 you may have some issues.

Was scan-time set to 1 and expiry set to 1 *ever* good?  I just did a quick google search and it looks like a lot of these GPU miner guides actually recommend that crap.  I always used a scan time of 30, expiry of 60 and queue of 1.  Was I wrong that whole time?  haha
Adjustment of scan time is from the CPU mining days. Adjustment of expiry time is from the pre-longpoll mining days (i.e. first getwork servers long before stratum). So neither of them have been helpful for over 2 years, not even for GPU mining. Most attempts at modifying them since then have been based on misinformation and mining solo to random altcoins.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
July 27, 2014, 12:46:21 AM
 #9797

Was scan-time set to 1 and expiry set to 1 *ever* good?  I just did a quick google search and it looks like a lot of these GPU miner guides actually recommend that crap.  I always used a scan time of 30, expiry of 60 and queue of 1.  Was I wrong that whole time?  haha

I can't see how it could be.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
bryonp
Member
**
Offline Offline

Activity: 77


View Profile
July 28, 2014, 04:51:57 PM
 #9798

Hello all,
I know this has been asked.

If I open up my closed network and port forward 9332
to my p2pool machine.......
will this help
the shares???
Even if there is no one logging in and using my pool but me???

Thanks for any info on this....
jonnybravo0311
Legendary
*
Online Online

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
July 28, 2014, 05:33:31 PM
 #9799

Hello all,
I know this has been asked.

If I open up my closed network and port forward 9332
to my p2pool machine.......
will this help
the shares???
Even if there is no one logging in and using my pool but me???

Thanks for any info on this....
No.  Opening port 9332 just exposes your node to the outside world, so other miners could potentially connect and mine on it.  If by "helping the shares" you mean, "having a lower percentage of orphans" then you're best served by ensuring the nodes you connect to have low ping times.  Opening port 9333 will allow for connections to the p2pool network's peers - i.e. nodes can connect inbound to you.  If you're having problems with "dead" shares, ensure your miners are configured optimally, and that you have solid internal network connections.

Quick explanation for you:

Orphaned shares - you found a share and broadcast your copy of the share chain.  Unfortunately, somebody else's copy of the share chain was broadcast and accepted prior to yours.
Dead shares - you found a share, but it is not added to the chain or broadcast because by the time you found that share, the share chain had already been updated.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
abdullahadam
Sr. Member
****
Offline Offline

Activity: 285


View Profile
July 28, 2014, 05:43:00 PM
 #9800

I'm looking for a calculator,  something that takes into account the current p2pool hashrate and yours and gives you an accurate estimate per block  how much you should make,  so I can verify that my miner is working correctly and my payout makes sense
Pages: « 1 ... 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 [490] 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 ... 744 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!