Running one EA on one terminal is simple. Running five EAs across three brokers on multiple prop firm accounts while keeping everything stable and responsive — that is where VPS planning matters. Get it right and you have a diversified, automated trading operation running around the clock. Get it wrong and you have a server that freezes at the worst possible moment.
This guide covers the exact resource requirements for running multiple EAs, how to determine when you need to upgrade, and the technical tricks that let you squeeze maximum performance from your VPS.
Resource Requirements Per Terminal
Every MetaTrader terminal consumes three resources: CPU, RAM, and disk I/O. Understanding the baseline for each lets you calculate exactly how many terminals your VPS can support.
RAM Usage
RAM is the most common bottleneck for multi-terminal setups. Here are realistic memory figures based on our measurements:
| Configuration | RAM Usage |
|---|---|
| MT4, no EAs, 2-3 charts | 80-120MB |
| MT4, 1 EA, 4-6 charts | 150-250MB |
| MT4, 2-3 EAs, 8+ charts with custom indicators | 250-400MB |
| MT5, no EAs, 2-3 charts | 150-200MB |
| MT5, 1 EA, 4-6 charts | 250-400MB |
| MT5, 2-3 EAs, 8+ charts with custom indicators | 400-600MB |
| Windows Server baseline (OS + services) | 1,200-1,800MB |
MT5 uses significantly more memory than MT4 due to its more advanced architecture, multi-threaded strategy tester, and deeper market depth data. If you are running MT5, plan for roughly 50-80% more RAM per terminal compared to MT4.
📊 Key Stat: A VPS with 4GB RAM provides approximately 2,200-2,800MB for MetaTrader after Windows takes its share. That supports 2-3 MT4 terminals comfortably or 2 MT5 terminals. Going beyond that triggers memory swapping, which devastates execution speed. See our troubleshooting guide for details on how memory swapping affects EA performance.
CPU Usage
CPU demands depend heavily on what your EA does:
- Simple EAs (moving average crossovers, fixed-rule entries) use minimal CPU — 1-5% per terminal during active trading
- Tick-based scalping EAs that process every incoming tick use 5-15% per core during volatile sessions
- Complex EAs with neural networks, heavy calculations, or multi-timeframe analysis can spike to 20-40% per core
For most traders running standard EAs, CPU is not the bottleneck — RAM is. But if you run computation-heavy strategies, CPU matters. Two dedicated cores handle 3-4 terminals with standard EAs. For intensive strategies, plan one dedicated core per 1-2 terminals.
Disk I/O
Each terminal writes logs, history data, and journal entries to disk. The I/O per terminal is modest (a few MB per hour), but when multiple terminals write simultaneously, slow storage creates queuing delays. NVMe SSD storage handles multiple terminals without issue. Spinning drives or budget SATA SSDs can become a bottleneck with 4+ terminals.
Plan Recommendation Matrix
Based on the resource requirements above, here is a practical guide for choosing the right FXVPS plan:
| Your Setup | Terminals | Recommended Plan | Specs |
|---|---|---|---|
| 1-2 EAs, 1 broker, 1 account | 1-2 | Core ($29/mo) | 1 vCPU, 2GB RAM, 40GB NVMe |
| 3-6 EAs, same or different brokers | 3-6 | Pro ($39/mo) | 2 vCPUs, 4GB RAM, 80GB NVMe |
| 6+ EAs, portfolio trading, copy trading master | 6+ | Scaling ($79/mo) | 4 vCPUs, 8GB RAM, 160GB NVMe |
These recommendations assume standard MT4 EAs with moderate indicator loads. If you run MT5 exclusively or use resource-intensive EAs, shift one tier up.
View full plan details on our pricing page.
The Portable Mode Trick for Multiple Instances
Here is a situation many traders face: you want to run two accounts with the same broker on the same VPS. The problem is that MetaTrader only allows one installation per broker by default. If you install it twice, the second installation overwrites the first.
The solution is portable mode, which tells MetaTrader to store all its data in the installation folder instead of the AppData folder. This lets you run multiple independent instances from different directories.
Setting Up Portable Mode (MT4)
- Install MT4 from your broker to the default location (e.g.,
C:\Program Files\Broker MT4\) - Copy the entire installation folder to a new location (e.g.,
C:\MT4-Account2\) - In the copied folder, create an empty file called
portable.ini(not portable.txt — make sure file extensions are visible) - Launch
terminal.exefrom the copied folder - MT4 starts in portable mode, storing all data locally
You now have two independent MT4 instances that can run different accounts with the same broker simultaneously.
💡 Tip: When using portable mode, each instance’s data folder is its own installation directory. EAs, indicators, and templates are NOT shared between instances. If you update an EA, you need to update it in each portable installation separately. Create a batch script to copy updated .ex4 files to all instances at once.
Setting Up Portable Mode (MT5)
MT5 uses the same approach, but the file is called portable (no extension):
- Install MT5 from your broker
- Copy the installation folder to a new directory
- Create a file named
portable(no extension) in the root of the copied folder - Launch
terminal64.exefrom the copied folder
For a deeper dive into running multiple MT4 installations, see our dedicated guide on installing multiple MT4 platforms with the same broker.
Optimizing Multiple Terminals for Performance
Running multiple terminals efficiently requires more than just having enough RAM. Here are the optimizations that keep everything running smoothly.
Reduce Chart Count
Every open chart consumes memory and CPU cycles for rendering. If your EA only needs the H1 chart for EURUSD, do not leave the M1, M5, M15, and D1 charts open as well. Each unnecessary chart wastes 10-30MB of RAM and generates rendering overhead.
A single EA typically needs one chart — the timeframe and symbol it trades on. Close everything else.
Disable Unnecessary Visual Elements
In each terminal:
- Turn off the news feed (Tools > Options > Server > uncheck “Enable News”)
- Close the Market Watch window if you do not need it (or reduce it to only the symbols your EA trades)
- Disable sound alerts if you are not monitoring the terminal visually
- Remove grid lines and unnecessary chart objects
These individually save small amounts of resources, but across 5+ terminals the savings compound meaningfully.
Use Offline Charts for Non-Trading Analysis
If you want to monitor a pair on a timeframe your EA does not trade on, use offline charts (MT4) or custom symbols (MT5). These do not maintain a live data feed and consume far less resources than regular charts.
Stagger Terminal Startup
When the VPS boots (after a restart or maintenance), do not launch all terminals simultaneously. Each terminal connecting to a broker server and downloading history data generates a burst of CPU, RAM, and network usage. Five terminals launching at once can spike resource usage past safe limits for several minutes.
Configure your startup scripts to launch terminals with 30-60 second delays between each one. This spreads the initialization load.
✅ Best Practice: Create a Windows startup script (batch file in the Startup folder) that launches terminals sequentially with
timeout /t 30between each launch. This prevents the resource spike that causes terminals to freeze or fail during boot. For setup details, see our MetaTrader auto-startup guide.
Monitoring Resource Usage
Once your multi-terminal setup is running, monitor it regularly to catch problems before they affect trading.
Task Manager Checks
Open Task Manager (Ctrl+Shift+Esc) and check:
- Total RAM usage: Should stay below 80% of available memory. Above 85% and you risk swapping.
- CPU usage per terminal: Should stay below 20% per terminal during normal operation. Spikes during news events are expected but sustained high usage indicates a problem.
- Disk activity: Should be minimal. Sustained disk activity suggests a storage bottleneck or a background process competing for I/O.
Performance Monitor
For more detailed tracking, use Windows Performance Monitor (perfmon):
- Open perfmon.msc
- Add counters for Memory > Available MBytes, Processor > % Processor Time, and PhysicalDisk > Avg. Disk Queue Length
- Let it run during a trading session to get baseline data
- If available memory drops below 500MB, CPU exceeds 80%, or disk queue length exceeds 1.0, you are at capacity
When to Upgrade
Upgrade to the next VPS plan when any of these conditions persist:
- RAM usage consistently above 80%
- CPU usage above 70% during active sessions
- You need to add another terminal but the current plan cannot support it
- MT4/MT5 execution times (visible in the Journal tab) have degraded
Do not wait until the VPS is at 100% capacity. Running at 90%+ leaves no headroom for volatility spikes, when every terminal demands more resources simultaneously.
Multi-Broker and Multi-Account Strategies
If you are running EAs across multiple brokers (common for diversification or prop firm management), each broker typically requires its own terminal installation. Here is how to organize it:
C:\Trading\
├── Broker1-Live\ (standard install)
├── Broker1-Account2\ (portable mode)
├── Broker2-Live\ (standard install)
├── Broker2-Demo\ (portable mode)
└── PropFirm-Eval\ (standard install)Label directories clearly so you know which terminal is which. A common mistake is accidentally running a live EA on a demo account (or vice versa) because the terminals are not clearly identified.
The Cost of Getting It Wrong
Running more terminals than your VPS can handle does not crash the server — it degrades performance gradually. Memory swapping starts silently, tick processing slows down, and execution quality drops across all terminals. You might not notice until you review trade logs and realize slippage increased across the board.
The cost of running three EAs on a VPS that can only handle two is not the price difference between plans — it is the cumulative execution degradation across all three EAs. Spending $15/month more for the right plan prevents hundreds in slippage losses.
Getting Started
If you are planning a multi-terminal setup, start with the right plan:
- 1-2 terminals: Core plan ($29/mo, 1 vCPU, 2GB RAM)
- 3-6 terminals: Pro plan ($39/mo, 2 vCPUs, 4GB RAM)
- 6+ terminals: Scaling plan ($79/mo, 4 vCPUs, 8GB RAM)
Not sure which plan fits? Start with a $1.99 trial on the Core plan, set up your terminals, and monitor resource usage for a week. If you need more headroom, upgrading is instant and does not require reconfiguring anything.