yep, that did it, back into a good range now - thx

what is your HW rate like at this frequency? I had mine sitting at 275 with a HW around 4%. I could not reduce this even though I walked the timeout from 40 through to 55, so now mine is sitting at the default 250, with an almost 0% HW (one machine has been 0% for the last three days) I want to get as close to 275 as possible and I know some of the defaults just do not work (300 for example give me a very very low hash rate and high HW)

Hi all,

maybe I can get some answers here, been searching for a while and no answers yet.  

have been trying to run p2pool (BTC) for a couple of months on OSX 10.9.5, latest versions of both p2pool and bitcoin-qt. Biggest issue is getblocktemplate latency, the graph looks like a sawtooth wave and goes from a latency of about 1.3s to 3-4s. restarting bitcoin-qt drops it down to 500ms but it soon builds back to around the 2s mark (in about an hour and half).

tried various resolutions, running from ram disk, ssd, another (more powerful mac pro) machine, downgraded to earlier version of OS X (10.7.5) but to no avail, still high latency.

thought about running it under windows (no I won't go there - I hate windows more now than when I started to install p2pool) then I went to linux (opensuse)

I have now been running p2pool successfully on linux for three days now, the getblocktemplate latency sometimes spikes to around 300-400ms but averages 130ms! amazing.

what leaves me puzzled is that I am using exactly the same hardware (dual boot mac pro) which leaves me thinking that the issue is with OS X and bitcoin-qt, and since I prefer to use OS X, does anyone know a way to reduce this latency under OS X, or do I need to find another way to run the wallet? does anybody think it is a bitcoin-qt issue?

any one else have this problem on OS X and been able to fix it? love to hear from you if you have.

before i forget, I mined another alt coin using p2pool for about a week in OS X, the wallet was a qt wallet and the getblock template latency was around 250ms, so the high latency only appears to be with Bitcoin. any help would be appreciated.
 
Regards
Pallol.