A Linux VDS can feel slow while its CPU chart looks ordinary because utilization does not show every kind of waiting. Processes may be queued for CPU time, stalled on memory reclaim or storage, or waiting behind a service queue or remote dependency. The way to find the cause is to capture repeatable measurements during the slowdown and match them to the affected operation—not to diagnose from one percentage.
Why is my VPS slow when CPU usage is low?
CPU utilization measures time spent in particular CPU states; it does not measure how long a request spends waiting elsewhere. A server can therefore have modest aggregate CPU use and still deliver poor response times. The Linux kernel’s Pressure Stall Information (PSI) documentation describes how contention for CPU, memory, or I/O can produce latency spikes and throughput losses.
As an Amazon Associate I earn from qualifying purchases.
Start by noting when the slowdown began, which endpoint, command, or job is affected, whether it affects all users or only some clients, and whether it is continuous or periodic. Compare the same time interval in request latency, service logs, host metrics, and relevant dependency metrics. Preserve the initial output before restarting services or changing limits.
Free tools Windows power users keep installed
One-click scans. No signup required.
Take a time-correlated Linux snapshot
Run short interval samples while the symptom is present; a long-uptime average is not an incident snapshot. These commands provide a starting point:
#1 Best Overall
- 12th Intel Alder Lake N95 Processor – The GMKtec G3 S Mini PC is powered by the 12th Gen Intel N95 processor with 4 cores, 4 threads, 6MB cache and a burst frequency up to 3.4GHz. Compared with N100/N5105/N5100/N5095, the N95 delivers up to 36% overall performance improvement. Perfect for routine tasks, office work, and home entertainment, this compact mini desktop is more convenient than traditional bulky PCs.
- 8GB RAM & 256GB SSD Storage – Pre-installed with 8GB DDR4 memory and a fast 256GB M.2 2242 SSD, the G3 S mini desktop offers quicker startup, smoother multitasking, and faster file transfers. Enjoy seamless performance whether you’re working on multiple applications, browsing, or streaming content.
- Rich Interfaces & Connectivity – The G3 S mini computer comes equipped with USB 3.2 (up to 10Gbps), dual HDMI 2.0 (4K@60Hz), and a 3.5mm audio jack. With support for WiFi 5, Bluetooth 5.0, and Gigabit Ethernet (RJ45 1000MbE), it connects easily with monitors, projectors, printers, office equipment, and other peripherals, making it versatile for both home and business use.
- Dual 4K Display Support – Featuring upgraded Intel UHD Graphics (up to 1000MHz), the G3 S supports 4K video playback and AV1 decoding for a smooth viewing experience. With dual HDMI outputs, you can connect two 4K@60Hz displays simultaneously, enabling efficient multitasking for work and entertainment.
- GMKTEC WARRANTY - GMKtec offers a 3-year limited warranty (1 year replacement + 2 years parts replacement) for each mini PC, starting from the date of the purchase effective on all sales starting Oct. 2026. All defects due to design and workmanship are covered. With a professional after sales team always ready to attend to your needs, you can simply relax and enjoy your mini PC
uptime
nproc
vmstat 1 10
mpstat -P ALL 1 10
If sysstat is installed, interval reports can add CPU and queue context:
sar -u 1 10
sar -q 1 10
Use the manual installed on the server, since sysstat versions and available fields vary. In vmstat, inspect runnable and blocked tasks as well as CPU state. In mpstat or sar, compare user, system, idle, iowait, and steal across repeated samples.
Correlate every sample with the affected operation’s latency and timestamp. Linux exposes CPU accounting through /proc/stat and /proc/uptime; the kernel documentation describes those interfaces. No single universal threshold diagnoses a slow VDS: compare with the server’s baseline, vCPU count, workload, and user-visible latency.
Recommended Free Tools
Read CPU demand, load, and virtualization signals
Load average is not CPU utilization
Load average is not a CPU percentage. It includes runnable or running tasks and tasks in uninterruptible sleep, so a high load can reflect work waiting on something other than CPU. The sysstat sar manual describes the load-average measure. Compare it with vCPU count, runnable and blocked task counts, CPU state, and other measurements rather than treating load above the vCPU count as proof of CPU saturation.
Steal time can indicate delayed guest CPU time
%steal is time a virtual CPU spent involuntarily waiting while the hypervisor serviced another virtual processor, as described in the sysstat manual and proc_stat(5). If repeated samples show steal rising alongside the slowdown, save timestamps and instance details visible to you, then ask the provider to inspect scheduling or allocation. Guest measurements alone do not identify which host component or tenant caused the delay, and one reading does not prove provider fault.
Rank #2
- 【AMD Ryzen 3 5300U CPU: Outperforms N150 & 3500U】 BOSGAME E5 mini PC is powered by the TSMC 7nm FinFET architecture AMD Ryzen 3 5300U processor (4 Cores, 8 Threads, up to 3.8GHz boost, 6MB total cache). Compared to low-end Intel N150 or 3500U chips which only have 4 single threads and throttle under load, the 5300U delivers over 30% faster multi-core speed. Run 30+ browser tabs, large Excel sheets, and Zoom meetings simultaneously without system lag.
- 【8GB DDR4 RAM & 256GB NVMe SSD Storage】 Installed with high-speed 8GB DDR4 dual-channel memory and a fast 256GB M.2 2280 SSD, eliminating slow boot times and application loading delays. To accommodate growing data requirements, the upgradeable hardware design features dual SODIMM slots that allow you to expand memory up to 64GB RAM, ensuring smooth operation during heavy multitasking.
- 【High-Capacity Dual M.2 SSD Storage Expansion】 Never worry about running out of space for your business files. In addition to the pre-installed 256GB system drive, the motherboard houses an extra empty internal M.2 2280 NVMe PCIe 3.0 slot. This allows you to easily add a second solid-state drive for up to an additional 2TB of storage capacity (upgrades not included) without needing to remove or reinstall the original operating system.
- 【Radeon 6-Core Graphics & Triple 4K Displays】 Integrated with official AMD Radeon Graphics (6 Graphics Cores, 1500 MHz frequency) for casual gaming, photo editing, and crisp 4K media decoding. Featuring 1x HDMI 2.0 port, 1x DisplayPort, and 1x Full-Function Type-C port, the E5 outputs true 4K@60Hz resolution to three monitors at once. This multi-screen setup eliminates constant window-switching for traders, programmers, and office workers.
- 【Dual 2.5GbE LAN Ports for Advanced Networking】 Experience fast wired network transmission speeds up to 2500Mbps without lagging or buffering. The integration of dual 2.5 Gigabit Ethernet ports (powered by Realtek RTL8125 controller) makes this compact computer an exceptional hardware choice for tech enthusiasts. Easily configure it into software routers, hardware firewalls (pfSense, OpnSense), home NAS servers, or local homelabs.
Interpret iowait cautiously
%iowait is an accounting signal, not a disk diagnosis. The Linux man-pages proc_stat(5) documentation warns that the value is difficult to calculate and may be unreliable. Corroborate it with per-device latency and queue data, blocked tasks, and application timing.
Check CPU, memory, and I/O pressure
Where the kernel exposes PSI, read its three interfaces during the slowdown:
cat /proc/pressure/cpu
cat /proc/pressure/memory
cat /proc/pressure/io
Each available interface reports some and, where supported, full lines. some tracks time when at least some tasks stall; full tracks time when all non-idle tasks stall simultaneously. The avg10, avg60, and avg300 values are rolling averages over 10, 60, and 300 seconds; total is cumulative stall time. These are measurement windows, not recommended thresholds. PSI fields and file availability depend on kernel support, so check whether the files exist rather than assuming every VDS provides them. See the kernel PSI documentation.
Rising memory or I/O pressure that aligns with slow work can explain latency despite modest CPU use. Memory reclaim may involve writing pages to swap or flushing file-backed pages; CPU pressure means tasks wait for CPU time, while I/O pressure means they wait for I/O completion. The systemd resource-pressure guidance describes these mechanisms.
Distinguish memory reclaim from storage waits
Measure memory and swap activity over time
free -h
vmstat 1 10
sar -r 1 10
sar -W 1 10
Look for swap-in and swap-out activity, major faults, reclaim activity, and memory PSI at the same time as the service slowdown. Used memory by itself does not establish memory pressure: Linux also uses memory for caches. The sysstat manual documents memory, paging, major-fault, and swap statistics.
Rank #3
- 【1-Year Worry-Free Warranty】Your satisfaction is our priority. Glorlin provides a 1-year warranty covering any hardware malfunctions. We support returns or exchanges to ensure a 100% worry-free shopping experience. Have a question? Reach out to us through our official after-sales email for a prompt solution.
- 【Reliable Performance with Ryzen 7 Processor】Powered by AMD Ryzen 7 8745HS (8 cores, 16 threads, up to 4.9GHz), this mini pc delivers stable performance for daily workloads. Suitable for office tasks, programming, and multitasking, it works well as a ryzen mini pc for both home and business use.
- 【Radeon 780M Graphics for Media and Light Gaming】Equipped with integrated Radeon 780M graphics, this mini gaming pc supports smooth 4K video playback and handles many popular games at adjusted settings. A practical mini computer for media, editing, and casual gaming.
- 【Mini PC 16GB RAM and Fast Storage】This mini pc 16gb ram configuration includes single 16GB DDR5 memory (4800MHz,3GB is assigned to VRAM by default) and a 1TB NVMe SSD, offering quick boot times and responsive system performance. Dual M.2 slots allow storage expansion up to 4TB for growing files and projects.
- 【Quad 4K Display Support for Productivity】The mini desktop computer supports up to four 4K displays via HDMI, DisplayPort, and dual USB-C ports. Ideal for multi-screen workflows such as coding, trading, or content creation with improved efficiency.
Measure the device backing the workload
iostat -xz 1 10
Identify which device actually backs the affected workload, then compare read and write rates, queueing, await or latency, and utilization across the incident interval. Device type and virtualization layers affect what guest-visible counters mean. High iowait alone does not establish a failing disk; combine it with device-level measurements, blocked tasks, and application timing.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsLook beyond host resource percentages
Check for tasks in D state and blocked-process counts where available, then correlate them with device and mount activity. A network filesystem or remote dependency can cause waits that a CPU chart will not explain.
Compare latency measured from the server with reports from affected clients. Depending on the architecture, examine packet loss, retransmits, DNS timing, connection backlog, worker saturation, and application, database, or external-service timing. A guest-side host metric cannot determine whether a user-facing delay comes from the network path or an upstream service. Use existing logs or tracing to find where request time is spent.
Use signals to guide the next investigation
| Signal during the slowdown | What it can suggest | What it cannot prove alone |
|---|---|---|
| Load average above vCPU count | More runnable or uninterruptible work may be present than available CPU capacity. | CPU saturation specifically; load includes uninterruptible tasks. |
| Steal rises alongside latency | Guest vCPU time is involuntarily delayed under virtualization. | Which tenant or host component caused the delay. |
| Iowait rises | CPU idle accounting overlaps outstanding I/O. | A failing disk; the kernel documents accounting limitations. |
| Memory PSI, swapping, and major faults rise together | Memory-related stalls or reclaim may affect work. | That adding RAM is the only or best fix. |
| I/O PSI aligns with device latency or queueing | I/O stalls may be affecting slow operations. | Whether the cause is a local device, shared storage, filesystem, or remote mount. |
| Host counters look ordinary | The measured host resources may not be the bottleneck. | That the application or network is healthy. |
These interpretations are consistent with the proc_stat(5) documentation, sysstat manual, and kernel PSI documentation; none substitutes for measurements from the affected workload.
Choose a reversible mitigation and verify it
Make a change only after the measurements point to a pressure or slow stage. Change one thing at a time, record it, and compare the same user-facing latency and resource metrics afterward. Roll back if service performance worsens.
- CPU pressure: identify the process or service and its parallelism. If safe, reduce nonessential concurrency, defer batch work, or shed low-priority load.
- Memory pressure: identify allocation growth and reclaim or swap behavior. Release caches only when the service can do so safely; otherwise reduce workload demand or right-size memory based on observed demand.
- I/O pressure: identify the device and processes driving waits. Stagger backup or batch work, inspect storage and filesystem health, and escalate when guest evidence points to shared storage or a host layer.
- Steal pressure: provide the provider with timestamped interval samples and ask it to check host scheduling or resource allocation; do not present a single reading as proof of a host fault.
- No host pressure signal: trace the slow request through service queues, databases, and remote dependencies. Address the slow stage demonstrated by that trace instead of resizing the VM by reflex.
The systemd guidance describes releasing unneeded caches for memory pressure and reducing parallelism, deferring work, or shedding load under CPU or I/O pressure. Compare any proposed alternative, such as reducing concurrency or moving to a larger instance, using representative-load latency, queue or pressure behavior, operational risk, and cost. A larger instance is not a universal remedy when the measured bottleneck is elsewhere.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




