[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 671.

twmz

hero member

Activity: 737

Merit: 500

Quote from: organofcorti on July 04, 2012, 08:17:51 PM

How dynamic is the difficulty? How often does it change?
If it changes often and this causes orphaned shares, what would the downside of changing it less frequently be?

I don't know if it changes every share or every few shares, but I'm not sure how the frequency of difficulty changes, alone is causing extra DOA/orphaned shares. If, when you started looking for a share the difficulty was 800 and you find a share that is valid for difficulty <= 800, the only way that that wouldn't be valid is if someone else found a share in between when you started looking and when you found a share (which is the only time the difficulty changes). But if that happens, then your share is DOA anyway because your share doesn't build off the most recent share (which arrived at your node and changed the difficulty).

Maybe I am missing something, though?

organofcorti

donator

Activity: 2058

Merit: 1007

Poor impulse control.

Couple of questions, rav3n_pl:

How dynamic is the difficulty? How often does it change?

If it changes often and this causes orphaned shares, what would the downside of changing it less frequently be?

Thanks for the work you do explaining p2Pool - it's really very helpful for those of us that want to understand it better but don't actually mine there.

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

https://en.bitcoin.it/wiki/P2Pool#Miners
Added simple tips that help few ppl reduce local DOA when using cgminer (best miner imo).

We have 2 kind of stales/doa there.

1. Miner getting work from p2pool
2. Miner finds a share diff>1 solution and send it to pool
3. Pool register share to calculate hash speed of miner
4. Pool checking that SD of share is higher that current SD of p2pool
5. If 4 is true Pool sending share to to other nodes.

Tuning miner options can reduce DOA that appears between 2 and 3. We can see it as red line in local graph.
It will NOT reduce doa/stales in between 4 and 5. Forrestv is struggling to improve logic of pool in that point. BUT like in "real" bitcoin share chain there is no way to reduce number of orphans to 0... ;]

sharky112065

sr. member

Activity: 383

Merit: 250

Quote from: rav3n_pl on July 02, 2012, 03:38:26 PM

Outdated clients/nodes/miners:

1PoNvnRhbvFE4xebEXjcVWfA3f2CGQkrCw
1DpJ9tfVotdAXc2FKfUDRJhHLP72hzBtQ4
17n2PjMRMZWsz6fiF9KpQZpLwRDzum7TzV
1HM8ysRnYZzmXD5i4W7FEiDP3brCZGsYC5
1Hxhyew5cJthaxX1iGi6gKjguaGYHpPoLj
16i6LtbydUput1BPDABmHtiFpuKAk9mtVT

Check your P2pool software and update it!

Sadly, you are wrong. My address is in that list and I upgraded my node three days ago and have double checked via the stats page.

twmz

hero member

Activity: 737

Merit: 500

Quote from: rav3n_pl on July 02, 2012, 03:38:26 PM

Outdated clients/nodes/miners:

...

Check your P2pool software and update it!

Sadly, people running outdated clients are almost certainly not reading this thread. Pretty much the only way to get their attention is to force an upgrade (i.e. fork them so that they stop getting paid regularly).

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Outdated clients/nodes/miners:

1PoNvnRhbvFE4xebEXjcVWfA3f2CGQkrCw
1DpJ9tfVotdAXc2FKfUDRJhHLP72hzBtQ4
17n2PjMRMZWsz6fiF9KpQZpLwRDzum7TzV
1HM8ysRnYZzmXD5i4W7FEiDP3brCZGsYC5
1Hxhyew5cJthaxX1iGi6gKjguaGYHpPoLj
16i6LtbydUput1BPDABmHtiFpuKAk9mtVT

Check your P2pool software and update it!

Icoin

hero member

Activity: 585

Merit: 501

chapeau for the new version 3.1-15 my node works flawless since the update to bitcoind 0.6.3 thanks for the awesome work !!

Prattler

full member

Activity: 192

Merit: 100

Quote from: Red Emerald on July 01, 2012, 03:00:07 PM

So I realize it hasn't been very long, but have the new share changes helped the orphan rate?

Yes! So far v3 changes have helped to save 1 block from being orphaned.

http://blockchain.info/block-index/241146

Still quite a lot of orphans past few days, hopefully it's just bad luck - they were all close calls.

doobeedoo

newbie

Activity: 24

Merit: 0

Quote from: sharky112065 on July 01, 2012, 02:59:06 PM

Quote from: doobeedoo on July 01, 2012, 08:13:49 AM

Quote from: doobeedoo on July 01, 2012, 07:29:53 AM

Quote from: Icoin on July 01, 2012, 03:17:26 AM

I obeserved today a phenomenon

Suddenly my stales rate went drasticaly up allso the whole machine was lagging badly, im not sure about what did cause that, i could not find any activities in my logs so that wasnt caused by any apache related activity, just p2pool and the chains was running. I suspect that this has something to do with peers; this could be intentionaly or cause of a bug. i realized that stales and orphaned shares on the p2pool operating chain are probably caused trough this.

got the same problem.
my DOA increased to 40-50 %.
using bitcoind 6.3.

investigated that my ztex-boards caused the problem. for some reason java took 100% of all 4 cores.
did a reboot and every thing is fine now.

Did this per chance happen at midnight 12 AM on the 1st of July? There was a leap second adjustment that has caused all kinds of problems. The solution is to reboot the computer that is having issues. This max CPU usage is something I have heard developers in other non Bitcoin related IRC channels mention.

thanks!
yes, it happened at 12AM and it was caused by the leap-second. I read that bitlc.net had some trouble with their java-apps too.

Red Emerald

hero member

Activity: 742

Merit: 500

So I realize it hasn't been very long, but have the new share changes helped the orphan rate?

sharky112065

sr. member

Activity: 383

Merit: 250

Quote from: doobeedoo on July 01, 2012, 08:13:49 AM

Quote from: doobeedoo on July 01, 2012, 07:29:53 AM

Quote from: Icoin on July 01, 2012, 03:17:26 AM

I obeserved today a phenomenon

Suddenly my stales rate went drasticaly up allso the whole machine was lagging badly, im not sure about what did cause that, i could not find any activities in my logs so that wasnt caused by any apache related activity, just p2pool and the chains was running. I suspect that this has something to do with peers; this could be intentionaly or cause of a bug. i realized that stales and orphaned shares on the p2pool operating chain are probably caused trough this.

got the same problem.
my DOA increased to 40-50 %.
using bitcoind 6.3.

investigated that my ztex-boards caused the problem. for some reason java took 100% of all 4 cores.
did a reboot and every thing is fine now.

Did this per chance happen at midnight 12 AM on the 1st of July? There was a leap second adjustment that has caused all kinds of problems. The solution is to reboot the computer that is having issues. This max CPU usage is something I have heard developers in other non Bitcoin related IRC channels mention.

Icoin

hero member

Activity: 585

Merit: 501

I would llike to point your attention towards the BMP Project listed on cryptostocks echange. This project has as the one of the primary goal to add a nice amout of hashpower (acutaly approxmatly 30 gh/s on avarage) to p2pool. At the moment the shares are free to buy in total 50k for a price of 0.1 BTC each. I would realy feel honored if members of the p2pool comunity would deside to become a shareholder. For more Informations please visit https://bitcointalksearch.org/topic/cryptostocks-gmp-crowdmining-90880 or directly at croyptostocks https://cryptostocks.com/securities/9 . For Security concerns: My personalities was audited and verfied trough cryptostocks https://bitcointalk.org/index.php?topic=88036.20

doobeedoo

newbie

Activity: 24

Merit: 0

Quote from: doobeedoo on July 01, 2012, 07:29:53 AM

Quote from: Icoin on July 01, 2012, 03:17:26 AM

I obeserved today a phenomenon

Suddenly my stales rate went drasticaly up allso the whole machine was lagging badly, im not sure about what did cause that, i could not find any activities in my logs so that wasnt caused by any apache related activity, just p2pool and the chains was running. I suspect that this has something to do with peers; this could be intentionaly or cause of a bug. i realized that stales and orphaned shares on the p2pool operating chain are probably caused trough this.

got the same problem.
my DOA increased to 40-50 %.
using bitcoind 6.3.

investigated that my ztex-boards caused the problem. for some reason java took 100% of all 4 cores.
did a reboot and every thing is fine now.

Icoin

hero member

Activity: 585

Merit: 501

Quote

What bitcoind version ur using? You just described 6.2 lag bug Smiley

thanks for the hint, meanwhile i use 0.6.3 bitcoind, everything back to normal here

doobeedoo

newbie

Activity: 24

Merit: 0

Quote from: Icoin on July 01, 2012, 03:17:26 AM

I obeserved today a phenomenon

Suddenly my stales rate went drasticaly up allso the whole machine was lagging badly, im not sure about what did cause that, i could not find any activities in my logs so that wasnt caused by any apache related activity, just p2pool and the chains was running. I suspect that this has something to do with peers; this could be intentionaly or cause of a bug. i realized that stales and orphaned shares on the p2pool operating chain are probably caused trough this.

got the same problem.
my DOA increased to 40-50 %.
using bitcoind 6.3.

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: Icoin on July 01, 2012, 03:17:26 AM

Suddenly my stales rate went drasticaly up allso the whole machine was lagging badly, im not sure about what did cause that, i could not find any activities in my logs so that wasnt caused by any apache related activity, just p2pool and the chains was running.

What bitcoind version ur using? You just described 6.2 lag bug

Icoin

hero member

Activity: 585

Merit: 501

I obeserved today a phenomenon

Suddenly my stales rate went drasticaly up allso the whole machine was lagging badly, im not sure about what did cause that, i could not find any activities in my logs so that wasnt caused by any apache related activity, just p2pool and the chains was running. I suspect that this has something to do with peers; this could be intentionaly or cause of a bug. i realized that stales and orphaned shares on the p2pool operating chain are probably caused trough this.

The solution is simple: restart the pool more often, a node that is running to long probably causes a higher amout of stales or even orphans...

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

Quote from: organofcorti on June 21, 2012, 03:33:43 AM

Rav3n_pl forwarded me a link to his local p2Pool stats page, which was very useful.

Can anyone else do that? Or take a screenshot or something? You can pm me the screenshot so it wont end up public.

Useful with just one person on it? Well, have a gander at http://5.9.24.81:9332/static/ if you like

my payout has been steadily decreasing, i think i should have stopped at max and went back to maxbtc, then wait til all my shares expire to come back *scratch*

Prattler

full member

Activity: 192

Merit: 100

Quote from: rav3n_pl on June 29, 2012, 02:46:05 AM

Ok, someone tell me how THIS is possible:

Code:

Blocks found in last day:

Note that blocks may have been orphaned from the P2Pool chain and so not be here.
time	hash
Fri Jun 29 2012 07:43:45 GMT+0200	00000000000000e47abfd1391d1feb1f4b7aede82dc0b48304edd6473820e2bb
Fri Jun 29 2012 05:30:55 GMT+0200	00000000000005d014e1902f49d1beb52facd3bbab1bf69ba7df888cc72644ea

http://blockexplorer.com/block/00000000000000e47abfd1391d1feb1f4b7aede82dc0b48304edd6473820e2bb - no such block??

http://178.195.18.168:9332/static/share.html#00000000000000e47abfd1391d1feb1f4b7aede82dc0b48304edd6473820e2bb

Looks like he mined a totally junk block, perhaps due to his bad connection or his bitcoind misbehaving.

~~Junk shares like that shouldn't be accepted, they should be orphaned. Perhaps similarly to the discouraging Gavin implemented for bitcoin. Hopefully the devs will fix it soon!~~ Edit: this is already what is happening, there's just a special rule for block solving shares, that's why it got through.

Indeed if you explore his shares around this incident you'll see he was having a very high orphan rate. The pool orphan rate spike are mostly all his shares, it seems. In the end, p2pool was not paying him, urging him to fix the problem.

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Ok, someone tell me how THIS is possible:

Code:

Blocks found in last day:

Note that blocks may have been orphaned from the P2Pool chain and so not be here.
time	hash
Fri Jun 29 2012 07:43:45 GMT+0200	00000000000000e47abfd1391d1feb1f4b7aede82dc0b48304edd6473820e2bb
Fri Jun 29 2012 05:30:55 GMT+0200	00000000000005d014e1902f49d1beb52facd3bbab1bf69ba7df888cc72644ea

http://blockexplorer.com/block/00000000000000e47abfd1391d1feb1f4b7aede82dc0b48304edd6473820e2bb - no such block??

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 671. (Read 2591920 times)