centos swapper的最佳实践

Creating Swap Space
The first step in configuring swap is to create a swap file or partition. For most users, a swap file is more flexible and easier to manage than a dedicated partition. To create a 4GB swap file, use the following commands:

sudo dd if=/dev/zero of=/swapfile bs=1M count=4096  # Create a 4GB file filled with zeros
sudo chmod 600 /swapfile                         # Restrict permissions to root only
sudo mkswap /swapfile                            # Format the file as swap space
sudo swapon /swapfile                            # Enable the swap file immediately

To ensure the swap file is mounted automatically after a reboot, add the following line to /etc/fstab:

echo '/swapfile swap swap defaults 0 0' | sudo tee -a /etc/fstab

For systems requiring more swap or those preferring a traditional approach, you can create a swap partition using tools like fdisk or parted, format it with mkswap, and enable it with swapon. However, swap files are generally preferred for their simplicity.

Adjusting Swappiness
Swappiness is a kernel parameter that controls how aggressively the system moves data from RAM to swap. It ranges from 0 to 100, where 0 tells the kernel to avoid swap unless absolutely necessary, and 100 encourages aggressive swapping. For most servers, a value between 10 and 30 is ideal—it reduces unnecessary disk I/O while still providing a safety net for memory overflow. To adjust swappiness:

• Temporary change (takes effect immediately):

  sudo sysctl vm.swappiness=10
  

• Permanent change (persists after reboot):
  Edit /etc/sysctl.conf and add:

  vm.swappiness=10
  

  Then apply the changes with:

  sudo sysctl -p
  

This setting is particularly useful for memory-intensive workloads, where excessive swapping can degrade performance.

Optimizing Swap Size
The appropriate swap size depends on your system’s physical memory and workload. While older guidelines suggested 2x physical memory, modern systems with ample RAM often need less. Here’s a more nuanced approach:

• <4GB RAM: 2x physical memory (e.g., 4GB RAM → 8GB swap).
• 4–16GB RAM: Equal to physical memory (e.g., 8GB RAM → 8GB swap).
• 16–64GB RAM: 8GB swap (sufficient for most server workloads).
• 64–256GB RAM: 16GB swap (avoids overcommitting disk space).
• >256GB RAM: 32GB swap (rarely needed but provides a buffer).
  These recommendations balance performance and resource usage, ensuring swap is available when needed without wasting disk space.

Monitoring Swap Usage
Regular monitoring helps you understand swap behavior and identify potential issues. Use these commands to track swap usage:

• View total, used, and free swap:

  free -h
  

• List active swap devices/partitions:

  swapon --show
  

• Detailed memory/swap statistics:

  vmstat 1  # Shows swap in/out rates (si/so columns)
  

• Process-level memory/swap usage:

  top  # Check "Swap" column for individual processes
  

Monitoring helps you determine if your swap size is adequate or if you need to adjust swappiness.

Using Zram for Compressed Swap
Zram is a kernel feature that creates a compressed block device in RAM, acting as swap space. Unlike traditional swap on disk, zram avoids slow disk I/O by compressing data in memory. This is ideal for systems with limited RAM but can also improve performance by reducing reliance on disk-based swap. To set up zram:

1. Install the zram-config package:

   sudo yum install zram-config
   

2. Start the zram service:

   sudo systemctl start zram-config
   

3. Adjust the zram size (e.g., 4GB):
   Edit /etc/zram-config.conf and set:

   ZRAM_DEVICE_SIZE=4G
   

Zram is particularly effective for servers with high memory pressure, as it provides faster swap access while conserving disk space.

Important Considerations

• Avoid Swap on SSDs (If Possible): While modern SSDs are durable, frequent swap operations can still wear them out faster than HDDs. If your server has sufficient RAM, consider disabling swap entirely or using zram instead.
• Test Changes in a Non-Production Environment: Before applying swap configurations to production, test them in a staging environment to ensure they meet your performance and stability needs.
• Combine Multiple Optimization Strategies: For best results, combine techniques like adjusting swappiness, using zram, and monitoring swap usage. This holistic approach ensures your system balances memory and disk usage effectively.