Quote from: -ck on December 12, 2015, 09:30:50 PM

Quote from: p3yot33at3r on December 12, 2015, 04:22:48 PM

Quote from: -ck on December 12, 2015, 03:46:41 PM

Quote from: p3yot33at3r on December 12, 2015, 03:04:34 PM

Edit: Ouch - that DOA rate........

Almost 3 am, but...

What's normal/good?

Mine sits at about 3% - but it's a local private node.

Yeah, don't know what to make of it. The overnight run saw 9 shares come in total without any orphans or dead but of course you need about 100 shares to get a fair idea of the real efficiency. I can understand if you move your miner away and appreciate the testing you did initially to confirm it works though, thanks.

It's been a while since I've played with p2pool though and something is really bugging me that I spot in the logs. I was wondering if anyone could answer me since my python knowledge is almost non-existent. On block changes, I'm NOT seeing p2pool immediately ask for a new block template when looking at my bitcoind logs which I have extra debugging on. Take for example this last block:

The block came in here:

Code:

2015-12-12 21:11:05.242988 UpdateTip: new best

And p2pool asked for the first newblock template here:

Code:

2015-12-12 21:11:23.387677 CreateNewBlock

Note the timestamps. There are 18 seconds between the block change and the first block template request. Now on my pool software I get a new template within milliseconds of the block update.

So here's the question. Is p2pool by design not updating immediately on block changes and hashing on stale work? Am I missing something?

edit: see Forrest's answer above...

I *believe* (and may be incorrect) that p2pool will wait for a valid share (pool wide) before sending new work @ 30 seconds on average. I recall a couple years ago discussing this with someone. As P2Pool does not subscribe to bitcoind blocknotify it is not aware of the block change...

If I am right and this is the case, setting up a blocknotify flag in Bitcoin.conf and integrating it into the code should not be to hard, but I suspect there is a reason Forrest set it up this way? (Or maybe -blocknotify did not exist then?)