Hello, please read below:

Error of Setting Timer in MT4

Hello I bought the MT4 and MT5 version in order to copy trades from MT5 to MT4.

All seems correctly configured, but the trades are not copied from MT5 to MT4.

It works! Thank you.

It was a problem of missing symbols mappings.

That's great Paolo, well done.

You're very welcome. 😊

Hello, thank you for your purchase.

Local Trade Copier EA is designed to copy and close trades extremely fast, typically 0.2 to 0.5 seconds, but this speed depends heavily on the performance of your VPS and the connection quality to your brokers. The copier itself does not introduce delays, but several external factors can.

Here are the key points to check:

1. VPS performance and real CPU cores
   Not all VPS servers are equal. Some advertise many “virtual cores”, but they offer poor real performance. This can easily add 300–700 ms of latency to copying.
   If your MT4/MT5 charts freeze or the prices stop updating, that is a direct sign your VPS is overloaded.

2. Latency to broker servers
   Check the ping (in the bottom right corner of MT4/MT5).
   For fast copying you need below 10–15 ms.
   Anything above 30–40 ms can delay both copying and order closure.

3. Running multiple terminals
   Each MT4/MT5 terminal consumes CPU and RAM.
   If you run many terminals on the same VPS, execution will slow down even if the VPS specs look “good on paper.”

4. Network-related disruptions
   Brief interruptions between the transmitter and receiver terminals (or between terminal and broker) can delay trade copying or closure.

5. High-frequency trading limitations
   For HFT-style strategies, even 0.5 seconds can matter. However, Local Trade Copier EA already operates at the maximum speed possible within MT4/MT5 architecture, so improving your VPS and network connection is essential.

To optimize speed:

• Use a high-performance VPS with real dedicated CPU cores (check Contabo).
• Ensure low latency to both brokers.
• Avoid running too many terminals on the same VPS.
• Restart terminals often to maintain smooth performance.

If you want, I can review your setup and tell you exactly where the delay is coming from. Just send me:

• A screenshot of your transmitter and receiver terminals (with MarketWatch visible)
• The VPS specifications
• The broker ping values
• How many terminals you are running on the VPS

I’ll be happy to help you optimize everything so you get the fastest possible copying speed.

To recheck everything, I’m currently running Local Trade Copier entirely in local mode. Despite this, I’m still observing the same delay, especially when closing trades. The lag consistently reaches close to one second.

I’ve attached screenshots of both the sender and receiver terminals, with Market Watch visible. Here are the additional details you requested:

RECEIVER:

• specifications:

  • System type: x64-based PC

  • Processor: 1 installed — Intel64 Family 6 Model 154 Stepping 3 GenuineIntel ~2300 MH

  • Total physical memory: 16,007 MB

  • Available physical memory: 3,809 MB

  • Virtual memory: max size 18,439 MB, available 3,642 MB

  • OS: Windows 10 (C:\WINDOWS\system32)

• Broker ping values:

  • Sender: ~95 ms

  • Receiver: ~92 ms

• Number of terminals running: 2 (only sender and receiver for this test)

Let me know if you need anything else to help diagnose the issue. I appreciate your assistance in optimizing the copier’s performance.

Hello again, and thank you for all the details.

Based on the information you provided, the delay is not caused by Local Trade Copier EA, but by your infrastructure, mainly two factors:

1. Very high broker latency (92–95 ms)
With this ping, a closure delay near 1 second is expected.
Fast copying is only possible when broker latency is:

• Below 10–15 ms (ideal)
• Below 30 ms (acceptable)

Please ask your broker where their trading servers are located, so you can choose a VPS in that same region. This alone will reduce the delay dramatically.

2. Underpowered VPS resources
Your VPS shows:

• Only one (virtual) CPU core
• Very low available RAM
• Limited virtual memory

This slows down MT5, especially during trade closures.

Recommended solution

For two MT5 terminals (1 transmitter + 1 receiver), the following VPS is fully adequate and provides strong real performance:

Contabo Cloud VPS 10:
https://contabo.com/en/vps/cloud-vps-10/?image=windows-server.335&qty=1&contract=12&storage-type=cloud-vps-10-150-gb-ssd

• Select the datacenter closest to your broker’s server (ask them directly).
• Choose Windows Server 2025, which offers smoother and more stable performance for MT4/MT5 copying setups.

With a stronger VPS and a broker ping below 15 ms, you should see closure times around 0.2–0.5 seconds.

Please contact me directly (I have sent you all this information in a private message here in MQL5.com) to find the best solution for your needs.

I’ll check with my broker about server location and consider upgrading my VPS as you suggested. I’ll make some changes and test again.

Hello and thank you for your purchase,

Why are you writing something (about a scam EA), without even contacting me first!

Please follow my instructions below and let me know if you need any help.

Like this screenshot.

Hello Brian and thank you for your purchase,

There are 18 different lot size types to choose from in the Local Trade Copier EA.

You can read about them in the 'Lot Size Type' setting, in the Settings/Inputs guide below:

https://www.mql5.com/en/blogs/post/745681

Let me know if you have any more questions please.