It seems it works fine without failover-only and the latest cgminer versions on my setup: as long as the P2Pool node is fast enough I guess you don't need failover-only (it may be a worthwhile precaution to add it though).

hopefully, i'm fine without tweaking anything, 121 efficiency here, but it still say orphaned 0, is this a problem?
another problem is that the last version of p2pool don't work for me, it say:"error bitcoin version to old, upgrade to 0.5 or newer!", but i have already 0.8.1 version...

btw, i'm mining the same amount of BTC guild for now, i hope i can make more

no, no litecoin here, how can i run the 3.1 without the error, saying that i have a old version?

dead link

With bfgminer: does --dyn-gpuinterval <number> override --intensity? Is dyngpu the equivalent of saying "i want my desktop to have no less than 1000/<number> frames per second"? I set the option to the recommended 50 and it felt like everything onscreen was lagging. Intuitively I put it at 20fps and figured out it may be that. So then I changed the interval to 16(which is the rounded result for 60fps) and everything went back to normal. How does this impact my mining though?

I always find it weird how my P2Pool hashrate keeps fluctuating even in idle, sometimes reaching as high as 280Mh/s or dropping as low as 110Mh/s. I have my miner set up as recommended for my card. Is there anything I can do about it or is this not the miner/setup's fault and rather p2pool's?

what this line really do? what is the benefit?
-Q 0 -g 1 --intensity d --gpu-dyninterval 50

with this line, my intensity is set to 9, but i found that intensity 7 is the best for 7950

with intensity 7 i mine 575 mh, instead with int 9 only 550

above 9 nothing change, the max is still 575

Given the extreme bitcoind tunings seen in the P2Pool thread that would hurt everyone's income I added a more detailed bitcoind tuning guide designed to give optimal getblocktemplate latencies.

Update: new FAQ entry for low memory (~1GB) server.