Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 504. (Read 2591928 times)
Idk the celerons, atoms and i5s I've used are trash
The celeron might not be enough. My latency on a 1.3ghz dual core atom (8gb ram, 120gb ssd) was high enough to increase my orphan and DOA rate pretty dramatically. The again, the celeron should be slightly faster.
My getblocktemplate latency was around ~500ms with the Atom. Dropped to ~100ms running on my main i7.
My getblocktemplate latency was around ~500ms with the Atom. Dropped to ~100ms running on my main i7.
Yeah, I think I might use a different SSD, something a little bigger. The little Celeron 847 is pretty quick for what it is. 
Catched an error today:
Code:
2013-07-24 12:58:36.067043 Pool: 2343GH/s Stale rate: 9.8% Expected time to block: 15.9 hours
2013-07-24 12:58:44.749809 Peer sent entire transaction a4bcbbc4fbed73523e13ba325acd3efe5e706b3fe8b492751f73598c7a5ca603 that was already received
2013-07-24 12:58:51.094497 P2Pool: 17428 shares in chain (17432 verified/17432 total) Peers: 7 (0 incoming)
2013-07-24 12:58:51.097240 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2013-07-24 12:58:51.097320 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-07-24 12:58:51.097409 Pool: 2343GH/s Stale rate: 9.8% Expected time to block: 15.9 hours
2013-07-24 12:59:06.124648 P2Pool: 17428 shares in chain (17432 verified/17432 total) Peers: 7 (0 incoming)
2013-07-24 12:59:06.124736 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2013-07-24 12:59:06.124767 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-07-24 12:59:06.124804 Pool: 2343GH/s Stale rate: 9.8% Expected time to block: 15.9 hours
2013-07-24 12:59:21.151871 P2Pool: 17428 shares in chain (17432 verified/17432 total) Peers: 7 (0 incoming)
2013-07-24 12:59:21.151978 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2013-07-24 12:59:21.152017 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-07-24 12:59:21.152061 Pool: 2343GH/s Stale rate: 9.8% Expected time to block: 15.9 hours
2013-07-24 12:59:28.991313 Peer sent entire transaction f2f79a3ea9cf95cf4995b7dff8be2c6063706abc00c754b66a5f6fe80d635871 that was already received
2013-07-24 12:59:36.180783 P2Pool: 17428 shares in chain (17432 verified/17432 total) Peers: 7 (0 incoming)
2013-07-24 12:59:36.181005 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2013-07-24 12:59:36.181121 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-07-24 12:59:36.181265 Pool: 2343GH/s Stale rate: 9.8% Expected time to block: 15.9 hours
2013-07-24 12:59:36.372657 > Error while processing Event callbacks:
2013-07-24 12:59:36.372933 > Traceback (most recent call last):
2013-07-24 12:59:36.373074 > File "/home/pioruns/p2pool/p2pool/p2p.py", line 280, in handle_shares
2013-07-24 12:59:36.373234 > self.node.handle_shares(result, self)
2013-07-24 12:59:36.373369 > File "/home/pioruns/p2pool/p2pool/node.py", line 48, in handle_shares
2013-07-24 12:59:36.373505 > self.node.set_best_share()
2013-07-24 12:59:36.373627 > File "/home/pioruns/p2pool/p2pool/node.py", line 297, in set_best_share
2013-07-24 12:59:36.373749 > self.best_share_var.set(best)
2013-07-24 12:59:36.373864 > File "/home/pioruns/p2pool/p2pool/util/variable.py", line 74, in set
2013-07-24 12:59:36.373986 > self.changed.happened(value)
2013-07-24 12:59:36.374099 > ------
2013-07-24 12:59:36.374213 > File "/home/pioruns/p2pool/p2pool/util/variable.py", line 42, in happened
2013-07-24 12:59:36.374333 > func(*event)
2013-07-24 12:59:36.374444 > File "/home/pioruns/p2pool/p2pool/node.py", line 96, in broadcast_share
2013-07-24 12:59:36.374543 > peer.sendShares([share for share in shares if share.peer_addr != peer.addr], self.node.tracker, self.node.known_txs_var.value, include_txs_with=[share_hash])
2013-07-24 12:59:36.374664 > File "/home/pioruns/p2pool/p2pool/p2p.py", line 288, in sendShares
2013-07-24 12:59:36.374770 > assert tx_hash in known_txs, 'tried to broadcast share without knowing all its new transactions'
2013-07-24 12:59:36.374875 > exceptions.AssertionError: tried to broadcast share without knowing all its new transactions
2013-07-24 12:59:36.996534 Peer sent entire transaction 1607b548e80dc1aaad5ac47dc263ce0fc2ece8c532eb38a1f1f55fb168fed197 that was already received
2013-07-24 12:59:37.032141 Peer sent entire transaction 1607b548e80dc1aaad5ac47dc263ce0fc2ece8c532eb38a1f1f55fb168fed197 that was already received
2013-07-24 12:59:37.439208 Peer sent entire transaction 1607b548e80dc1aaad5ac47dc263ce0fc2ece8c532eb38a1f1f55fb168fed197 that was already received
2013-07-24 12:59:39.190384 P2Pool: 17429 shares in chain (17433 verified/17433 total) Peers: 7 (0 incoming)
2013-07-24 12:59:39.193220 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2013-07-24 12:59:39.193264 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-07-24 12:59:39.193307 Pool: 2355GH/s Stale rate: 9.8% Expected time to block: 15.8 hours
2013-07-24 12:59:39.300764 Peer sent entire transaction 1607b548e80dc1aaad5ac47dc263ce0fc2ece8c532eb38a1f1f55fb168fed197 that was already received
2013-07-24 12:59:54.220979 P2Pool: 17429 shares in chain (17433 verified/17433 total) Peers: 7 (0 incoming)
2013-07-24 12:59:54.221136 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2013-07-24 12:59:54.221191 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
Problem isn't necessarily p2pool, its bitcoind. As long as it can produce work in .1 seconds you're good. For a couple microseconds it will use 100% cpu, and remember disk space as blockchain gets bigger.
What spec of machines are folks using for p2pool? I'm thinking of setting it up myself, but not sure what machine to use.
I've got a Celeron 847 (dual core 1.1GHz) with 8GB RAM and a 64GB SDD. Is that likely to be enough? Probably running Windows Server 2008R2, so very little OS overhead.
I've got a Celeron 847 (dual core 1.1GHz) with 8GB RAM and a 64GB SDD. Is that likely to be enough? Probably running Windows Server 2008R2, so very little OS overhead.
That should be plenty. The SSD will be the biggest help.
M
What spec of machines are folks using for p2pool? I'm thinking of setting it up myself, but not sure what machine to use.
I've got a Celeron 847 (dual core 1.1GHz) with 8GB RAM and a 64GB SDD. Is that likely to be enough? Probably running Windows Server 2008R2, so very little OS overhead.
I've got a Celeron 847 (dual core 1.1GHz) with 8GB RAM and a 64GB SDD. Is that likely to be enough? Probably running Windows Server 2008R2, so very little OS overhead.
How far back does p2pool look at your work share to calculate your share in a solved block?
The length of the share chain is around 8640 shares, which with an average 30s share time, is 3 days.
How far back does p2pool look at your work share to calculate your share in a solved block?
Maybe I'm just jinxed.
Told you, my payout is currently at about half the normal level due to the my bad luck in finding shares over the last couple of days and this is when we find 2 blocks in less than 2 hours.
Though bad software or hardware doesn't help
Edit: yes 16 block apart - not too bad.
Edit2: see it was making up for your half payout by paying you twice
Maybe I'm just jinxed.
Told you, my payout is currently at about half the normal level due to the my bad luck in finding shares over the last couple of days and this is when we find 2 blocks in less than 2 hours.
When is this round going to end 
Seeing as my nodes have had very bad luck the last couple of days (2.2hrs to share, 6 shares in the last 48 hours!) and my payout has dropped to under half what it was a day ago, I'm predicting a bunch of blocks in short succession!
Thinking otherwise is called the Gambler's Falacy.
I added a BFL SC Single on to p2pool today ... I wonder if that will help
(P.S. I run /+64 but I don't put up the true share difficulty)
I am aware of that, just pointing out that my luck (in general, not just mining) always seems to be on the bad end of the scale. Maybe I'm just jinxed.
omg, we found one. now 10 more please.
Why p2pool.info is showing wrong hashrate?
My node reports right now:
Code:
Pool Hashrate: 261.6 GH/s
Estimated Time to Block: 5d 22h 32m
Current Round: 4d 17h 0m
My node reports right now:
Code:
Pool rate: 2.00TH/s (9.1% DOA+orphan) Share difficulty: 8470
Node uptime: 1.714 days Peers: 6 out, 5 in
It must be on the old fork
*sigh*
My home network has been down for a couple hours and so p2pool.info switched to using one of the other public p2pool nodes to get stats. Sadly, it happened to choose one that is on a fork.
Edit: ironically, it was pulling stats from p2pool.org, which is on an old fork. I'll remove that one from the list of possible backup stats nodes.
Why p2pool.info is showing wrong hashrate?
My node reports right now:
Code:
Pool Hashrate: 261.6 GH/s
Estimated Time to Block: 5d 22h 32m
Current Round: 4d 17h 0m
My node reports right now:
Code:
Pool rate: 2.00TH/s (9.1% DOA+orphan) Share difficulty: 8470
Node uptime: 1.714 days Peers: 6 out, 5 in
It must be on the old fork
Why p2pool.info is showing wrong hashrate?
My node reports right now:
Code:
Pool Hashrate: 261.6 GH/s
Estimated Time to Block: 5d 22h 32m
Current Round: 4d 17h 0m
My node reports right now:
Code:
Pool rate: 2.00TH/s (9.1% DOA+orphan) Share difficulty: 8470
Node uptime: 1.714 days Peers: 6 out, 5 in
When is this round going to end
Seeing as my nodes have had very bad luck the last couple of days (2.2hrs to share, 6 shares in the last 48 hours!) and my payout has dropped to under half what it was a day ago, I'm predicting a bunch of blocks in short succession!
I've been on for 3 days now. I'm still not at "ideal" payout. Despite running at > 100% efficiency. Everyone else seeing this? Running around 5gh/s.
M
Does the reported hashrate match your mining software? Also, on the graphs page check the "Local Rate" vs "Local Rate Reflected in Shares". If LRRiS is lower than LR, than you have just had bad luck and it should even out with time.
Yeah, it takes quite a while now because the difficulty shot up after the upgrade. I forget how many days it took my 15GH to reach optimal, but I felt like it was near a week.
When is this round going to end
Seeing as my nodes have had very bad luck the last couple of days (2.2hrs to share, 6 shares in the last 48 hours!) and my payout has dropped to under half what it was a day ago, I'm predicting a bunch of blocks in short succession!
I've been on for 3 days now. I'm still not at "ideal" payout. Despite running at > 100% efficiency. Everyone else seeing this? Running around 5gh/s.
M
oh, check out this beast:
If you're gonna keep posting this crap, at least learn how to use a code box.Seriously, how difficult is this?
If you're complaining about the length, then surely something like
this
would be better
Quote
Again, most punished shares are good shares turned block-stale by a new block. That means with hash < block target, they would have been a valid block at the time they were found.
Yeah, I didn't notice that/pick up on that myself until that one share that was 20 seconds prior to block still being 'punished'.
Jump to: