VPS Benchmarking Rules

date
Jul 20, 2024
slug
vps-benchmarking-rules
status
Published
tags
VPSBenchmark
summary
type
Page
To ensure consistency and accuracy in our performance benchmarks, we strictly adhere to a comprehensive set of standardized rules for each test conducted on VPS instances. Here are the detailed guidelines:

VPS Freshness

  • New VPS Deployment: Each benchmark is conducted on a newly deployed VPS with no pre-installed software. This "fresh start" approach ensures that the results are not influenced by any previous configurations or installations.

VPS Configuration

  • CPU and RAM: Each VPS instance or VPS provider being evaluated uses a configuration with 2 CPU cores and 4 GB of RAM, or the closest available equivalent. This ensures uniform hardware resources and allows for objective testing across all providers.

Operating System

  • OS Version: The preferred operating system for benchmarks is Debian 12. If Debian 12 is not available, Debian 11 is used as a fallback. This choice ensures that the benchmarks are conducted on a stable and up-to-date Linux distribution.

System Updates

  • Latest Updates: Before running any benchmark, the system is updated to the latest version available. This includes all Linux updates to ensure that the VPS is running on the most recent and secure software versions.

Network Configuration

  • IP Versions: Both IPv4 and IPv6 are enabled for the benchmarks, if available. This dual-stack configuration allows for a comprehensive evaluation of network performance across different IP protocols.

Timing

  • Benchmark Execution Time: Benchmarks are consistently run between 12:00 PM and 1:00 PM in the instance's region. This fixed time window minimizes variations due to time-of-day effects on server load and network traffic.

Benchmarking Tool

  • YABS (Yet Another Bench Script): The YABS tool is used for all benchmarking tests. It provides detailed performance metrics, including CPU, memory, disk I/O, and network speed, which are crucial for evaluating the VPS capabilities.

By meticulously following these rules, we ensure that each benchmark is conducted under consistent conditions, allowing for accurate and reliable performance comparisons across different providers and instances.