Bitcoin Forum
December 04, 2016, 06:07:46 AM *
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 ... 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 [411] 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2029325 times)
smooth
Legendary
*
Offline Offline

Activity: 1246



View Profile
April 09, 2014, 01:45:16 AM
 #8201

Now it's been nearly 4 days since a block was found.  When that block is found, assuming I continue on without interruption and I find about 6 shares a day, I'll get 18 shares worth of payment from that block, and from every block found until my rate of found shares goes down.

Mostly correct. Not necessarily exactly 18 shares worth. If that's your average then it might be a little higher or lower than that.

Also, remember, its only valid shares that count. Invalid shares don't exist except on a stats page.

1480831666
Hero Member
*
Offline Offline

Posts: 1480831666

View Profile Personal Message (Offline)

Ignore
1480831666
Reply with quote  #2

1480831666
Report to moderator
There are several different types of Bitcoin clients. Server-assisted clients like blockchain.info rely on centralized servers to do their network verification for them. Although the server can't steal the client's bitcoins directly, it can easily execute double-spending-style attacks against the client.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480831666
Hero Member
*
Offline Offline

Posts: 1480831666

View Profile Personal Message (Offline)

Ignore
1480831666
Reply with quote  #2

1480831666
Report to moderator
1480831666
Hero Member
*
Offline Offline

Posts: 1480831666

View Profile Personal Message (Offline)

Ignore
1480831666
Reply with quote  #2

1480831666
Report to moderator
1480831666
Hero Member
*
Offline Offline

Posts: 1480831666

View Profile Personal Message (Offline)

Ignore
1480831666
Reply with quote  #2

1480831666
Report to moderator
roy7
Sr. Member
****
Offline Offline

Activity: 434


View Profile
April 09, 2014, 03:55:37 AM
 #8202

Again, thanks for taking the time and providing the explanation!

My pleasure. Here's my one S1 that I own:

http://us-east.royalminingco.com:9332/static/miner.html?id=1Gtt49xTxD3udiKcMfuzK37oJu1pGbnr8A

Click on Week or Month and you can see more of my share value history over time.

Also remember for BTC the 3 day thing is just the max capacity of the window. It's really supposed to be 3 blocks worth of work on average. So once the pool start finding blocks faster than 1/day, shares will last less than 3 days.

RoyalMiningCo: Pools retired. Was fun!
jonnybravo0311
Hero Member
*****
Offline Offline

Activity: 994


Mine at Jonny's Pool


View Profile WWW
April 09, 2014, 12:47:56 PM
 #8203

Again, thanks for taking the time and providing the explanation!

My pleasure. Here's my one S1 that I own:

http://us-east.royalminingco.com:9332/static/miner.html?id=1Gtt49xTxD3udiKcMfuzK37oJu1pGbnr8A

Click on Week or Month and you can see more of my share value history over time.

Also remember for BTC the 3 day thing is just the max capacity of the window. It's really supposed to be 3 blocks worth of work on average. So once the pool start finding blocks faster than 1/day, shares will last less than 3 days.

Looking at your stats...

1) I like the front end by John Doe.  Very clean!
2) You don't have a single orphaned/dead share.  I wish I were so lucky.  After restarting my local node last night from upgrading to 0.9.1 I have found 2 shares, 1 of them is an orphan.  Over the past few days I've noticed my orphan rate has gone way up... from getting maybe 1 orphaned share in the first 15 shares I found, to getting a streak of about 8 orphaned shares in a row.

I know there have been tons of write-ups done on how to tune your local node, and I've read through them.  Unfortunately I'm just consistently getting a ton of orphans.  I'll keep trying to tune things to see if I can reduce the orphan rate.  Perhaps you could offer up some further suggestions?  Here's my setup:

Bitcoin-Qt and p2pool latest versions are running on a quad-core i7 (4850HQ @ 2.3GHz) with 16G RAM and a 512G PCI-e SSD.  It is on a wired gigabit internal network connected to the outside world at 35Mbps down 10Mbps up.  There is virtually no other traffic on this network (an iPhone and an iPad).  I have opened up ports 9332, 9333, 8333.  I have also tried a few of the different settings in bitcoin.conf (changing block size up and down, setting max connections from values of 6 to 50, etc).  I'm hashing away with an Antminer S1 over clocked to 200GH/s @ 393MHz with ~0.1% HW.  The S1 is on the latest firmware.  Yes, it's wired into the network (not wireless).

The biggest culprit I see is over the past week the reported Bitcoind GetBlock Template Latency has a mean of 0.572s (572ms seems way too high).  Over the past day, the mean is 372ms, which I feel is still ridiculously high.  Am I correct in my assumption here that this latency is likely what is causing me the pain?

Also, to give you an example of how things look, since I restarted everything last night after the upgrade, (11+ hours ago) I've found 2 shares, 1 of which is an orphan - effectively then 1 share added to the share chain.  I can certainly accept that it is taking me longer than the "expected" time to find shares.  Unfortunately, when I finally *do* find that share and it is then orphaned, it really has a negative impact.

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.
roy7
Sr. Member
****
Offline Offline

Activity: 434


View Profile
April 09, 2014, 02:35:15 PM
 #8204

2) You don't have a single orphaned/dead share.  I wish I were so lucky.  After restarting my local node last night from upgrading to 0.9.1 I have found 2 shares, 1 of them is an orphan.  Over the past few days I've noticed my orphan rate has gone way up... from getting maybe 1 orphaned share in the first 15 shares I found, to getting a streak of about 8 orphaned shares in a row.

Oh I've had some. I just restarted it a day or two ago. I was trying to find some ways to reduce the orphans further. I guess I could plot orphaned shares too. Next step for the interface is to add a list of all shares at the bottom like recent blocks.

I know there have been tons of write-ups done on how to tune your local node, and I've read through them.  Unfortunately I'm just consistently getting a ton of orphans.  I'll keep trying to tune things to see if I can reduce the orphan rate.  Perhaps you could offer up some further suggestions?

The main thing I'm trying at the moment is using -n to connect to the largest public nodes I can find. This way my shares might get spread more quickly, and/or I'll get updated on someone else's shares more quickly. I added the couple nodes with the highest hash rate I could locate, as well as one that had the highest incoming/outgoing connections.

The biggest culprit I see is over the past week the reported Bitcoind GetBlock Template Latency has a mean of 0.572s (572ms seems way too high).  Over the past day, the mean is 372ms, which I feel is still ridiculously high.  Am I correct in my assumption here that this latency is likely what is causing me the pain?

I don't actually know on that one. I assume share orphans are more a factor of the speed your found shares make it out to the network vs other people's found shares. If all users have the same orphan rate then the orphans don't matter, because we all get a proportional amount of a found block.

RoyalMiningCo: Pools retired. Was fun!
jonnybravo0311
Hero Member
*****
Offline Offline

Activity: 994


Mine at Jonny's Pool


View Profile WWW
April 09, 2014, 03:01:17 PM
 #8205

Quote
The main thing I'm trying at the moment is using -n to connect to the largest public nodes I can find. This way my shares might get spread more quickly, and/or I'll get updated on someone else's shares more quickly. I added the couple nodes with the highest hash rate I could locate, as well as one that had the highest incoming/outgoing connections.

Interesting idea.  I hadn't thought to force connections to known large nodes.  I assume you can either a) pass multiple nodes or b) provide multiple -n parameters in the startup?

a) ./run_p2pool.py -n host1:port host2:port
b) ./run_p2pool.py -n host1:port -n host2:port

I'll give that a try to see if it helps propagate my shares more quickly.

Again, thanks for the help Smiley

Side note... 14 hours of uptime on the node, 2 shares found (1 orphan)... arghh... lol.  Come on Lady Luck, shine down on the p2pool hashers!

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.
jonnybravo0311
Hero Member
*****
Offline Offline

Activity: 994


Mine at Jonny's Pool


View Profile WWW
April 09, 2014, 06:24:28 PM
 #8206

Hey roy7,

So, I decided to check your stats page again.  Now you've found 11 shares (3 more since this morning when I first checked).  I've found exactly 0 more.

Am I just exceedingly unlucky, or have you been exceedingly lucky, or is something more nefarious going on here on my end?  Over 16 hours since the restart after upgrading Bitcoin-Qt to 0.9.1 and I've found 1 share...

Edit: Alright, that's just weird... when I refreshed the stats on your side it now says you've found 10 shares (? orphan, ? dead).  Ummm... I KNOW it showed 11 just a minute ago... lol

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.
roy7
Sr. Member
****
Offline Offline

Activity: 434


View Profile
April 09, 2014, 06:28:03 PM
 #8207

Hey roy7,

So, I decided to check your stats page again.  Now you've found 11 shares (3 more since this morning when I first checked).  I've found exactly 0 more.

Am I just exceedingly unlucky, or have you been exceedingly lucky, or is something more nefarious going on here on my end?  Over 16 hours since the restart after upgrading Bitcoin-Qt to 0.9.1 and I've found 1 share...

You must be unlucky? The interface tells me the time to share for 186 GH/s is currently 4h 3m 37 s. I don't see how/why bitcoind would mess you up. I'm also running 0.9.1.

RoyalMiningCo: Pools retired. Was fun!
jonnybravo0311
Hero Member
*****
Offline Offline

Activity: 994


Mine at Jonny's Pool


View Profile WWW
April 09, 2014, 06:33:37 PM
 #8208

Hey roy7,

So, I decided to check your stats page again.  Now you've found 11 shares (3 more since this morning when I first checked).  I've found exactly 0 more.

Am I just exceedingly unlucky, or have you been exceedingly lucky, or is something more nefarious going on here on my end?  Over 16 hours since the restart after upgrading Bitcoin-Qt to 0.9.1 and I've found 1 share...

You must be unlucky? The interface tells me the time to share for 186 GH/s is currently 4h 3m 37 s. I don't see how/why bitcoind would mess you up. I'm also running 0.9.1.


LOL... with luck like that... seriously... 1 share in 16 hours... that's just plain awful.  I could probably calculate it by hand faster Tongue

Edit: I noticed that the versions showing on our nodes are different.  Yours shows 13.4-34-gabbbdd3-dirty.  Mine is 13.4-24-gf0eeb48-dirty.  I just did a git pull from forrestv repo last night when I updated to 0.9.1.  How'd you get the 4-34 version?  You running off some branch/fork?

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.
roy7
Sr. Member
****
Offline Offline

Activity: 434


View Profile
April 09, 2014, 06:48:29 PM
 #8209

LOL... with luck like that... seriously... 1 share in 16 hours... that's just plain awful.  I could probably calculate it by hand faster Tongue

Edit: I noticed that the versions showing on our nodes are different.  Yours shows 13.4-34-gabbbdd3-dirty.  Mine is 13.4-24-gf0eeb48-dirty.  I just did a git pull from forrestv repo last night when I updated to 0.9.1.  How'd you get the 4-34 version?  You running off some branch/fork?

I have various patches applied but I didn't realize that would increment the version number. I'm running forrestv's repo for BTC, p2pool-n repo for VTC, and rav3n's repo for Uno. Here's a graph of my p2pool fork for BTC:

https://github.com/roy7/p2pool/network

Looks like I'm only running mmouse's minerstats and my own vardiffbyaddress. However I thought I also had iongchun's auto-worker-diff applied, but maybe I never pushed that up to my fork. If I have time tonight I'll clean it up some.

RoyalMiningCo: Pools retired. Was fun!
jonnybravo0311
Hero Member
*****
Offline Offline

Activity: 994


Mine at Jonny's Pool


View Profile WWW
April 09, 2014, 06:58:41 PM
 #8210

Ahh... I've got rav3n's and forrestv's.  Are you merge-mining the BTC/VTC/UNO?  What kind of impact, if any, does that have vs just mining BTC?  I assume you'd start the p2pool with something like:

./run_p2pool.py --merged walletID@host:port ...

Yeah?

Edit: Well, you're obviously not merge-mining the VTC since it's scrypt-n Wink

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.
roy7
Sr. Member
****
Offline Offline

Activity: 434


View Profile
April 09, 2014, 10:20:39 PM
 #8211

I merge mine Namecoin on UNO and BTC. That's it so far. Haven't tried United Scrypt, Huntercoin, etc.

RoyalMiningCo: Pools retired. Was fun!
kano
Legendary
*
Offline Offline

Activity: 1918


Linux since 1997 RedHat 4


View Profile
April 09, 2014, 11:51:17 PM
 #8212

Three blocks were found in 21 hours.  I see the logic though, three rounds took longer.

Irony ... Smiley
Quote
Embarrassed to admit you're wrong?

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
IYFTech
Hero Member
*****
Offline Offline

Activity: 686


WANTED: Active dev to fix & re-write p2pool in C


View Profile
April 11, 2014, 12:45:19 AM
 #8213

Right, I'm checking out. These 4, 5 or 6+ day blocks don't even pay my electric bill  Roll Eyes

Adios amigos.

-- Smiley  Thank you for smoking  Smiley --  If you paid VAT to dogie for items you should read this thread:  https://bitcointalk.org/index.php?topic=1018906.0
smooth
Legendary
*
Offline Offline

Activity: 1246



View Profile
April 11, 2014, 12:47:52 AM
 #8214

Right, I'm checking out. These 4, 5 or 6+ day blocks don't even pay my electric bill  Roll Eyes

Adios amigos.

You could save up a bit from the 3-block days. Just saying.

IYFTech
Hero Member
*****
Offline Offline

Activity: 686


WANTED: Active dev to fix & re-write p2pool in C


View Profile
April 11, 2014, 01:02:23 AM
 #8215

Right, I'm checking out. These 4, 5 or 6+ day blocks don't even pay my electric bill  Roll Eyes

Adios amigos.

You could save up a bit from the 3-block days. Just saying.



Still not enough. Still having to reboot once a week are you?

Just asking.  Wink

-- Smiley  Thank you for smoking  Smiley --  If you paid VAT to dogie for items you should read this thread:  https://bitcointalk.org/index.php?topic=1018906.0
smooth
Legendary
*
Offline Offline

Activity: 1246



View Profile
April 11, 2014, 01:12:43 AM
 #8216

Right, I'm checking out. These 4, 5 or 6+ day blocks don't even pay my electric bill  Roll Eyes

Adios amigos.

You could save up a bit from the 3-block days. Just saying.



Still not enough. Still having to reboot once a week are you?

Just asking.  Wink

No reboots, just p2pool instance restart. Yes still set up to do that, no idea if its still needed but everything works as-is so I leave it alone.
IYFTech
Hero Member
*****
Offline Offline

Activity: 686


WANTED: Active dev to fix & re-write p2pool in C


View Profile
April 11, 2014, 01:17:40 AM
 #8217

You'll be OK:

I know its been a long wait, but now it should only take about one more day to get a block.  Just FYI.


 Cheesy Cheesy Cheesy Cheesy Cheesy Cheesy Cheesy

-- Smiley  Thank you for smoking  Smiley --  If you paid VAT to dogie for items you should read this thread:  https://bitcointalk.org/index.php?topic=1018906.0
smooth
Legendary
*
Offline Offline

Activity: 1246



View Profile
April 11, 2014, 01:28:18 AM
 #8218

You'll be OK:

I know its been a long wait, but now it should only take about one more day to get a block.  Just FYI.


 Cheesy Cheesy Cheesy Cheesy Cheesy Cheesy Cheesy

More like 2 days now. We're slacking.
Littleshop
Legendary
*
Offline Offline

Activity: 1316



View Profile WWW
April 11, 2014, 03:46:41 AM
 #8219

You'll be OK:

I know its been a long wait, but now it should only take about one more day to get a block.  Just FYI.


 Cheesy Cheesy Cheesy Cheesy Cheesy Cheesy Cheesy

More like 2 days now. We're slacking.


And now finally, a block.  1 min ago.  Smiley


CaptEmulation
Full Member
***
Offline Offline

Activity: 135


View Profile
April 11, 2014, 09:40:21 PM
 #8220

And another one!

Pages: « 1 ... 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 [411] 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 ... 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!