Improve what you can measure honestly
Begin by checking whether the numbers you plan to compare have matching units, compatible windows, and a known measurement boundary. A device power estimate and a wall-meter reading are not interchangeable. Keep missing coverage visible in both charts and summaries.
Test a calculation by hand
Work through the hashrate guide's examples before adding a ratio to your own dashboard. Reject an invalid or missing denominator, and document whether a reported average is weighted by time. A polished card should never hide uncertainty behind extra decimal places.
Reduce operational noise
Optimization can mean making a system easier to operate, not merely changing hardware settings. Use the alert guide to separate missing telemetry from measured underperformance, define useful recovery conditions, and remove notifications that consistently have no action attached.
Keep tuning outside the demo
The public examples do not change clocks, fans, voltage, or operating profiles. Any real setting change requires equipment-specific guidance, authorization, and an appropriate validation process. Use the sample dashboard to improve measurement presentation first. Avoid turning an operational ratio into a promise of mining proceeds or a forecast based on undocumented assumptions.
