1.What is the calculation method of mining pool hashrate and local hashrate?
1. In order to avoid too much fluctuations on displaying the real-time hashrate, the real-time hashrate is the average value calculated from last 15 minutes. The local hashrate displayed by the miner is usually updated every second, so there will be difference between two real-time hashrate value.
*You can often see the local hashrate is displayed as a horizontal straight line on the chart. This is usually due to the optimization of the hashrate chart by the mining software. Under normal running conditions, the hashrate of the miner can never be a horizontal straight line without fluctuations.
2. The local hashrate of the mining machine usually shows the unaffected hashrate, while in the mining pool shows the actual value after the effect of rejection and invalidity (usually due to bad network or overclocking) and fee from software. So there will be differences.
2.The hashrate difference between pool and local is bug. How to check and locate the problem?
Firstly, you need to find the specific miner that have big difference between the local and pool, then check its log.
The methods to check logs for different machines are following:
The following takes whatsminer as an example
Click Status, you can see the log information in CGMiner API Log, System Log, and Miner Log in the drop-down box.
Click Status, CGMiner Status in the drop-down box, this page contains information such as hashrate rejection rate, machine restart log, etc.
Graphics mining machine
First, you need to confirm what OS you are using, or the mining kernel, etc.
Check the miner, select the ⛏ symbol on the upper right, and click the mining log
According to the feedback from our users and the confirmation of log data, the hashrate deviation percentage between local and pool is within 3%.
The main reasons for the hashrate gap are:
- Fee, as shown in the figure below, LolMiner 0.7%, Gminer 0.65%, T-rex 1%, PhoenixMiner 0.65%, Nbminer 1%,
- Display false hashrate. As seen from the last column of the figure below, the displayed numbers are basically 1% above the actually value. According to the recommendation of HiveOS, there are obvious hints that many kernels have false hashrate about 2% higher.