Hi Terk,
Since joining CM I have been consistently missing around 400kh/s to 700kh/s according to my WU. I don't get this problem with middle or waffle, can you check this out for me? many thanks
1KZQ3KVfk9nABZ14A5oFR34tjrDzxPoBbu
Nothing wrong with this username from my side.
You have 2.81 MH/s accepted on average in the last 24 hours and 0.15 MH/s rejected (the site doesn't show rejected 24h avg, I checked it manually - more detailed stats are on my todo list). That means that your total hashrate detected by the pool was 2.96 MH/s on average in the last 24 hours.
I see that you have some small rig running on the Oregon server and most of your hashpower at Europe. I even double checked if it's the Oregon what's missing, because it's a similar number to what you're reporting, but everything is fine as well. I checked manually in regions databases and in the last hour you had 0.317 MH/s in Oregon and 2.638 in Europe = 2.955 MH/s combined, which is exactly what the central database and the website is reporting for your last hour (on the website the main dial rounds it to 3.0, but on the 24h chart when you mouse over the point it's 2.9547.
What is your WU? Is it far from the 3 MH/s what the site reports as your average 24h accepted+rejected? The most common mistake that people make is to check one hour average from the webpage, which is always an estimate and is vulnerable to variance.
If the difference to the 24h avg is really that high, then did you have any MH/s logged on your backup pool? It's possible that your miners disconnect and spend some minutes on another pool? I can't think of anything else.
Thanks for the reply, I understand you must be busy.
WU is around 3.4MH/s (1.9 on one rig and 1.5 on the other) but less at night (GMT) as my neighbour's bedroom is above the rig's so I underclock my 290's to keep the noise down.
I know the estimates aren't exact, yet like I said I don't get this issue elsewhere, but profits were good and I figured it was normal for CM, but then I saw people's screenshots and realised it was just me.
It's not that some Mh/s is tied up in another backup pool as I have had this issue from day one with CM and it doesn't resolve if I restart my rigs.
It's weird as I don't see anyone else with this problem and had my fingers crossed it would be something obvious on your end.