Author

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

sr. member
Activity: 448
Merit: 250
Did we just fork?  My "Expected time to share" just tripled.  I'm also not seeing the "Switchover imminent" messages anymore.

I hope so, my expected time to share went from about 35 minutes to 3 hours.
legendary
Activity: 1036
Merit: 1000
DARKNETMARKETS.COM
Errors in new version:
Code:
Linux 3.2.0-4-amd64 x86_64 GNU/Linux
Description:    Debian GNU/Linux 7.1 (wheezy)
Python 2.7.3
Current p2pool version: 13.1
Code:
2013-07-15 01:23:20.739541 P2Pool: 17343 shares in chain (17347 verified/17347 total) Peers: 7 (1 incoming)
2013-07-15 01:23:20.739646  Local: 0H/s in last 10.0 minutes Local dead on arrival: ??? Expected time to share: ???
2013-07-15 01:23:20.739683  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-07-15 01:23:20.739726  Pool: 1280GH/s Stale rate: 15.5% Expected time to block: 1.0 days
2013-07-15 01:23:24.094661 > Error in DeferredResource handler:
2013-07-15 01:23:24.094747 > Traceback (most recent call last):
2013-07-15 01:23:24.094779 >   File "/home/pioruns/p2pool/p2pool/util/deferred_resource.py", line 24, in render
2013-07-15 01:23:24.094810 >     defer.maybeDeferred(resource.Resource.render, self, request).addCallbacks(finish, finish_error)
2013-07-15 01:23:24.094843 >   File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 137, in maybeDeferred
2013-07-15 01:23:24.094875 >     result = f(*args, **kw)
2013-07-15 01:23:24.094904 >   File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/web/resource.py", line 250, in render
2013-07-15 01:23:24.094935 >     return m(request)
2013-07-15 01:23:24.094964 >   File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 1213, in unwindGenerator
2013-07-15 01:23:24.094995 >     return _inlineCallbacks(None, gen, Deferred())
2013-07-15 01:23:24.095023 > --- ---
2013-07-15 01:23:24.095051 >   File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 1070, in _inlineCallbacks
2013-07-15 01:23:24.095081 >     result = g.send(result)
2013-07-15 01:23:24.095109 >   File "/home/pioruns/p2pool/p2pool/web.py", line 186, in render_GET
2013-07-15 01:23:24.095137 >     res = yield self.func(*self.args)
2013-07-15 01:23:24.095165 >   File "/home/pioruns/p2pool/p2pool/web.py", line 446, in
2013-07-15 01:23:24.095195 >     new_root.putChild('graph_data', WebInterface(lambda source, view: hd.datastreams[source].dataviews[view].get_data(time.time())))
2013-07-15 01:23:24.095225 > exceptions.KeyError: 'last_'
2013-07-15 01:23:35.771283 P2Pool: 17343 shares in chain (17347 verified/17347 total) Peers: 7 (1 incoming)
2013-07-15 01:23:35.771436  Local: 0H/s in last 10.0 minutes Local dead on arrival: ??? Expected time to share: ???
2013-07-15 01:23:35.771502  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-07-15 01:23:35.771572  Pool: 1280GH/s Stale rate: 15.5% Expected time to block: 1.0 days
Code:
2013-07-15 01:28:24.560067 > Traceback (most recent call last):
2013-07-15 01:28:24.560102 >   File "/home/pioruns/p2pool/p2pool/util/deferred_resource.py", line 24, in render
2013-07-15 01:28:24.560137 >     defer.maybeDeferred(resource.Resource.render, self, request).addCallbacks(finish, finish_error)
2013-07-15 01:28:24.560177 >   File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 137, in maybeDeferred
2013-07-15 01:28:24.560214 >     result = f(*args, **kw)
2013-07-15 01:28:24.560248 >   File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/web/resource.py", line 250, in render
2013-07-15 01:28:24.560288 >     return m(request)
2013-07-15 01:28:24.560320 >   File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 1213, in unwindGenerator
2013-07-15 01:28:24.560355 >     return _inlineCallbacks(None, gen, Deferred())
2013-07-15 01:28:24.560385 > --- ---
2013-07-15 01:28:24.560416 >   File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 1070, in _inlineCallbacks
2013-07-15 01:28:24.560449 >     result = g.send(result)
2013-07-15 01:28:24.560479 >   File "/home/pioruns/p2pool/p2pool/web.py", line 186, in render_GET
2013-07-15 01:28:24.560510 >     res = yield self.func(*self.args)
2013-07-15 01:28:24.560543 >   File "/home/pioruns/p2pool/p2pool/web.py", line 446, in
2013-07-15 01:28:24.560576 >     new_root.putChild('graph_data', WebInterface(lambda source, view: hd.datastreams[source].dataviews[view].get_data(time.time())))
2013-07-15 01:28:24.560622 > exceptions.KeyError: 'last_'
legendary
Activity: 1904
Merit: 1002
Did we just fork?  My "Expected time to share" just tripled.  I'm also not seeing the "Switchover imminent" messages anymore.

Edit: It appears so... this was the last switchover message in my log (time is EST).
Quote
2013-07-14 18:36:51.640422 Switchover imminent. Upgraded: 92.061% Threshold: 95.000%

After which I see several of these:
Quote
2013-07-14 18:38:52.620338 Lost peer -
2013-07-14 18:38:52.620455     Connection was aborted locally, using
2013-07-14 18:38:52.620595     L{twisted.internet.interfaces.ITCPTransport.abortConnection}.
2013-07-14 18:38:52.620723
2013-07-14 18:38:52.620843     @since: 11.1

I'm looking forward to ASIC reports.  I can recommend this guide for setting up and tuning p2pool (just mind that it might not yet be updated for the ASIC friendly changes this fork brings, so don't be discouraged by the warnings): https://bitcointalksearch.org/topic/a-guide-for-mining-efficiently-on-p2pool-includes-fud-repellent-and-faq-153232

I would like to see my tiny 20GH/s get knocked out of the top 10 Smiley
sr. member
Activity: 454
Merit: 252
Could someone explain the changes in SHARE_PERIOD and SPREAD? I understand it's to support ASICs in some way but can we get a more detailed explanation as to what these setting do?

Code:
Bitcoin:
        SHARE_PERIOD=10, # seconds
        NEW_SHARE_PERIOD=30, # seconds

        SPREAD=3, # blocks
        NEW_SPREAD=3, # blocks

Litecoin:
        SHARE_PERIOD=10, # seconds
        NEW_SHARE_PERIOD=15, # seconds

        SPREAD=12, # blocks
        NEW_SPREAD=3, # blocks

Thanks!

I'm not sure about SPREAD, but SHARE_PERIOD is the target time between shares.  Essentially, the sharechain is blockchain of valid bitcoin blocks, but it has a target block time of SHARE_PERIOD.  The payouts for valid blocks have to pay out to the last CHAIN_LENGTH shares.

SPREAD is basically how long will p2pool remember shares in units of expected time to share. If it should take 10 hours for a share, a spread of 3 means shares are remembered for 30 hours (although there is a cap of 24 hours, this is more important to LTC as of now).
legendary
Activity: 1904
Merit: 1002
Could someone explain the changes in SHARE_PERIOD and SPREAD? I understand it's to support ASICs in some way but can we get a more detailed explanation as to what these setting do?

Code:
Bitcoin:
        SHARE_PERIOD=10, # seconds
        NEW_SHARE_PERIOD=30, # seconds

        SPREAD=3, # blocks
        NEW_SPREAD=3, # blocks

Litecoin:
        SHARE_PERIOD=10, # seconds
        NEW_SHARE_PERIOD=15, # seconds

        SPREAD=12, # blocks
        NEW_SPREAD=3, # blocks

Thanks!

I'm not sure about SPREAD, but SHARE_PERIOD is the target time between shares.  Essentially, the sharechain is blockchain of valid bitcoin blocks, but it has a target block time of SHARE_PERIOD.  The payouts for valid blocks have to pay out to the last CHAIN_LENGTH shares.
legendary
Activity: 1270
Merit: 1000
Could someone explain the changes in SHARE_PERIOD and SPREAD? I understand it's to support ASICs in some way but can we get a more detailed explanation as to what these setting do?

Code:
Bitcoin:
        SHARE_PERIOD=10, # seconds
        NEW_SHARE_PERIOD=30, # seconds

        SPREAD=3, # blocks
        NEW_SPREAD=3, # blocks

Litecoin:
        SHARE_PERIOD=10, # seconds
        NEW_SHARE_PERIOD=15, # seconds

        SPREAD=12, # blocks
        NEW_SPREAD=3, # blocks

Thanks!
legendary
Activity: 1904
Merit: 1002
I have 6 GH/s pointed to P2Pool.  Can I get a %% update it currently is at?

Switchover imminent. Upgraded: 66.962% Threshold: 95.000%


? I'm seeing an average of 91% over last 24h in the graphs and a big chunk of hashrate switched over less than 24 hours ago. The switch should happen in the next 48h.

Hashrate has been rising too: it's at ~1.4TH/s. Exciting times for p2pool, we may regain a spot in the top 5 pools if enough people join and lower variance:currently only people understanding variance and able to afford it are on p2pool, with lower variance more people will join.

There is 12 hour lag.


the changes will take effect 12 hours after 95% of the mining power has been upgraded, as usual.


I guess it will be a little while yet.

Still, I would agree with your 48 hour estimate.
hero member
Activity: 896
Merit: 1000
I have 6 GH/s pointed to P2Pool.  Can I get a %% update it currently is at?

Switchover imminent. Upgraded: 66.962% Threshold: 95.000%


? I'm seeing an average of 91% over last 24h in the graphs and a big chunk of hashrate switched over less than 24 hours ago. The switch should happen in the next 48h.

Hashrate has been rising too: it's at ~1.4TH/s. Exciting times for p2pool, we may regain a spot in the top 5 pools if enough people join and lower variance:currently only people understanding variance and able to afford it are on p2pool, with lower variance more people will join.
sr. member
Activity: 252
Merit: 250
I have 6 GH/s pointed to P2Pool.  Can I get a %% update it currently is at?

Switchover imminent. Upgraded: 66.962% Threshold: 95.000%


*sigh* Was hoping it would be higher by now.  Thanks for the update though.
legendary
Activity: 1904
Merit: 1002
I have 6 GH/s pointed to P2Pool.  Can I get a %% update it currently is at?

Switchover imminent. Upgraded: 66.962% Threshold: 95.000%
legendary
Activity: 1904
Merit: 1002
Pretty selfish

But it could hurt revenue by 5% for a whole day!  He certainly can't afford that.... unless he has a fast connection and fast hard drives.  Then his 110%+ efficiency would make up for it Tongue.
sr. member
Activity: 252
Merit: 250
I have 6 GH/s pointed to P2Pool.  Can I get a %% update it currently is at?
legendary
Activity: 2912
Merit: 1060
member
Activity: 77
Merit: 10
...but everybody keeps their ASICs in pocket :-/
yes, because the switch over is not done yet. I will point my ASICs to p2pool when switch over is done and it's working with the new 30sec interval.

If you had larger ASICs, you could probably make the difference.
sr. member
Activity: 397
Merit: 500
...but everybody keeps their ASICs in pocket :-/
yes, because the switch over is not done yet. I will point my ASICs to p2pool when switch over is done and it's working with the new 30sec interval.
.m.
sr. member
Activity: 280
Merit: 260
I'd love to help moar - but everybody keeps their ASICs in pocket :-/
zvs
legendary
Activity: 1680
Merit: 1000
https://web.archive.org/web/*/nogleg.com
2013-07-14 10:49:30.211333 Switchover imminent. Upgraded: 72.139% Threshold: 95.000%

2013-07-14 11:02:43.978599 Switchover imminent. Upgraded: 71.870% Threshold: 95.000%



bleat


i even reactivated "Moses Blah" an incredibly wasteful 6990, tap tap
hero member
Activity: 662
Merit: 500
Here are the top 3 public nodes (total of 6-7 GH/s) from http://p2pool-nodes.info/
Notice anything in common?
http://212.109.128.148:9332/static/
http://86.185.31.215:9332/static/
http://37.59.10.166:9332/static/

their web interface doesn't tell them a switch is imminent...

The warning is on the graphs page
http://37.59.10.166:9332/static/graphs.html?Day

This last 2-3% is sooooo frustrating!
sr. member
Activity: 454
Merit: 252
Here are the top 3 public nodes that are still < v13 (total of 6-7 GH/s) from http://p2pool-nodes.info/
Notice anything in common?
http://212.109.128.148:9332/static/
http://86.185.31.215:9332/static/
http://37.59.10.166:9332/static/

their web interface doesn't tell them a switch is imminent...
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
5,3% is "old", so we sill need some more power to switch.
Jump to: