When the reject rate increases, the total hashrate drops. At first I was thinking it was that people were using --no-submit-stale, but that shouldn't account for that much hashrate loss.
I've talked way too much about difficulty in this thread. It doesn't play a factor.
Hash rate drop
- Assume 100 miners connected to pool. They are always connected and always hashing.
- Pool switches to low diff coin (all miners still connected)
- Miners start to get "new block" "new block" "new block" (in my experience this can go on for 10 minutes without submitting a share)
- Hash rate on pool drops (not because miners aren't mining -- they just can't submit shares fast enough prior to a block change)
That's my interpretation of why there is a hash drop.
I have 4 7950s connected to your pool, they generally hum along between 2.4mhs - 2.6mhs on a LTC pool. Here, on the pool side by hash rate has been consistently reported as 1.9-2.1mhs. The only thing I can attribute that to from what I see on my end is the "new block new block new block" for 10 minutes without being able to submit a share, therefore to the pool it doesn't look like I'm mining.
Just my two cents, I wanted to continue to beat the dead horse. I think share difficulty has everything to do with it, but I'm of a layman viewpoint. Thanks for your hard work and I hope to see this pool get better.