Foreign exchange EA running maintenance: What do you care to run multiple accounts on a VPS?
For additional checklists related to foreign exchange Ea running maintenance: what do you care to run multiple accounts on a VPS, visit the [EA Rebate trading academy](https://www.earebate.com） and validate the process in a demo environment.
For testing around “What to look at in running multiple accounts on a VPS”, reference is made to [EA Rebate's EA and Platform Education](https://www.earebate.com) Additional check items, which should ultimately remain in the program log and actual account conditions.
Multiple accounts usually require the installation or copying of a separate transaction platform directory to avoid configuration, log and EA files. Each example should have a clear name and record the corresponding account and server.
Simultaneous operation increases the use of memory, processors and network resources. If VPS resources are insufficient, the platform may be Garden or stop responding. Examples should be progressively increased and the use of resources monitored.
Do not allow the same strategy to duplicate the total risk of exceeding the plan in multiple accounts due to configuration errors. A list of accounts can be established to record EA versions, varieties, parameters, risk caps and recent inspection times.
Why can't we just copy one shortcut?
The platform may share configurations, templates and logs if multiple shortcuts still point to the same data directory. A single version of the version could affect all accounts and even load the parameters of one account to another. A more conservative approach is to use a stand-alone installed and data catalogue for each example and to name it as “broker - account number end - use”. Prior to relocation, it should also be confirmed whether the license allows for the operation of multiple examples or accounts.
Resource planning cannot be limited to opening the platform. The low average CPU occupancy does not mean that peaks will not occur when the behavior is intense. Processors, usable memory, disk space and network connections should be monitored and upgraded and restarted.
Multiple Account Checklist
- Whether or not the correct server and account number is entered in each instance;
- The consistency of the suffix, the size of the contract and the smallest lot size;
- Whether the EA version, parameter documents and transaction identifiers are unique;
- Whether a single account risk is added to the portfolio ceiling;
- (b) Whether the chart and automatized traffic status can be restored once the platform is restarted;
- Whether logs, backups and alerts can be located in specific instances.
If the 10 accounts operate the same direction strategy, the risk will not naturally be dispersed over the 10 platforms. It should be managed with a view to both the level of risk and the consolidation of all accounts.
