Note: hashrate charts may be incorrect

I discovered an issue where, under high database load, the hashrate charts may be lower than what is actually being earned. The reason for the problem is that the query is selecting shares that haven't yet been written to the database because of high load, and therefore it looks like fewer shares were submitted.

While all the shares are recorded eventually and payment is correct, the charts may be too low until Chris releases a fix in 6 hours. The fix will delay the computation of those hashrate charts by fifteen minutes, to ensure that all shares have been written before the final hashrates are computed.