Noisy neighbors: when the VPS slows because of someone else

[Amanhasnoname]

A virtual server shares physical hardware with other customers. When another tenant uses heavy CPU or disk resources, the host may throttle the others, causing stalls. This is the noisy neighbor problem.

The symptom for traders is irregular latency spikes with no obvious cause on the machine itself. CPU usage in the guest looks normal, yet processing is slowed by the host's scheduler.

Detect it by logging loop timings inside the EA: measure how long a fixed small task takes, and record outliers. Spikes that appear at random times, not tied to market events, hint at host contention.

Choosing a provider with dedicated resources or guaranteed CPU shares reduces the risk. Some plans offer reserved cores. Higher-priced plans typically have fewer tenants per host.

If problems persist, ask the provider for host information, or migrate to a different node. Keep records of timestamps and measurements as evidence.

The cheapest VPS plan is rarely the cheapest option once missed fills are counted.

How consistent is the VPS's timing when a simple benchmark task runs every second?