forex-scalping.com

The machine that updates itself

A true story shape, repeated by plenty of traders. A position opens on a fast pair. A scalp is going well. The target is two pips away. Then the platform freezes. The operating system has started an update. The CPU is pegged, the platform window is unresponsive, and the price moves against the position.

By the time the system recovers, the trade is a loss.

Trading on a general-purpose computer invites this kind of event. Windows updates, antivirus scans, browser tabs, and cloud syncing all compete for resources.

A dedicated trading machine, or better a VPS, avoids most of it. Updates can be scheduled for weekends. Unneeded software can be removed.

There is also the hardware side: laptop battery saver modes that throttle the processor, sleeping screens that suspend background tasks, and USB devices that cause driver interrupts.

None of this is exciting. All of it has cost real money for someone.

What has been the most unexpected thing on a trading computer that caused a delay or a missed trade?

Automatic updates on Windows can restart the computer at inconvenient times, closing the trading terminal and stopping EAs. On a VPS running unattended, that can leave positions unmanaged for hours if the terminal is not set to restart automatically. Many traders have discovered this after finding their VPS rebooted overnight with the terminal closed. Windows allows active hours to be set, during which restarts are avoided, but those hours have limits and may not cover all trading periods. Configuring update settings carefully, and scheduling restarts for the weekend when markets are closed, reduces the risk of an unexpected interruption during the trading week.

The most unexpected one for me was a laptop that dropped into a power saving mode whenever the charger got nudged loose. I was in a short EURGBP scalp with the target about three pips away, the terminal stopped updating for nearly eight seconds, and I got filled on my stop at a price well beyond where I'd set it. It took me a week to realise the charger was the cause.

After that I stripped the machine down. I turned off automatic updates, set the power plan to high performance with the screen sleep disabled, and removed the cloud sync that kept spiking the disk. Then I moved the platform to a small VPS and kept the laptop only for charting.

The other thing worth checking is the terminal log. Mine showed gaps of several seconds between ticks that I had blamed on the broker for months. A quick look at timestamps would have saved me a lot of annoyed trades.