Can MT5 Use Both Local CPU and Remote Farm Agents at the Same Time?
Yes. MT5 can run enabled local agents and remote farm agents in the same optimisation, but the right mix depends on whether your local machine is only a controller or also carries live trading and daily work.
For MT5 local CPU and remote farm agents, the local terminal usually stays the master node while Strategy Tester distributes passes across local workers and remote agents together. That hybrid setup is often the practical middle ground between a small MetaTrader VPS and a full MT5 backtest farm, especially when you want faster optimisation without moving every task away from your own machine.
Quick answer
MT5 can use local CPU agents and remote farm agents at the same time in one optimisation run if both are enabled and reachable.
Best use case
Keep the terminal local as the controller, use some local cores when available, and add remote farm capacity when the pass count becomes too large for one machine.
Main caution
If the same Windows machine also hosts live trading, using every local core for testing can create avoidable contention even when remote agents are present.
Key Takeaways
A mixed local and remote MT5 setup is valid, but it should be intentional.
The most useful way to think about this is not “local or remote,” but “which work belongs where.” Local agents can add useful throughput, while remote farm agents handle the heavier parallel load. The right balance depends on whether your local machine is dedicated to research or still doubles as a live trading box, office workstation, or smaller MetaTrader server.
Yes, both can run
MT5 Strategy Tester can distribute optimisation passes across local agents and remote agents in the same session.
The local terminal still matters
Your own MT5 terminal remains the coordinator, so local responsiveness and stable connectivity still matter even when most compute is remote.
Do not force everything onto one box
If the machine also runs live terminals, reserve headroom locally and let the farm carry the heavier optimisation share.
Comparison Table
How the main MT5 optimisation layouts compare.
Traders usually end up choosing between local-only testing, remote-only testing, or a hybrid model. The hybrid approach is often the best bridge when you want extra speed without turning your main machine into a pure controller with no local participation.
| Layout | How it works | Good fit | Main trade-off |
|---|---|---|---|
| Local agents only | The MT5 terminal and all tester agents run on the same machine. | Smaller research jobs or early setup work on one dedicated box. | Throughput is limited by one machine and can interfere with live use. |
| Remote farm only | The local terminal mainly coordinates while almost all compute runs on remote agents. | Larger optimisation batches when the local machine should stay light. | You still depend on the local controller and on the remote environment being ready. |
| Hybrid local plus remote | Local CPU agents contribute part of the work while remote farm agents add scale. | Growing MT5 workloads where some local CPU is available but not enough alone. | You must manage local headroom carefully to avoid contention. |
| Dedicated test server plus farm | A dedicated Windows server hosts the master terminal and local agents, with remote farm nodes added when needed. | Serious ongoing optimisation where a normal trading VPS is already too small. | More infrastructure, but usually cleaner for sustained testing. |
Practical Setup
How to use local CPU and remote farm agents in one MT5 workflow.
A practical setup is usually simple: keep one MT5 terminal as the controller, decide how many local cores can safely participate, then attach remote agents for the part of the workload that should scale out. The hybrid model works best when the local machine has a clear role instead of trying to be a live VPS, office desktop, and full optimisation node all at once.
1. Define the local role
If the local machine is only for research, you can usually allow more local agents. If it also runs live trading, charts, or RDP work, keep extra headroom and avoid using every core.
2. Enable only useful local agents
Local agents help when the machine still has spare CPU and RAM. They are less useful when each additional local worker makes the terminal slower or competes with production tasks.
3. Let the farm absorb the scale
Remote agents are usually the cleaner place for larger optimisation batches, especially when the real goal is speed rather than squeezing every last local thread.
Practical Checklist
Use this checklist before you start a hybrid MT5 optimisation.
Before the run
- Confirm the local MT5 terminal is the machine you want to use as the master controller.
- Decide whether the local box is research-only or also hosts live MetaTrader workloads.
- Enable only the number of local agents that leaves comfortable CPU and RAM headroom.
- Check that remote agents or the remote farm are reachable and visible to Strategy Tester.
- Use a backtest farm or separate test server when the pass count is already known to be large.
During the run
- Watch whether the terminal stays responsive while results are returned.
- Reduce local agents if the controller becomes slow or if other MT5 terminals are affected.
- Keep live trading off the same machine when optimisation starts becoming a regular heavy task.
- Move from a small VPS to stronger infrastructure when the test workflow keeps outgrowing the box.
- Use a separate dedicated MetaTrader server when production and testing no longer mix cleanly.
Decision Support
How to decide whether local agents should stay in the mix.
When VPS Is Not Enough
A standard Forex VPS stops fitting once MT5 optimisation becomes a real compute workload.
A normal Windows VPS can still make sense for a small master terminal or for modest testing, but it is usually the wrong long-term layer once you start combining more local agents, heavier data, and ongoing farm-based optimisation. At that point the question is not only how to attach remote agents, but whether your controller should move to stronger infrastructure.
A VPS can still be enough when
- The local terminal mainly coordinates jobs and runs few or no local agents.
- Optimisation is occasional rather than a daily high-CPU workflow.
- The VPS is not also overloaded with many live trading terminals.
- You mainly need remote farm scale, not strong local compute.
Move beyond a VPS when
- You want reliable local agents plus remote agents at larger scale.
- Controller responsiveness drops during optimisation.
- Testing competes with live MT5 sessions on the same Windows instance.
- You are effectively building an optimisation pipeline, not only hosting one terminal.
Standard VPS Vs MQL5 VPS
Where each option fits for mixed local and remote MT5 testing.
MQL5 VPS is usually better for
Simpler platform-bound hosting for live trading where you are not trying to build a broader MT5 optimisation environment around local and remote agents.
Full Windows VPS or dedicated is usually better for
RDP access, controller management, heavier test workflows, and transitions toward a dedicated test host or an EPYC-based backtest farm.
Troubleshooting
Common signs that the hybrid setup is configured badly.
Local machine is too busy
If the MT5 terminal becomes laggy, RDP sessions slow down, or live platforms on the same box feel unstable, reduce local agents and let the remote side carry more of the optimisation.
Remote agents add little benefit
If the job is too small or the local controller is the new bottleneck, extra remote agents may not help much. The answer can be cleaner job sizing, fewer local conflicts, or a stronger controller machine.
Testing and live trading are mixed too long
Once optimisation becomes routine, keeping it on the same box as production trading usually creates recurring friction even if the setup technically still runs.
Infrastructure decisions keep getting delayed
If you are repeatedly tuning agent counts on a machine that is obviously too small, the real fix is often to move the controller to a stronger server rather than keep optimising around the limitation.
Final Recommendation
Use local and remote MT5 agents together only when each side has a clear role.
For most serious traders, the best pattern is to let the MT5 terminal remain the local master, keep some local CPU only if that machine can spare it, and move heavier parallel compute to remote farm agents. If the controller box also needs to host live trading, use a smaller local agent count or move testing to a separate server. If optimisation is becoming a core workload, compare a dedicated Windows server for MetaTrader with a proper MT5 backtest farm instead of treating a normal VPS as the permanent answer.
Related Pages
Useful internal pages for the next step.
FAQ
Common follow-up questions.
These answers match the article content and stay focused on practical MT5 optimisation decisions.
Can MT5 use local CPU agents and remote farm agents at the same time?
Yes. MT5 Strategy Tester can distribute optimisation work to enabled local agents and selected remote agents in the same run, as long as those agents are available and properly configured.
Should you always let MT5 use all local CPU cores when remote farm agents are connected?
No. If the same machine is also used for the terminal, RDP work, or live trading, reserving some local CPU headroom is often safer than letting every core participate in optimisation.
What does the local machine do when remote farm agents are added?
The local MT5 terminal remains the controller for the optimisation job. It coordinates passes, receives results, and can also contribute its own local agents if they are enabled.
When is a normal VPS not enough for mixed local and remote MT5 optimisation?
A normal VPS is usually not enough when optimisation becomes a sustained high-CPU workflow, when many agents should run in parallel, or when live trading and testing start competing for the same resources.
Is a dedicated server better than a VPS for MT5 local agents?
Often yes for heavier workloads. A dedicated server gives more predictable CPU access and is usually a cleaner host for local MT5 agents than a standard shared-CPU VPS when optimisation is frequent.
Do remote farm agents remove the need for a local machine entirely?
Not usually. You still need a local master terminal to launch and manage the optimisation, and many traders keep at least some local resources for coordination, lighter agents, or result handling.
Need help choosing between local MT5 agents, a stronger server, or a remote farm?
Send your optimisation pass count, whether the same machine also runs live trading, and how many local cores you want to keep available. We can help you decide between a VPS, a dedicated MetaTrader server, or a cleaner MT5 farm layout.
