{"id":221,"date":"2026-01-01T02:00:03","date_gmt":"2026-01-01T02:00:03","guid":{"rendered":"https:\/\/virtualserversvps.com\/blog\/?p=221"},"modified":"2026-06-19T02:39:40","modified_gmt":"2026-06-19T02:39:40","slug":"a-comprehensive-guide-to-linux-vps-virtual-private-server","status":"publish","type":"post","link":"https:\/\/virtualserversvps.com\/blog\/a-comprehensive-guide-to-linux-vps-virtual-private-server\/","title":{"rendered":"Linux VPS Performance Tuning: Optimize Kernel Parameters for Maximum Throughput"},"content":{"rendered":"\n

If you’re running applications on a Linux VPS, you’re already getting dedicated resources and root access. But are you getting the maximum<\/em> performance your virtual server can deliver? Default Linux kernel settings are tuned for general-purpose use, not for the specific workloads you’re running. By adjusting key kernel parameters, you can significantly improve network throughput, disk I\/O, and memory management on your VPS. For a comparison of VPS providers that support full kernel tuning, check out the provider comparison table<\/a>.<\/p>\n\n\n\n

Understanding sysctl and Kernel Parameters<\/h2>\n\n\n\n

The Linux kernel exposes hundreds of tunable parameters through the \/proc\/sys\/<\/code> virtual filesystem. You can view and modify them at runtime using the sysctl<\/code> command. Permanent changes go into \/etc\/sysctl.conf<\/code> or a file in \/etc\/sysctl.d\/<\/code>. Before making any changes, always back up your current configuration:<\/p>\n\n\n\n

sudo sysctl -a > ~\/sysctl-backup-$(date +%F).txt<\/code><\/pre>\n\n\n\n
1. Network Performance Tuning<\/h2>\n\n\n\n
Network latency and throughput are critical for web servers, APIs, and database-driven applications. Here are the most impactful tweaks:<\/p>\n\n\n\n
Enable TCP BBR Congestion Control<\/h3>\n\n\n\n
BBR (Bottleneck Bandwidth and Round-trip propagation time) is Google’s modern congestion control algorithm. It can dramatically improve throughput on high-latency links:<\/p>\n\n\n\n
echo 'net.core.default_qdisc=fq' | sudo tee -a \/etc\/sysctl.conf\necho 'net.ipv4.tcp_congestion_control=bbr' | sudo tee -a \/etc\/sysctl.conf\nsudo sysctl -p<\/code><\/pre>\n\n\n\n
Verify BBR is active with sysctl net.ipv4.tcp_congestion_control<\/code>. You should see bbr<\/code> as the output.<\/p>\n\n\n\n
Increase TCP Buffer Sizes<\/h3>\n\n\n\n
Default TCP buffer sizes are conservative. For better throughput, especially on connections with high bandwidth-delay product, increase them:<\/p>\n\n\n\n
# Increase TCP max buffer sizes\nnet.core.rmem_max = 134217728\nnet.core.wmem_max = 134217728\n# Set TCP auto-tuning buffers (min, default, max)\nnet.ipv4.tcp_rmem = 4096 87380 134217728\nnet.ipv4.tcp_wmem = 4096 65536 134217728\n# Enable TCP window scaling\nnet.ipv4.tcp_window_scaling = 1<\/code><\/pre>\n\n\n\n
Optimize Connection Handling<\/h3>\n\n\n\n
For web servers handling many concurrent connections, these settings prevent socket exhaustion:<\/p>\n\n\n\n
net.ipv4.tcp_fin_timeout = 15\nnet.ipv4.tcp_tw_reuse = 1\nnet.core.somaxconn = 4096\nnet.ipv4.tcp_max_syn_backlog = 8192\nnet.core.netdev_max_backlog = 5000<\/code><\/pre>\n\n\n\n
2. Memory and VM Tuning<\/h2>\n\n\n\n
VPS instances often have limited RAM, so memory management settings matter significantly:<\/p>\n\n\n\n
# Reduce swappiness (default 60) \u2014 prefer keeping data in RAM\nvm.swappiness = 10\n# Increase dirty page ratios for better write performance\nvm.dirty_background_ratio = 5\nvm.dirty_ratio = 10\n# Increase max number of memory map areas a process may have\nvm.max_map_count = 262144<\/code><\/pre>\n\n\n\n
A swappiness value of 10 tells the kernel to avoid swapping unless absolutely necessary. This is particularly useful on VPS plans with limited disk I\/O, where swap thrashing can cripple performance. Compare VPS plans with sufficient RAM for your workload at the provider comparison page<\/a>.<\/p>\n\n\n\n
3. Filesystem and Disk I\/O Tuning<\/h2>\n\n\n\n
Disk I\/O is often the bottleneck on virtual servers. These settings help optimize filesystem performance:<\/p>\n\n\n\n
# Increase the maximum number of open files\nfs.file-max = 2097152\n# Allow more inotify watchers (useful for file synchronization tools)\nfs.inotify.max_user_watches = 524288\n# Increase aio (async I\/O) request limit\nfs.aio-max-nr = 1048576<\/code><\/pre>\n\n\n\n
Choosing the Right I\/O Scheduler<\/h3>\n\n\n\n
Modern Linux kernels use the multi-queue block layer. For VPS instances backed by SSD storage (common with KVM-based providers), use the none<\/code> or nvme<\/code> scheduler. For traditional spinning disks, kyber<\/code> or bfq<\/code> may work better. Check your current scheduler with:<\/p>\n\n\n\n
cat \/sys\/block\/*\/queue\/scheduler<\/code><\/pre>\n\n\n\n
To switch to the none<\/code> scheduler (best for SSDs):<\/p>\n\n\n\n
echo 'ACTION==\"add|change\", KERNEL==\"sd*[!0-9]\", ATTR{queue\/scheduler}=\"none\"' | sudo tee \/etc\/udev\/rules.d\/60-iosched.rules<\/code><\/pre>\n\n\n\n
4. Applying Changes Permanently<\/h2>\n\n\n\n
Create a dedicated configuration file and apply all settings at once:<\/p>\n\n\n\n
sudo tee \/etc\/sysctl.d\/99-vps-performance.conf << 'EOF'\n# Network tuning\nnet.core.default_qdisc = fq\nnet.ipv4.tcp_congestion_control = bbr\nnet.core.rmem_max = 134217728\nnet.core.wmem_max = 134217728\nnet.ipv4.tcp_rmem = 4096 87380 134217728\nnet.ipv4.tcp_wmem = 4096 65536 134217728\nnet.ipv4.tcp_window_scaling = 1\nnet.ipv4.tcp_fin_timeout = 15\nnet.ipv4.tcp_tw_reuse = 1\nnet.core.somaxconn = 4096\nnet.ipv4.tcp_max_syn_backlog = 8192\nnet.core.netdev_max_backlog = 5000\n# Memory tuning\nvm.swappiness = 10\nvm.dirty_background_ratio = 5\nvm.dirty_ratio = 10\nvm.max_map_count = 262144\n# Filesystem tuning\nfs.file-max = 2097152\nfs.inotify.max_user_watches = 524288\nfs.aio-max-nr = 1048576\nEOF\nsudo sysctl -p \/etc\/sysctl.d\/99-vps-performance.conf<\/code><\/pre>\n\n\n\n
5. Verifying Performance Gains<\/h2>\n\n\n\n
After applying these optimizations, benchmark your VPS to measure improvement:<\/p>\n\n\n\n