My VPS once hit 100% CPU at 07:58 London because I had left twelve charts, three DOM windows, and two half-forgotten EAs running over the weekend. The terminal hiccuped; a stop click lagged; I flattened late.
Fix was subtraction. One terminal profile for London: four charts max, no research browsers on the box, defensive scripts only, and a Sunday reboot with a CPU check before the open. I also moved screenshots and journal typing to the local machine so the VPS only trades.
If Task Manager is entertaining, the box is wrong for scalping. Prop challenge mornings especially: I would rather a plain setup that responds than a cockpit that stutters when EURUSD jumps. Overload is a process risk equal to a wide spread - it just shows up as delay instead of price. After the fix I log CPU and free RAM every Sunday in the same file as ping. If CPU idle is already high before London, I strip profiles before the open rather than during it. Lag at 08:01 is not a mystery when Sunday said the box was heavy.
Advertisement
CPU overload on VPS with too many charts and EAs
-
PropScalpDesk
- Posts: 521
- Joined: Sat Sep 19, 2026 7:50 pm
Recommended broker for automated trading & scalping
-
Shadow Trader
- Posts: 989
- Joined: Wed Sep 09, 2026 5:19 pm
Re: CPU overload on VPS with too many charts and EAs
The half-forgotten EAs are the bit that rings true. On my old 2 vCPU box the worst offender wasn't the chart count, it was one small utility EA that printed a line to the journal on every tick, which on a fast EURUSD open meant thousands of writes a minute.
Two settings helped more than removing charts. I dropped max bars in chart to 5,000, since nothing I scalp needs years of M1 history loaded, and I turned off news and sounds in the terminal options.
Windows itself is the other trap. Updates and Defender scans love to start when the box has sat idle all weekend, so I set active hours to cover 06:00 to 22:00 London and only do the Sunday reboot after checking nothing is pending.
Sunday idle numbers can mislead as well. A box sitting at 8% on Sunday can still hit 90% when every chart redraws on the 08:00 candle, so I run a counter from 07:55 to 08:10 on Mondays and want the peak under 60%.
How many terminals do you run on one box? I stopped at two after a third one pushed the open spike past that line.
Two settings helped more than removing charts. I dropped max bars in chart to 5,000, since nothing I scalp needs years of M1 history loaded, and I turned off news and sounds in the terminal options.
Windows itself is the other trap. Updates and Defender scans love to start when the box has sat idle all weekend, so I set active hours to cover 06:00 to 22:00 London and only do the Sunday reboot after checking nothing is pending.
Sunday idle numbers can mislead as well. A box sitting at 8% on Sunday can still hit 90% when every chart redraws on the 08:00 candle, so I run a counter from 07:55 to 08:10 on Mondays and want the peak under 60%.
How many terminals do you run on one box? I stopped at two after a third one pushed the open spike past that line.
-
Shadow Trader
- Posts: 989
- Joined: Wed Sep 09, 2026 5:19 pm
Re: CPU overload on VPS with too many charts and EAs
PropScalpDesk, two terminals is my hard ceiling too, and I would push the Sunday check one step further. I now open both terminals at 07:50 on the check day and watch Task Manager through the first busy candle, not just at idle.
A box that sits at 10% idle and spikes to 70% when both terminals redraw is already too close for a live Monday. I want that rehearsal peak under 50% or I strip a chart profile before the week starts.
The journal writing EA lesson also made me ban any utility that logs on every tick. Heartbeat once a minute is fine. Tick spam on M1 during the London open is how a 2 vCPU box dies.
I moved the economic calendar to the local machine as well. The VPS browser was quietly eating RAM overnight and only showed up when the open hit.
Do you keep a written strip list for Sunday, or decide on the fly when the counter looks ugly? Mine is four lines taped under the monitor so I do not negotiate at 07:58.
A box that sits at 10% idle and spikes to 70% when both terminals redraw is already too close for a live Monday. I want that rehearsal peak under 50% or I strip a chart profile before the week starts.
The journal writing EA lesson also made me ban any utility that logs on every tick. Heartbeat once a minute is fine. Tick spam on M1 during the London open is how a 2 vCPU box dies.
I moved the economic calendar to the local machine as well. The VPS browser was quietly eating RAM overnight and only showed up when the open hit.
Do you keep a written strip list for Sunday, or decide on the fly when the counter looks ugly? Mine is four lines taped under the monitor so I do not negotiate at 07:58.