How fast is a local trade copier? MT5 to MT4 measured on two demo accounts
How long does a local trade copier really take to copy a trade from MetaTrader 5 to MetaTrader 4? Instead of quoting "milliseconds", I ran a live test on two demo accounts on the same PC and read the times from the terminal logs. This post shows the setup, every measured value and what drives the delay.
Setup
- Master: MetaTrader 5, Deriv demo account. Slave: MetaTrader 4, MetaQuotes demo account. Same Windows PC, both terminals open.
- Copier: Chakana Trade Copier (one EA, master or slave mode, no DLL). The master publishes its positions to a shared file; the slave reads it every 500 ms (the default sync interval).
- Lot mode on the slave: same lot as the master. SL/TP mode: same price.
- Sequence run by a script on the master: open EURUSD 0.50, GBPUSD 0.30, USDJPY 0.40 and XAUUSD 0.10; move the EURUSD stop loss and take profit; close half of EURUSD; close USDJPY; close everything.
- Measured value: time from the master's "done" line in the MetaTrader 5 log to the slave's "opened / modified / closed" line in the MetaTrader 4 log. Both logs use the clock of the same PC.
Results
| Action on the master | Master done | Slave done | Delay |
|---|---|---|---|
| Open BUY EURUSD 0.50 | 18:56:11.897 | 18:56:13.048 | 1.15 s |
| Open SELL GBPUSD 0.30 | 18:56:16.136 | 18:56:16.403 | 0.27 s |
| Open BUY USDJPY 0.40 | 18:56:20.394 | 18:56:20.951 | 0.56 s |
| Open SELL XAUUSD 0.10 | 18:56:24.667 | 18:56:25.434 | 0.77 s |
| Modify EURUSD SL and TP | 18:56:31.913 | 18:56:32.435 | 0.52 s |
| Close 0.25 of EURUSD (partial) | 18:56:39.227 | 18:56:39.929 | 0.70 s |
| Close USDJPY | 18:56:45.446 | 18:56:45.962 | 0.52 s |
| Close XAUUSD | 18:56:52.689 | 18:56:53.752 | 1.06 s |
| Close GBPUSD | 18:56:52.920 | 18:56:53.495 | 0.58 s |
| Close EURUSD (rest) | 18:56:53.160 | 18:56:54.005 | 0.85 s |
Ten actions: minimum 0.27 s, maximum 1.15 s, median 0.64 s, average 0.70 s. Every action was copied: same symbols, same lots, the stop loss and take profit followed the change, and the partial close left 0.25 lots open on both sides.
Where the time goes
- Polling: with a 500 ms sync interval the slave sees a new trade between 0 and 500 ms after the master publishes it, about 250 ms on average.
- Slave execution: the slave's broker needs its own time to fill the order. In the MetaTrader 4 log the gap between "instant order" and "order was opened" was around 0.25 to 0.4 s in this test.
- Busy moments: the first trade (1.15 s) and the three closes sent within half a second (up to 1.06 s) were the slowest, because the slave had several actions to process in the same cycle.
Prices are not identical
The two accounts are on different servers with different quotes. The EURUSD buy filled at 1.09722 on the master and 1.09717 on the slave. That difference comes from the two price feeds and from the delay above. A copier cannot remove it; it can only limit it with a maximum slippage and a maximum price difference (skip the entry if the slave's price moved too far).
Practical takeaways
- Keep master and slave on the same PC or VPS: the copy then does not depend on an internet service between them.
- A shorter sync interval reduces the average wait, at the cost of more disk reads.
- On funded or small accounts, set limits on the slave side (maximum lot, maximum total lots, daily loss) so a mistake on the master is not copied without control.
- Expect small price differences between brokers; check them with your own accounts before going live.
Limitations
One test, two demo accounts, one PC, about one minute of activity. Other brokers, servers, VPS hardware or busier markets will give different numbers.
Watch it and try it
The full test is in this video: MT5 to MT4 live copy (4 markets). Chakana Trade Copier copies between MetaTrader 4 and 5 terminals on the same computer, with lot modes, symbol mapping, slave limits and account protection, and it has a free demo in the Strategy Tester:
- MetaTrader 5: Chakana Trade Copier MT5
- MetaTrader 4: Chakana Trade Copier MT4
Trading involves risk of loss. Results on a slave account can differ from the master because of spread, slippage and execution.


