A trading VPS keeps MetaTrader and your expert advisors running when your own computer is off, asleep or on an unstable connection. Getting the size right is simple once you know what each terminal needs. This guide covers what matters in a trading server, how to size it, and how to avoid paying for capacity you will not use.
Before you start
Write down your setup:
- How many terminals you run (MetaTrader 4, MetaTrader 5 or others), and for how many accounts.
- How many charts and expert advisors (EAs) or indicators run in each.
- Whether you also use a browser, TradingView or other tools on the same server.
- Your broker's trading server location, usually listed in their documentation or support pages.
Note: This guide is about the server, not trading strategy. MdmHost does not give investment advice.
Why Windows
MetaTrader and most retail trading platforms are Windows programs. That makes a Windows VPS or a Windows Admin RDP the natural choice. You connect with Remote Desktop on port 3389, for example 203.0.113.10:3389, and see a normal Windows desktop with your terminals on it.
What to size
RAM
Memory is the main limit. Windows itself needs a few gigabytes. Each terminal then adds its own share, which grows with:
- the number of open charts,
- the amount of history data loaded (the Max bars in chart setting),
- the number and complexity of EAs and indicators.
A lean terminal with a few charts uses far less than one with dozens of charts and heavy indicators. As a rough starting point, plan around 4 GB for Windows with one or two light terminals, and more as you add terminals, charts or a browser. Measure once running and adjust.
CPU
Most EAs are light, but a few heavy indicators or many terminals reacting to the same tick at once can cause CPU spikes. Two vCPUs suit a small setup; add more for several busy terminals. Running backtests in the Strategy Tester on the same server uses a lot of CPU and is better done at quiet times.
Storage
Each terminal stores price history and logs. They grow slowly but steadily. Leave plenty of free space and clear old logs now and then.
Location matters more than size
Every order travels from your terminal to the broker's server. The shorter that trip, the lower the latency. A server in or near the same city as your broker's trading server can cut round-trip time sharply compared with a home connection on another continent.
Choose a server location close to your broker, then measure. See what is latency for how to test it.
Keep terminals running 24/7
- Disconnect, do not sign out. Close the Remote Desktop window to leave the session running. Signing out closes MetaTrader.
- Auto-start after a reboot. Windows updates or maintenance can restart the server. Set your terminals to start automatically. See auto-start MetaTrader after a reboot.
- Control updates. Set Windows Update active hours or schedule restarts for the weekend when markets are closed.
Check it works
- Open all your terminals with every chart and EA you normally use.
- Open Task Manager → Performance and watch Memory and CPU for a busy trading session.
- In MetaTrader, check the connection status in the bottom-right corner. It shows the ping to the broker's server in milliseconds.
- If memory stays above about 85–90%, reduce charts and history bars or move to a bigger plan.
Troubleshooting
- Terminals close when you disconnect: you signed out instead of closing the window. Reconnect and start them again.
- High ping in MetaTrader: the server is far from the broker. Pick a closer location.
- The server is slow with many terminals: lower Max bars in chart in Tools → Options → Charts, close unused charts, or upgrade the plan.
- EAs stop after a weekend: Windows may have restarted for updates. Check auto-start and Windows Update settings.
Next steps
- Set up the platform: install MetaTrader on a VPS.