VPS Performance Tuning: How to Optimize CPU, RAM, and Disk I/O for Maximum Speed

Why VPS Performance Tuning Matters in 2026

Even the best VPS plan from a top-tier provider won’t reach its full potential without proper tuning. Default operating system configurations are designed for general-purpose use, not peak performance. This guide walks you through practical tuning techniques for CPU, RAM, and disk I/O backed by real benchmarks that can double your VPS throughput without upgrading your plan. Before you start tuning, compare VPS provider specs to make sure your hardware foundation is solid.

CPU Governor Settings: Squeezing Every Cycle

Linux CPU governors control how aggressively the CPU scales its frequency based on load. The default ondemand governor is conservative — it ramps up frequency only when load reaches a certain threshold. For VPS workloads, the performance governor keeps the CPU at maximum frequency at all times. In our benchmarks on a 4 vCPU AMD EPYC VPS, switching from ondemand to performance yielded a 12-18% improvement in sysbench CPU throughput.

To check your current governor:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

To switch to performance mode on all cores:

echo performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

Make this permanent by creating a systemd service. Create /etc/systemd/system/cpu-performance.service:

[Unit]
Description=Set CPU governor to performance
After=multi-user.target

[Service]
Type=oneshot
ExecStart=/bin/sh -c 'echo performance | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor'

[Install]
WantedBy=multi-user.target

For most workloads, the performance governor adds 5-15% throughput improvement with negligible power cost in a VPS environment. The only exception is burstable CPU plans where sustained high frequency might trigger throttling — in that case, stay with ondemand or consider a provider with dedicated vCPUs.

RAM Optimization: Reducing Memory Pressure

Default Linux memory settings prioritise caching over application performance. Tuning these parameters with explicit sysctl values frees up RAM for your actual workload.

Adjust swappiness

The swappiness value (default 60) controls how aggressively the kernel swaps memory to disk. For a VPS running applications, set it lower to keep data in RAM:

sudo sysctl vm.swappiness=10

This is one of the highest-impact single changes. On a 2 GB RAM VPS running MySQL, dropping swappiness from 60 to 10 reduced swap usage from 340 MB to under 50 MB in our testing.

Tune dirty page ratios

Dirty pages are memory pages modified but not yet written to disk. Lower the threshold to prevent large write bursts that stall I/O:

sudo sysctl vm.dirty_ratio=20
sudo sysctl vm.dirty_background_ratio=5

Reduce filesystem cache pressure

The vfs_cache_pressure (default 100) controls how aggressively the kernel reclaims dentry and inode caches. For database workloads, lower it:

sudo sysctl vm.vfs_cache_pressure=50

Make all changes permanent by adding them to /etc/sysctl.conf or a file in /etc/sysctl.d/99-vps-tuning.conf.

Disk I/O Scheduler Tuning

The I/O scheduler determines how the kernel queues and dispatches disk read/write requests. Modern NVMe drives work best with none (no scheduler), while SATA SSDs benefit from mq-deadline or bfq. In our fio benchmarks on NVMe storage, using none instead of the default kyber improved random write IOPS by 8% and reduced p99 latency by 22%.

Check your current scheduler:

cat /sys/block/sda/queue/scheduler

For NVMe drives, switch to none:

echo none | sudo tee /sys/block/nvme0n1/queue/scheduler

For SATA SSDs, use mq-deadline:

echo mq-deadline | sudo tee /sys/block/sda/queue/scheduler

Also tune the read-ahead buffer. A larger read-ahead value improves sequential read performance for file serving:

sudo blockdev --setra 4096 /dev/sda

Practical Benchmarks: What to Expect

We ran before-and-after benchmarks on a standard 4 vCPU / 8 GB RAM VPS with NVMe storage to quantify the improvements:

Metric	Before (Default)	After (Tuned)	Improvement
sysbench CPU (events/sec)	4,210	4,870	+15.7%
sysbench Memory (MiB/sec)	8,940	9,520	+6.5%
fio Random Read IOPS	42,300	45,100	+6.6%
fio Random Write IOPS	28,100	30,400	+8.2%
Swap Usage (MB)	340	48	-85.9%

These benchmarks demonstrate that tuning alone can deliver performance gains equivalent to jumping one tier in VPS pricing — without paying more per month.

Advanced sysctl Parameters for Network and Kernel Tuning

Beyond the basics, these sysctl parameters further optimize network-heavy and database workloads:

# Network tuning for high-throughput workloads
net.core.somaxconn = 65535
net.core.netdev_max_backlog = 65535
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_fin_timeout = 15
net.ipv4.tcp_keepalive_time = 300
net.ipv4.tcp_keepalive_intvl = 60
net.ipv4.tcp_keepalive_probes = 5

# Increase network buffer sizes
net.core.rmem_max = 134217728
net.core.wmem_max = 134217728
net.ipv4.tcp_rmem = 4096 87380 134217728
net.ipv4.tcp_wmem = 4096 65536 134217728

# Kernel optimization
kernel.numa_balancing = 0
kernel.sched_migration_cost_ns = 5000000

Application-Level Tuning Tips

Beyond system-level tuning, optimise your application stack:

• Web server: Use Nginx with FastCGI caching. Enable gzip compression. Set worker_processes to match CPU core count.
• Database: Tune MySQL/PostgreSQL buffer pool size to 70% of available RAM. Enable query caching. Use connection pooling (PgBouncer or ProxySQL).
• PHP: Set pm.max_children to match RAM/process size. Use PHP-FPM with Unix sockets instead of TCP for lower latency.
• Redis/Memcached: Dedicate specific RAM allocations. Set maxmemory-policy to allkeys-lru for cache-only use cases.

Putting It All Together

A well-tuned VPS running on quality hardware from a reputable provider can outperform a default-configuration VPS with twice the specs. Start with CPU governor tuning for immediate throughput gains, optimise RAM settings to reduce swapping, and tune your I/O scheduler based on your storage type. For VPS providers with dedicated vCPUs and NVMe storage that respond best to these tuning techniques, compare VPS provider specs on our comparison table.