Most traders spend hours backtesting EAs and refining entry logic but never once open Task Manager on their VPS. That is a mistake. A perfectly coded scalping EA means nothing if it is running on a VPS where RAM is maxed out and the CPU is pegged at 95% because of a runaway Windows Update process. The VPS is part of your trading system, and like any system component, it needs monitoring.
There are four metrics that matter for forex trading on a VPS: CPU usage, RAM usage, disk I/O, and network latency. This guide walks through each one with specific tools, normal ranges, and red-flag thresholds so you know exactly when things are fine and when you need to take action.
Metric 1: CPU Usage
CPU determines how quickly your EAs can process tick data, calculate indicators, and submit orders. Every MetaTrader terminal, every EA, and every indicator is competing for CPU cycles.
How to Monitor
Open Task Manager by right-clicking the taskbar and selecting Task Manager. Click the Performance tab, then select CPU from the left panel. You will see a real-time graph showing overall CPU utilization and a breakdown of speed, processes, and uptime.
For per-process detail, switch to the Details tab. Sort by CPU to see which processes are consuming the most. Look for terminal.exe (MT4) or terminal64.exe (MT5) — these are your MetaTrader processes.
What Is Normal
On a properly configured forex VPS, expect to see:
- Idle (no market hours): 3-10% CPU usage from Windows background services
- Active trading, 1-3 terminals: 10-30% average CPU usage
- News events / high volatility: Spikes to 50-60% are normal and temporary
⚠️ Warning: During major news events (NFP, FOMC, ECB), tick volume spikes 5-10x and spreads widen dramatically. Ensure your VPS has CPU headroom — if CPU hits 100% during news, orders queue instead of executing.
Red Flags
- Sustained usage above 80% during regular trading hours means your VPS is undersized for your workload, or a rogue process is consuming resources. Check the Details tab to identify the culprit.
- 100% CPU for more than a few seconds typically means a stuck EA calculation, a Windows Update downloading in the background, or antivirus performing a full scan. Kill the offending process or reschedule it to weekends.
If you consistently see 70%+ CPU during market hours after eliminating background processes, it is time to upgrade your FXVPS plan. Moving from Standard to Pro doubles your dedicated core allocation.
💡 Tip: Always confirm whether your VPS provider offers dedicated CPU cores or shared vCPUs. Shared cores mean your EA’s execution speed fluctuates based on other users’ workloads — exactly the inconsistency scalpers cannot afford.
Metric 2: RAM (Memory) Usage
RAM is the resource that runs out most visibly. When your VPS exhausts available RAM, Windows starts swapping to disk. Even on NVMe SSDs, swap is 100x slower than RAM. Your EA that normally executes in 1ms suddenly takes 50-100ms. For scalpers, that is the difference between profit and slippage.
How to Monitor
In Task Manager’s Performance tab, click Memory. The key numbers here are:
- In use: How much RAM is currently consumed by all processes
- Available: How much RAM is free for new allocations
- Committed: Total memory allocated (can exceed physical RAM if swap is active)
What Is Normal
Each MT4 terminal uses approximately 256-512 MB of RAM depending on the number of charts, indicators, and history bars loaded. MT5 terminals use 512 MB to 1 GB. Add 800 MB to 1 GB for Windows itself.
Practical examples:
- 2 GB VPS (Core plan): Comfortable for 1-2 MT4 terminals or 1 MT5 terminal
- 4 GB VPS (Pro plan): Handles 3-6 MT4 terminals or 2-3 MT5 terminals
- 8 GB VPS (Scaling plan): Runs 6-10 MT4 terminals or 4-6 MT5 terminals
The 25% Rule
Keep at least 25% of your total RAM free at all times. On a 4 GB VPS, that means staying below 3 GB in use. This headroom absorbs temporary spikes during news events when tick rates increase 5-10x and MetaTrader allocates additional buffers.
Red Flag
If Available drops below 15% of total RAM during normal trading, you are one news event away from swap. Either optimize your MetaTrader configuration or upgrade your plan.
Metric 3: Disk I/O
Disk performance matters more than most traders realize. MetaTrader continuously writes to log files, saves chart data, and updates history. Your EA may also write custom logs or data files. All of this is disk I/O.
How to Monitor
In Task Manager’s Performance tab, click Disk. You will see read and write speeds in real time, plus active time percentage.
For deeper analysis, open Resource Monitor (search “resmon” in the Start menu). The Disk tab in Resource Monitor shows per-process disk activity, including which files are being read and written. This is invaluable for tracking down unexpected disk activity.
SSD vs HDD
FXVPS uses NVMe SSDs across all plans, which deliver read/write speeds of 2,000-3,500 MB/s compared to 80-160 MB/s for traditional HDDs. This means MetaTrader history loading, EA initialization, and log writes happen almost instantly. If you are comparing VPS providers, always confirm they use SSD or NVMe storage — HDD-based VPS services still exist and they will noticeably slow your platform startup and backtesting.
✅ Best Practice: Place MT4/MT5 shortcuts in the Windows Startup folder (Win+R, type shell:startup) so your terminals and EAs restart automatically after any VPS reboot.
The Hidden Disk Problem: Log Files
MetaTrader generates log files in the MQL4/Logs or MQL5/Logs directory — one file per day. Over months, these accumulate to hundreds of megabytes or even gigabytes. Custom EAs that write verbose logs make this worse.
Check your log directories quarterly. Delete logs older than 30 days unless you need them for debugging. On a VPS with limited storage, old logs silently eating disk space can eventually cause MetaTrader to fail when it cannot write new data.
Metric 4: Network Latency
Network latency is the metric that directly affects trade execution speed. It measures the round-trip time for data to travel from your VPS to your broker’s server and back.
Checking Latency in MetaTrader
The quickest check is the status bar at the bottom-right corner of your MT4 or MT5 terminal. It displays the connection speed in milliseconds (e.g., “5.23 ms / 4 of 4”). This number is the round-trip latency to your broker’s trade server.
📊 Key Stat: A home internet connection typically adds 50-200ms of latency to every trade. A colocated VPS in the same datacenter as your broker cuts that to under 5ms, directly improving fill prices on every order.
- Under 5ms: Excellent. You are likely in the same datacenter or very close. This is what FXVPS delivers for 195+ supported brokers.
- 5-20ms: Good. Suitable for most trading strategies including day trading.
- 20-50ms: Acceptable for swing trading but problematic for scalping.
- Above 50ms: Your VPS is too far from your broker. You need to switch to a VPS location closer to your broker’s server.
Command-Line Network Tools
For raw network latency independent of MetaTrader, open Command Prompt on your VPS and run:
ping broker-server-addressReplace broker-server-address with your broker’s server IP (visible in MT4/MT5 under File → Login to Trade Account). This gives you the base network latency without MetaTrader processing overhead.
For more detail, run:
tracert broker-server-addressThis shows every network hop between your VPS and the broker. Fewer hops generally means lower latency. When your VPS is in the same datacenter as the broker (like FXVPS in Equinix LD4 alongside IC Markets, Pepperstone, and dozens of other major brokers), you will often see just 1-3 hops and sub-millisecond times.
Check your specific broker’s latency from each FXVPS datacenter at the broker latency page.
Setting Up Continuous Monitoring with Performance Monitor
For traders who want to log metrics over time rather than just checking spot values, Windows includes Performance Monitor (perfmon).
Open it by searching “perfmon” in the Start menu. Click Performance Monitor in the left panel, then click the green + button to add counters. The most useful counters for trading VPS monitoring are:
- Processor → % Processor Time: Overall CPU usage over time
- Memory → Available MBytes: Free RAM trending over hours/days
- PhysicalDisk → Disk Bytes/sec: Read/write throughput
- Network Interface → Bytes Total/sec: Network traffic volume
Set the graph duration to 1 hour or longer to spot patterns. You might discover that CPU spikes every day at the same time (a scheduled task), or that RAM slowly climbs throughout the week (a memory leak in an EA).
The Decision Matrix: When Metrics Say Upgrade
After monitoring for a week during normal trading, use these thresholds:
| Metric | Green (Stay) | Yellow (Watch) | Red (Upgrade) |
|---|---|---|---|
| CPU | Under 50% average | 50-70% average | Over 70% sustained |
| RAM | 40%+ available | 20-40% available | Under 20% available |
| Disk | Under 50% active | 50-80% active | Over 80% active |
| Latency | Under 5ms | 5-15ms | Over 15ms |
If you are in the red zone for any single metric, address it. If you are yellow on two or more metrics simultaneously, you are likely one market event away from performance degradation.
For latency issues, the fix is usually selecting the right VPS location rather than upgrading specs. FXVPS operates in London (LD4), New York (NY4), Tokyo (TY3), and Hong Kong (HK1) — choose the datacenter closest to your broker. For resource issues (CPU, RAM, disk), moving to the next FXVPS plan is the straightforward solution, with plans ranging from Core at $29/month to Scaling at $79/month.
Your VPS is infrastructure. Treat it like infrastructure. Monitor it, understand its limits, and you will catch problems before they cost you money on a live trade. Start with FXVPS dedicated resources and use these monitoring techniques to keep your trading edge sharp.