FXVPS
Get Started
vps rdp troubleshooting latency performance

Your VPS Feels Slow Over RDP but Your Trading Is Not Affected

person
FXVPS
Share
Your VPS Feels Slow Over RDP but Your Trading Is Not Affected

Sluggish Remote Desktop is one of the most common tickets we see, and it is almost always the same story. Windows on the VPS repaints slowly. Dragging a chart leaves a trail. Typing appears a beat after you type it. The natural conclusion is that the server is struggling, and the next thought is that trades must be suffering too.

They are not, and the reason is worth understanding once, because it changes what you should look at when something feels off.

What Remote Desktop actually does

Remote Desktop is a screen sharing protocol. Windows draws the desktop on the server, encodes what changed, sends those changes down to your computer, and your computer paints them. Your keyboard and mouse travel the other way. That is the whole job.

Your MetaTrader terminal, your EA, your indicators and your order flow are not part of that loop. They live on the server. When your EA decides to enter, the order goes from the terminal on the VPS to your broker across the datacenter network, at the server’s speed. Nobody has to be logged in for it to happen. Close the Remote Desktop window entirely and the EA keeps trading exactly as before.

So there are two completely separate paths, and they share almost nothing:

  • The trading path: VPS to broker. Short, engineered, measured in single-digit milliseconds. This is the one that decides your fills.
  • The viewing path: VPS to your home or office. Long, over the public internet, over your Wi-Fi, sharing a line with everything else you do. This is the one that decides whether the screen feels smooth.

A choppy picture tells you something about the second path. It tells you nothing about the first.

Proving it to yourself in about a minute

You do not have to take this on faith. Three checks settle it:

  1. Check the machine. Inside the VPS, press Ctrl+Shift+Esc for Task Manager and look at CPU and memory while the session feels bad. If they are unremarkable, the server is not the bottleneck. Our guide on monitoring CPU, RAM and disk on your trading VPS covers what normal looks like.
  2. Ping the broker from the server. Open a command prompt inside the VPS and ping your broker’s server. This measures the trading path. It is usually low and stable even while your screen is stuttering.
  3. Look at the terminal’s own record. The Journal tab in MetaTrader timestamps every order. Compare those timestamps with when the screen caught up. The orders went out on time.

If all three look clean and the screen still lags, the delay is between you and the server, which is exactly the part you can fix from your side.

The two things that control how smooth it feels

Your connection to the server. Wi-Fi, a busy line, a household streaming in 4K, a large upload, a video call, a VPN routing you the long way round. Any of these will make the picture stutter while the server sits idle. Wi-Fi is the most common culprit because it varies from second to second, which shows up as an uneven, jerky session rather than a uniformly slow one.

Your resolution and colour depth. This is the big one and the easiest to fix. Remote Desktop has to carry every pixel that changes. A 3840x2160 session at 32 bit colour is several times the data per second of a 1920x1080 session at 16 bit. Spread across two or three monitors it multiplies again. Most traders never touch these settings, so they run the heaviest possible configuration by default.

The settings that fix it

Before you next log in, open Remote Desktop Connection and click Show Options.

On the Display tab:

  • Set the resolution slider to 1920x1080 or lower. On a slower link, 1280x1024 is noticeably lighter again.
  • Set colours to High Color (16 bit). Charts look effectively identical and the data rate drops sharply.
  • Untick Use all my monitors. A multi-monitor session streams every screen.

On the Experience tab:

  • Choose Modem (56 kbps) or Low-speed broadband from the connection dropdown. This is not a claim about your speed. It tells Windows to strip the decorative parts of the picture, which is exactly what you want.
  • Untick Desktop background, Font smoothing, Desktop composition and Visual styles.
  • Make sure Persistent bitmap caching is ticked. It stores parts of the screen locally so they do not have to be resent.

Then on the General tab, enter your VPS IP followed by :41011. FXVPS listens on port 41011, not the Windows default of 3389, so the port is not optional. Save the connection as a .rdp file and these settings come back every time.

Two more things on your side that often matter as much as the client settings: plug into ethernet rather than Wi-Fi if you can reach a cable, and pause downloads, cloud sync, streaming and video calls while you are working on the VPS.

💡 Tip: If you only need the EA running and not the screen, close the Remote Desktop window instead of logging off. The session stays alive, your terminals keep trading, and there is no picture to stream at all. See how to properly disconnect from an RDP session for the difference between disconnect and log off.

On Mac, iPhone and Android

The Microsoft Remote Desktop apps expose the same controls under different names. On macOS, open the connection’s settings and set a fixed resolution rather than “Fit to window”, turn off “Optimize for Retina displays”, and reduce colour quality. Retina is the single heaviest setting on a Mac because it quadruples the pixel count. On mobile, the app scales the session for you, so the useful lever is switching from mobile data to a stable Wi-Fi connection. Our guides cover connecting from a Mac and connecting from Android in full.

When it really is the server

Occasionally it is. The signature is different: the lag is present regardless of resolution, it is there on a wired connection, and Task Manager inside the VPS shows sustained high CPU or memory pressure. The usual causes are a stack of terminals and indicators recalculating on every tick, a Windows Update pass running in the background, or antivirus scanning during a volatile session. In that case the fix is on the machine, not in the client, and it is either housekeeping or more resources. Optimizing MT5 on a VPS and Windows Server optimization for trading both cover the housekeeping side.

If it is still slow

Run a ping and a traceroute from your computer to your VPS IP while the session feels bad, and send us the output. That shows the route between you and us, hop by hop, including the parts we do not control but can often route around. Open a ticket with those two screenshots and we will read the path with you.

Frequently Asked Questions

Does a laggy RDP session slow down my EA or my order execution?

No. Your terminal and your EA run on the server, and orders go from the server to the broker over the datacenter network. Remote Desktop only carries a picture of the screen back to you. The picture can be late without a single order being late.

Why does the screen stutter when the server says CPU and memory are fine?

Because smoothness is decided elsewhere. It depends on the link between your computer and the server and on how much screen data that link has to carry. An idle server still looks choppy over congested Wi-Fi at full resolution and full colour.

What is the single quickest fix?

Drop to 1920x1080 or lower at 16 bit colour, untick “Use all my monitors”, and set the Experience tab to a low-speed profile with Persistent bitmap caching on. That combination removes most of the lag for most people.

Will a lower resolution make my charts less accurate?

No. The chart is drawn on the server from the same price data either way. You are changing how that image is transmitted to you, not what the terminal calculates or what it sends to the broker.

Is it better to use fewer, larger monitors in the session?

Yes for responsiveness. Each additional monitor in the session is another full screen of pixels to encode and send. One 1920x1080 screen with tabbed terminals is far lighter than three screens at native resolution.

My connection is fast, so why does this happen at all?

Raw download speed is not the constraint. Remote Desktop is sensitive to variation and to the upstream direction, both of which Wi-Fi and a busy line affect heavily even on a fast plan. A stable 20 Mbps wired line beats an erratic 500 Mbps wireless one for this purpose.