Quote from: Devious on February 18, 2013, 02:35:08 PM

The stale and unknowns are WAY too high, what's going on? I thought this was being addressed? 19% stale is not on my end, I've got 50MB fibre with a 32ms ping time, and I keep getting pool not providing work fast enough. If this can't be addressed it makes no sense to stay.

[2013-02-18 08:32:44] LONGPOLL from pool 0 detected new block
[2013-02-18 08:32:47] Rejected 006bb902 Diff 608/31 GPU 0 (prevhash-stale)
[2013-02-18 08:32:47] Rejected 0445a806 Diff 59/31 GPU 1 (prevhash-stale)
[2013-02-18 08:33:02] Rejected 01f4d841 Diff 130/31 GPU 0 (unknown-work)
[2013-02-18 08:33:03] Rejected 062b5f13 Diff 41/31 GPU 1 (unknown-work)
[2013-02-18 08:33:05] Rejected 01e16d7e Diff 136/31 GPU 1 (unknown-work)
[2013-02-18 08:33:08] Rejected 037ed51c Diff 73/31 GPU 0 (unknown-work)
[2013-02-18 08:33:09] Rejected 048fa180 Diff 56/31 GPU 0 (unknown-work)
[2013-02-18 08:33:10] Rejected 025d4668 Diff 108/31 GPU 1 (unknown-work)
[2013-02-18 08:33:19] Rejected 03c5e4c7 Diff 67/31 GPU 1 (unknown-work)

We do have some new hardware in the works. It'll be a week or two before it's deployed.

This is what I see on the site right now:

Pool Hash Rate   80.716 MH/s
Pool Efficiency   96.20%

Few mins later, reloaded the pool stats page, looks like this right now:

Pool Hash Rate   81.845 MH/s
Pool Efficiency   98.05%

Seems pretty good.

A few minutes later:

Pool Hash Rate   81.492 MH/s
Pool Efficiency   80.57%

Ugh... but... Ah! We also found the last block just a minute ago. Maybe the drops are happening on the round boundaries. That would explain the spikes in unknown-work? If you're submitting work for a block that was just solved? Your log seems to confirm that theory. LP new block found, then all work rejected for a minute after that?

Cheers.