Noisy Neighbor Problem
What a Noisy Neighbor Is and Why It Happens
A noisy neighbor is another tenant on the same physical host whose workload uses shared resources so heavily that it slows down your virtual server. The name describes the effect: a loud neighbor disturbs everyone else, even when the walls are meant to keep sound out.
A hypervisor isolates virtual machines from each other in software, by assigning each one separate memory and scheduling its CPU time. Some resources remain physically shared below that layer: CPU caches, memory bandwidth, the physical disks behind every virtual disk and the network card. A guest can be isolated on paper and still feel the effect of a neighbor using these shared parts.
Shared Resources and How Isolation Limits the Effect
Disk input and output is the most common source of trouble. A neighbor running a large database import or backup can fill the queue for the physical disk, so reads and writes on your server take longer, even if your own CPU use is low. A busy neighbor can also saturate a shared network uplink.
Providers reduce the effect with isolation controls. They can cap a guest's disk operations per second and network throughput, so that one guest cannot take everything. They can also place guests on separate storage or hosts. Isolation does not remove contention entirely, but it makes the impact smaller and more predictable. For the underlying mechanics, see how virtual machines are isolated from each other.
A Database That Slows Down Every Night
An online store's database becomes slow every night between 2 and 3 a.m., although traffic is at its lowest. The store's own CPU use and memory look normal, but disk wait times are high. The cause turns out to be a neighboring virtual machine on the same storage running a nightly backup.
The owner cannot see the neighbor or change its schedule. The provider can move the store to another host or apply a disk limit to the neighbor. The store can also move its own heavy tasks so they do not overlap with the backup window.
Frequently asked questions
How is a noisy neighbor different from overselling?
Overselling is a policy: a host sells more resources than it has. A noisy neighbor is an effect: one tenant's workload slows others down. Overselling makes noisy neighbors more likely because more guests compete for the same hardware, but a neighbor can still cause problems on a lightly loaded host. See the article on VPS overselling for the policy side.
Can I prevent a noisy neighbor from affecting my server?
You cannot control your neighbors, but you can reduce the risk. Choose a plan with dedicated resources if steady performance matters, ask the provider how it limits disk and network use, and watch for signs such as rising disk wait or CPU steal time. If the problem persists, ask the provider to move your server or consider a different host.