Recommendations and Best Practices

1. Implementation Strategy

• Testing on Small Groups: Always test new settings or firmware versions on 10–20 devices before scaling to the entire farm.
• Gradual Updates: When updating software on a large fleet of devices, divide the process into parts (25–50%) to ensure the stability of each group before proceeding.
• Time Planning: Perform critical operations during periods of low network activity or in the "off-season" to avoid infrastructure overload.

2. Optimization and Automation

• Using Templates: Create and save templates for typical Pool and filter settings, assigning them clear names (e.g., Pool_BTC_USA).
• Batch Processing: When working with selections of more than 1000 devices, always use batch mode to smooth out voltage spikes and reduce network load.
• Regular Audit: After completing mass actions, run the "Rescan" function and check the final reports to identify devices with a 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 disregard devices that reported an error during a mass operation; analyze the causes (timeouts, authorization) and resolve them separately.
• Updating Without Batching: Mass simultaneous firmware file uploads to the entire farm can lead to network equipment failures.

4. Useful Tips

• Skipping Confirmations: To speed up operations, hold down the Ctrl key when clicking a command button to skip the confirmation dialog.
• Isolation for Errors: Use the isolation mechanism (Ctrl/Cmd + I) to work with problematic devices separately from the main list.