In the time since P2Pool's original announcement it has evolved considerably.  I thought  having to wade through hundreds of pages of inapplicable cruft about old versions of the software to get to useful information was a disservice to people here, so I split off the old discussion to a separate archival thread.

P2Pool has come a long way since its humble beginnings: It's now a completely realistic solution for a great many miners. The software is still rapidly developing but it is reliable, featureful, and, of course, P2Pool is critical for the health and welfare of the Bitcoin system: Our trust in the Bitcoin system depends on it being highly decentralized. P2Pool prevents the centralization that non-distributed pools create.  This is important enough to people that P2Pool miners are currently being paid by Bitcoin users to participate.  P2Pool pools payments but mining decisions are still left to all the miners just as bitcoin was intended to work.

This "pool" (really a decentralized/distributed network just like Bitcoin) is still attractive even for people who aren't thinking about the health of Bitcoin overall. P2pool's decentralization is accomplished without compromising on miner profits and, unlike solo mining, while still allowing stable income. The things which p2pool can't do, like provide the utmost low variance (PPS) are offset by the lack of fees and by removing the risk of cheating by pool operators (which is almost undetectable if only done in moderation).

P2Pool isn't ideal for low speed (e.g. CPU) miners, and may never be— but it's absolutely a no brainier for anyone who would even consider solo-mining and a good majority of the people in between.

I'm personally really happy about the new built in per-worker graphs:


I hope to see more useful monitoring features in the future.

What is the likely cause of this?


Fairly frequent.  P2pool and bitcoind are running on the same system.

Thank you eja, I have had many stales and now just watched the CPU spike. I'll try on a different system.

I don't quite understand something that I was asking about in the thread that was just closed.

Which is better to be using?

Nightly snapshots from here:
https://github.com/forrestv/p2pool/zipball/master

Or the latest executables scattered about?

----------

Also, what are the dependencies for the graphs?

I have all these:
http://bitcoin.stackexchange.com/questions/2640/p2pool-crashes-the-bitcoin-client/2643#2643

but the graphs do not work, from what I have read it seems the problem is not having rrdtool, however I'm having trouble finding a current win32 version of rrdtool, it is also not in activestate.

Thanks

Watching

Re: Frizz23 if p2pool was running the subsidy payments should have came in. How are you launching p2pool? Are you using -a <address> with the same address every restart?

installed from GIT:

http://127.0.0.1:9332/graphs/

didnt find an easy way to install rrdtool on windows

looking for a way to check my hash rate remotely

does the higher acceptance rate of the git version affects client in any way? if a lower difficulty solution is found does it still look for another one (because the lower difficulty solutions dont really count as shares)?

It's already done. You don't need them to all be verified to mine... That's a bit confusing.

So you need to have several bitcoind's running with a different user pass in each?

I get this also about once every 5 minutes.


I have noticed it does occur when the cpu spikes to 100%.. would a sempron 145 and 2 gigs of ram be considered underpowered?