Diagnostic: Hashrate drop triggers

The hashrate drop triggers audit is available under the activity tab in the diagnostic and shows the current grade from the data obtained yesterday and a small historical chart for the performance of the last week. The grade is determined depending on how many hashrate drops triggers were fired. The more triggers per worker, the lower the grade.

 

Triggers are the most important mechanism that is keeping your mining operation in good health. However, firing too many triggers just isn't efficient.

Hashrate drops are compared through the worker's statistics data and checked every 10 minutes. The most recent detected hashrate is compared with the median value of the last hour (so last 6 entries in the worker's statistics, since the data is saved every 10 minutes). We decided to compare recent hashrate with median hashrate as median value isn't as sensitive to outliers as the average value. You can do several different actions for the hashrate drop trigger: restart mining client, reboot the machine, shut down the machine, stop mining, start mining, and call a webhook.

If you are getting too many hashrate drops triggers, this could be because of the following reasons:

  • You are mining the algorithm with frequent hashrate changing (for example X16R, X16Rv2). Try setting the hashrate drop % setting to a higher value.
  • One or more of your GPUs or ASIC boards are getting frequent interruptions, which makes the total hashrate lower. Examine your hardware.
  • Your rig or ASIC is having connectivity issues with the pool and is hashing with 0 H/s. Examine the status of your worker on the pool.