Do not use Eligius, I had the same problems. The miner doesn't flush the old work when asked and continues to submit them to the pool.
It seems P2Pool is also impacted.
If MINER "doesn't flush the old work when asked and continues to submit them to the pool"It seems P2Pool is also impacted.
than it doesn't matter what pool to use because that's miner problem
I just changed pools, the firmware is the same.
which pool are you using now?
I'm mining @ slush... and this is what I get for a block that last for only 7 minutes: 0.08573308 btc with 2 jups.
usually I got something like 0.19/0.24.
every time we found a block very early I got less than I use to have with longer block because "The miner doesn't flush the old work when asked and continues to submit them to the pool."
every time stratum notify a new block this is what I get:
Code:
[2013-10-09 19:42:36] Stratum from pool 0 detected new block
[2013-10-09 19:42:36] KnC running flushwork
[2013-10-09 19:42:36] KnC: accepted by FPGA 1 works, but only 0 submitted
[2013-10-09 19:42:36] Rejected 00815da7 Diff 506/326 KnC 0 (Job '26017' not found)
[2013-10-09 19:42:36] KnC running flushwork
[2013-10-09 19:42:36] KnC: accepted by FPGA 1 works, but only 0 submitted
[2013-10-09 19:42:36] Rejected 00815da7 Diff 506/326 KnC 0 (Job '26017' not found)
after those log my hasrate takes a while 10-20sec to climb up to usual level.
quoted the post where gigavps (admin of giga's semiprivate poll) confirm this behaviuor
Well Jupiters don't play well with p2pool. They remind me of the early BFL FPGAs, they are extremely slow to recover when they get new work. Anyone have any settings to to try out?
What's exact stats you're getting? How many DOA?
I am seeing higher stale rates from KNC equipment so it looks like they are not flushing work when the stratum server requests but are instead finishing old work and submitting it.
?
To add something more informative: order numbers don't play a role, payment dates do.