Specifications need context
Hashrate, device power, and energy efficiency belong together. Compare the exact hardware variant under comparable operating conditions, not a headline from one listing against a different variant's best result. Keep the algorithm attached to the comparison.
The ASIC efficiency guide explains J/TH through worked examples and shows why a fleet ratio should be calculated from compatible totals rather than a simple average of device ratios.
Build the inventory first
Record a stable device identifier, model variant, location, firmware version, supported cooling configuration, and service owner. Keep configuration references separate from secrets. A friendly display name should not be the only link between a physical machine and its measurement history.
When a device is replaced, retain the distinction between the old and new hardware. When it moves, preserve its identity while recording the location change. These small decisions make later incident reviews far easier to interpret.
Observe before changing settings
Establish a baseline with matched power and hashrate observations, timestamps, and known maintenance events. Verify that the collector distinguishes missing readings from observed zero values. A stopped device should not display a fictional zero-cost efficiency result.
Use only supported operating configurations and preserve a recovery path for authorized changes. This site does not offer remote control, firmware downloads, overclocking commands, or a universal temperature limit.
Plan the complete cooling path
Equipment, circulation, heat rejection, access, and maintenance form one system. The air versus immersion guide organizes questions for a qualified design review rather than offering a generic conversion recipe.
A device-only efficiency figure is not automatically a whole-site efficiency figure. Define where power is measured and what auxiliary equipment is included before comparing architectures.
Keep observation separate from control
A monitoring dashboard needs data, not unrestricted permission to change equipment. Where supported, use distinct identities for telemetry and privileged operations. Protect administration interfaces rather than exposing them publicly for convenience.
Our security guidance describes that separation and the boundary of the public demonstration. The sample API contract gives developers a small, explicit format to practice against without touching real devices.