Recommendations and Best Practices

1. Deployment strategy

• Testing on small groups: always validate new settings or firmware versions on 10–20 devices before scaling to the entire farm.
• Gradual updates: when updating software across a large fleet, split the process into stages (25–50%) to verify stability of each group before proceeding.
• Time planning: perform critical operations during periods of low network activity or in the "low season" to avoid infrastructure overload.

2. Optimization and automation

• Using templates: create and save templates for common pool and filter configurations, assigning clear names (for example, Pool_BTC_USA).
• Batch processing: when working with selections larger than 1000 devices, always use batch mode to smooth voltage spikes and reduce network load.
• Regular audits: after completing bulk actions, run "Rescan" and review final reports to identify devices with Failed status.

3. What to avoid

• Changing pools during peak load: this can lead to temporary hashrate loss and missed shares.
• Ignoring errors: do not overlook devices that reported errors during bulk operations; analyze the causes (timeouts, authentication) and resolve them individually.
• Updating without batching: simultaneous firmware file uploads across the entire farm may cause network equipment failures.

4. Useful tips

• Skipping confirmations: to speed up workflows, hold the Ctrl key while clicking a command button to skip the confirmation dialog.
• Isolation for issues: use the isolation mechanism (Ctrl/Cmd + I) to work with problematic devices separately from the main list.