Remote Proxy is a feature only intended for large scale mining operations. Remote Proxy is when a dedicated computer runs the Remote Agent application, but instead of controlling the mining on only the local computer, it will connect to a large number of miners and report the status back to Awesome Miner.
When designing a large system, the load on the Awesome Miner main application can be reduced by setting up one or several computers as Remote Proxies for making the majority of all network connections to the miners. A Remote Proxy is a standard Awesome Miner Remote Agent installation that has been configured to be used as a Remote Proxy in Awesome Miner. This feature is currently only supported for External Miners (management of ASIC miners)
Each Remote Proxy instance can be used to manage up to 10,000 miners. Remote Proxy can either run on Windows or Linux.
To configure a Managed Host to be used as a Remote Proxy, open the Properties dialog of the host via the Options dialog, Managed Hosts section, and enable Use as Remote Proxy as illustrated below.
By default all miners either don't have any Remote Proxy assigned at all, or use Local to also indicate that no Remote Proxy is used. There are two ways of assigning an External Miner to a Remote Proxy.
- Open the Properties for the External Miner and go to the Remote Proxy section
- Right click on one or many External Miners in the list of miners in the main window of Awesome Miner, and make the change as illustrated below
Automatic miner discovery
When a Managed Host is configured to be a Remote Proxy, a new configuration section will be made available - Automatic miner discovery. The discovery feature is similar to the network scan feature in Awesome Miner, but the process is automatic. A Remote Proxy can be configured with multiple IP address ranges where it will scan for new miners and automatically add them to the specified miner group in Awesome Miner. To automate the automatic configuration of new miners, a rule can be specified to be executed for all the added miners. The rule can for example setup API privileges and default pool settings on the miners.
The recommendation is to keep the number of miners per group below 1000 miners for performance reasons. The recommendation is to define multiple IP address ranges and map each range to a specific group, keeping the number of miners per group to less than 1000.