Makes no sense to move to p2pool, aside from trying to capitalise short term on the ghash '51% attack" hype. which has largely faded away, and besides been widely misinterpreted..
Pool Luck(?) (7 days, 30 days, 90 days): 134.5%140.9%109.1%
Totally makes no sense.
block solving is inhomogenous poisson process and you are gonna get noise and variance anyway..p2pool 7 + 30 day luck is good, but wind can change & on long enough timescale it's not prudent to focus on short term statistics unless you like to gamble, graph i posted is monte-carlo simulation smoothed with 10m trials
Solo mining with 0.01% of the hashrate, 50% chance to get < 32
BTC, 10% chance of > 65
BTC and beleive it or not 5% chance of getting 0..
instead if the same miner joined a pool that controls 0.1% of total net hashrate (they have 10% of that pools workers) 90% chance of earning > 26
BTC, 50% chance of earning > 35
BTC 10% of earning > 44
BTC as you can see above p2pool like setup has a higher chance of higher earnings, it also has higher chance of lower earnings. whereas variance is reduced on a larger pool meaning less chance of low earnings, less chance of high but more predictable overall and therefore more suitable for investors wanting stable returns.
Your math has some serious issues.
It is NOT prudent to solo mine unless you have 1%+ of the network. While peta has that at the moment, they wont in short order.
You should educate yourself on p2pool before you dismiss it with scary charts that mean absolutely nothing.
P2Pool was designed to be more efficient than standard mining. How? Instead of getting a fresh bite of the apple every 10 minutes, every share you submit is eligible to be part of a block. I am feeling generous so I will copy/pasta an earlier post of mine on the subject.
P2Pool has broken the 1phs barrier, add to that the "luck" being good at the moment, and it should act like a gravity well pulling more hashrate towards it and for the time being the luck and therefore the earnings.
Found this thread on p2pool.
https://bitcointalksearch.org/topic/a-guide-for-mining-efficiently-on-p2pool-includes-fud-repellent-and-faq-153232I think this covers it. From that thread.
What matters for good P2Pool results: low latencies
On average a miner on a classic pool needs to react to a new coinbase every 10 minutes. Every 10 minutes a miner on any pool can submit a share based on a block that isn't the last one anymore. This is wasted effort: it doesn't help generate the next block in the chain and the pool suffers from this. Most pools reject such work and ignore it when they compute miners' rewards.
Miners are often separated from their pools by long-distance networks with tens or hundreds of milliseconds of latency. This means that every 10 minutes a miner on a normal pool is wasting its efforts for at least tens or hundreds of milliseconds. This is why there are rejects even on properly tuned classic setups: for 10ms of latency between miner and pool on average you should expect 0.01/(60*10) = 0.0016%:
Latency Expected rejects
10ms 0.0016%
100ms 0.016%
1s 0.16%
Conclusion: on a traditional pool, relatively high latencies aren't such a big deal.
On P2Pool, the tracking of the proof of work is implemented by a sharechain which mirrors several properties of the Bitcoin blockchain:
A share is a proof of work with a given difficulty
A share uses the previous share in its input to make a sharechain like blocks do to build the blockchain
It builds on a block template given by a Bitcoin node: a share hitting the Bitcoin difficulty can become a block too
It's difficulty is dynamically adjusted to maintain a fixed average rate of share generation (one every 30 seconds)
The last point means that having a low latency is more important for a P2Pool miner than a miner on a traditional pool. Pay attention to the fact that a share being submitted too late to enter the sharechain can still produce a block so it's not wasted work (high reject rates are not a problem for global income on P2Pool unlike rejects on traditional pools). This said as the rejected share isn't in the sharechain it won't count as a proof of work for the purpose of distributing the pool's income.