Shares: 254 total (20 orphaned, 10 dead) Efficiency: 103.6%
What's wrong this picture? I'm at 11.8% stale, and I'm > 100% efficient.
I've done everything I can do to get the stale rate down, and I hover between 10% and 12%.
I've:
- changed AV to not scan bitcoin folder or p2pool folder
- changed cgminer to run on 1 thread, and 0 queue
- run p2pool on same box as bitcoin
- run p2pool on different box as bitcoin
- grab the newest version of p2pool every week or so.
I was around 5% before v8 came out.
What's going on here? Is this considered normal now?
M
were you running close to that 4% dead before? my # of dead is usually around 0-1%, but last time I tried p2pool, I was getting about 15% orphans. which has always been the main problem (for me). doesn't make a lot of sense, since my bitcoind is on a ram drive and has close to 1000 connections. probably need to use whatever the equivalent of addnode is in bitcoind to my p2pool command line to connect to the top 10 nodes or so (in ghash/s)
(uh, strayed off topic a bit i guess. your dead % looks high to me, maybe some local network issue w/ higher latency or something?)
ed:
correct me if i'm wrong, but it would work like this? person x gets a share based on work x, so now people are to have moved on to work y. 1 second later you submit your share based on work x, thus it is recognized as 'dead' by your p2pool client. for orphans, you would submit your work x and then begin working on work y (as well as anyone else that received your share). another person submits their work x a second later (not having received yours yet) and sends it to whoever they can on their peer list, and they all begin working on work z. the people that are working on work z find another share first, so then your submitted share is orphaned
so, then, dead shares would more likely be caused by local network issues or maybe CPU load or something like that, while orphans would more likely be caused by latency outside your local network??
ed2:
err, change the first part to say that you submit your share based on work x, but your p2pool client already recognizes that there's a prior valid solution
