firstly, thank you for a great service. I have been using MPH for some of its individual pools for a while now, just experimenting initially but lately I have used your monero pool all the time because it is the only one I can find with a pool server close to me with a decent ping time. I live in Australia and use asia1.monero.miningpoolhub.com:20580. Another good thing here is that you allow the claymore client to make an encrypted connection and thus a lower dev fee. So I am very happy with all that stuff.
I have a question though about the various hash-rate measurements available which can sometimes confuse me a bit.
For example, if I look now at my "workers" tab and add all the individual numbers together it totals 7.6 mh/s but if I then open the "dashboard" tab it shows a figure of 6.71 mh/s then changes to 8.03 mh/s.
I just did the same thing after a few minutes and the "workers" totallled to 8.725 mh.s but the dashboard showed still 8.03 mh/s.
Does this mean that the "worker's data is collected more frequently and the "dashboard" is just a longer average? If I add all of the hash-rates reported by the rigs I use it's something like 8.8 mh/s and if I look at the "graphs" that is appromimately where my graph peaks, but it looks like the average is around 8.3 - 8.6 mh/s. So does this mean that my rigs are offering 8.8 mh/s but you are not able to utilize all that hash rate all the time? I know there are random fluctuations all the time but is there any way for me to improve my settings to raise my average up to what my rigs are reporting?
ethereum, ethereum-classic, zcash, zclassic have asia server as well.
Worker's data and dashboard's data can be different because dashboard data is from regularly cached data. But worker's data is measured dynamically when you open the page.
Pool is showing just estimated hashrate. It's not easy for pool to know actual hashrate. Pool just uses some probability mathematics to measure which means it's very rough result.
I believe your rigs are working fine. my rigs are reporting like that too.
I think claymore cryptonote miner's hashrate numbers are a bit bigger than actual due to memory bandwidth. I'm just guessing.