Quote from: Mikestang on March 04, 2016, 11:45:08 PM

Quote from: DrHaribo on March 04, 2016, 10:26:59 PM

At Bitminter only a new bitcoin block makes old work get rejected.

That is not what I'm seeing, for example here is a reject that just happened as a result of the work restart:

I meant that namecoin work flushes do not cause stale work at Bitminter. I was talking about the work flush (restart), not the disconnects.

About the disconnects, let me know if us2 or eu1 works better.

Quote from: Mikestang on March 04, 2016, 11:45:08 PM

Quote from: DrHaribo on March 04, 2016, 10:26:59 PM

But yeah, have a look at the worker options and disable "Merged mining stale flush". That should reduce the frequency of those.

Done, I unchecked that box for all my workers. What are the pros/cons of that check box? I would hope to eliminate work restarts outright rather than reduce the frequency. Oh, and the screen cap immediately above was taken 15 minutes after I made this change, so it did not appear to eliminate it.

That checkbox makes the server not flush work when there is a new namecoin block. It will still flush work when there is a new bitcoin block and in some other (very rare) cases. Using this feature will cause much more stale namecoin work, but namecoin income isn't that high at the moment anyway.

Quote from: Mikestang on March 04, 2016, 11:45:08 PM

And no explanation why my gekko stick only mines here at 4-5GH instead of 12-14GH? It's very odd and I can reproduce easily, just change from kano to bitminter back and forth and note the speed difference.

That is indeed odd. Does it go up and down a lot, or is it 4-5 GH/s all the time?