I think it has something to do with the Varidef.
At another very large scrypt pool I used to run LTC I have noticed that my diff never goes higher than 700 and then all my miners runs max out around 42-44 Mhash pr machine.
But when running LTCD my miners run on avrage 37-39 Mhash, so I think varideff kills a lot of hash.
I could be nice if best pool hat different ports for different diffs like : 700, 1024,2048 and so on.
At another very large scrypt pool I used to run LTC I have noticed that my diff never goes higher than 700 and then all my miners runs max out around 42-44 Mhash pr machine.
But when running LTCD my miners run on avrage 37-39 Mhash, so I think varideff kills a lot of hash.
I could be nice if best pool hat different ports for different diffs like : 700, 1024,2048 and so on.
Vardiff shouldn't be a problem. But it depends on hashrate. If you have large hashrate or large rented rigs on single worker, vardiff should start with much higher value.
That's why we've opened 2 ports on each of our scrypt stratums High (>512) and Low VarDiff.
The correct hashrate is what you see at your miner side. Pool calculates average hashrate based on submitted shares in last minute, which is not always accurate
Strange, since how come i have almost no HW errors at Coinotron with diff 700 and Max Hash and when running at Best I get lots of HW errors and lower Hash. Miners are Zeus Lightnings running with PI´s, so same config for both pools ?
I noticed the vardiff adds HW errors..... go back to the 3015 instead of the 3315, fixed my issues. we need to address this to the pool....
only 15 blocks 
