try --queue 0 --scan-time 1 --expiry 1
it helps, but my s2 usually has about 100ghash of rejected
Thanks! That one change has made a bigger difference than anything else I've tried. I'm getting higher hashrates now but still see around 15% rejects at the top end (175 Ghs) with an average around 100 Ghs rejected. I'll play with those values and see if it gets any better.
That seemed to lower my hashrate and rejects by about the same amount ... was still getting > 20% ... I've given up on WH/NH SHA for the most part ... an effective hashrate of about 800 GH/s vs ~1100 GH/s (< 1% rejects) on other pools with > 100% average luck means it's just not profitable ... and this thing is barely making me $3 a day now, so downtime while I experiment trying to earn an extra few cents a day just isn't worth it ...
I do have WH set up as my primary pool, but with a price threshold about 35% higher than what the calcs say straight BTC should earn me ... if someone wants to pay an arm and a leg for SHA for some reason, I don't want to miss out on it, but I just can't make as much here with the S2 as I can elsewhere due to the massive rejects ...