Hi, here are some thought for another hobby miner...
Yeah, it's true that, in that particular case, Quarkcoin technically had the highest profit:difficulty ratio since Dimecoin was at a low point in its rewards.
Here's a couple I just took now that Dimecoin is on the up and mining power has started getting a little nuts:
Again, Quarkcoin (at the bottom of profitability) seems to have a disproportionate amount of hashrate pointed at it considering both its profitability and its difficulty. This seems unlikely to be just a reporting error, as it has been consistently reporting a hashrate above/close to what's pointed at Dimecoin, and it isn't a sudden difficulty spike, as it's been pretty close to that diff for a long time. That all said, why would Quarkcoin end up with more power pointed at it than Dimecoin, which is both higher difficulty AND higher profitability? Shouldn't Dimecoin receive a significantly larger amount of mining power, since it is both much more profitable and can handle more hashrate?
EDIT: Watching it climb a bit now (caught it live). At
<400MH it looks like it's distributing hashrate properly.
1.4GH looks about right too.
2.1GH shows what is making me suspicious, as Quarkcoin suddenly has absorbed a disproportionate amount of hashpower as far as the numbers look to me. At
6.2GH and
5.6GH (seen in that order) I don't even know what's going on; probably just adjusting for all the hashrate suddenly coming at the pool. The
rates keep moving, but I can't help but think there's just a bit too much being pointed at the coin on the bottom. Maybe things are working entirely as intended, but the numbers I'm seeing just strike me as odd. Ah well, that's enough live hashrate recording for one night. If the numbers when the pool's under heavy load look normal to you guys, then maybe everything's fine; heck if i know
. Even if there is a bug here, it'd only ever be an issue when algos get slammed like what happens to quark lately. Despite all my bitching, prioritising the server upgrade will probably alleviate this issue (if there is one) indirectly by reporting proper numbers better so miners can switch away faster when algos get overloaded anyhow, so yeah, just concentrate on that, lol.