Quote from: buonleloi on November 11, 2018, 01:42:03 AM

Yes, I can confirm that some regions are bad now ie. West US 2
But hash also drop a lot for other regions. Seem not optimize good for CPU yet.

One tip for you, set huge-page enable to your script that also get more hash.
http://prntscr.com/lguowu

So there was a bug in my autotune-feature for the thread-configuration. Apparently somehow this didn't have a noticeable effect with the pre-fork-algo, but since the fork the resulting hashrate is much worse.
So after fixing the bug the hashrate for 10 instances of F2 is back to around 1.4kH-1.6kH, and it does not seem to be dependent on the region so much anymore.

In order to activate the fix for your miners you can either restart your pool (scale to 0, then scale back to e.g. 10 instances) or you just wait for ca. 3 days (after running for 3 days the miners will fetch the latest version of the script from github).