{"id":18782,"date":"2023-07-13T08:26:21","date_gmt":"2023-07-13T08:26:21","guid":{"rendered":"https:\/\/webhostinggeeks.com\/howto\/?p=18782"},"modified":"2023-10-14T12:01:29","modified_gmt":"2023-10-14T12:01:29","slug":"how-to-setup-sysbench-for-cpu-and-memory-benchmarking-on-a-linux-machine","status":"publish","type":"post","link":"https:\/\/webhostinggeeks.com\/howto\/how-to-setup-sysbench-for-cpu-and-memory-benchmarking-on-a-linux-machine\/","title":{"rendered":"How to Setup Sysbench for CPU and Memory Benchmarking on a Linux Machine"},"content":{"rendered":"

\"How<\/p>\n

Benchmarking is a crucial aspect of understanding the performance of any system. For webmasters and system administrators, it’s essential to know the capabilities of managed web servers<\/a>, especially when hosting applications or websites that demand high resources.<\/p>\n

One of the most popular tools for benchmarking Linux systems is Sysbench. This tool provides a suite of tests to measure the performance of various system parameters, including CPU and memory.<\/p>\n

In this tutorial, we will guide you through the process of setting up Sysbench on a Linux machine and using it to perform CPU and memory benchmarking tests. By the end of this guide, you’ll have a clear understanding of your server’s capabilities and how to interpret the results.<\/p>\n

Let’s get started.<\/p>\n

Step 1: Installing Sysbench<\/h2>\n

First, update your system’s package list:<\/p>\n

sudo apt update<\/pre>\n
Install Sysbench using the package manager:<\/p>\n
sudo apt install sysbench<\/pre>\n
Step 2: Running the CPU Benchmark<\/h2>\n
To test the CPU performance, use the following command:<\/p>\n
sysbench cpu run<\/pre>\n
Example:<\/p>\n
\r\nsysbench 1.0.20 (using bundled LuaJIT 2.1.0-beta2)\r\n\r\nRunning the test with following options:\r\nNumber of threads: 1\r\n\r\nInitializing random number generator from current time\r\n\r\n\r\nPrime numbers limit: 10000\r\n\r\nInitializing worker threads...\r\n\r\nThreads started!\r\n\r\nCPU speed:\r\n    events per second:  1234.56\r\n\r\nGeneral statistics:\r\n    total time:                          10.0012s\r\n    total number of events:              12346\r\n\r\nLatency (ms):\r\n         min:                                  0.81\r\n         avg:                                  0.81\r\n         max:                                  1.23\r\n         95th percentile:                      0.82\r\n         sum:                                  9999.12\r\n\r\nThreads fairness:\r\n    events (avg\/stddev):           12346.0000\/0.00\r\n    execution time (avg\/stddev):   9.9991\/0.00\r\n<\/pre>\n
The above command will run the test using a single thread. If you want to test using multiple threads, specify the number of threads using the –threads option:<\/p>\n
sysbench cpu --threads=4 run<\/pre>\n
Example:<\/p>\n
\r\nsysbench 1.0.20 (using bundled LuaJIT 2.1.0-beta2)\r\n\r\nRunning the test with following options:\r\nNumber of threads: 4\r\n\r\nInitializing random number generator from current time\r\n\r\n\r\nPrime numbers limit: 10000\r\n\r\nInitializing worker threads...\r\n\r\nThreads started!\r\n\r\nCPU speed:\r\n    events per second:  4920.78\r\n\r\nGeneral statistics:\r\n    total time:                          10.0007s\r\n    total number of events:              49208\r\n\r\nLatency (ms):\r\n         min:                                  0.81\r\n         avg:                                  0.82\r\n         max:                                  1.25\r\n         95th percentile:                      0.83\r\n         sum:                                  39996.48\r\n\r\nThreads fairness:\r\n    events (avg\/stddev):           12302.0000\/12.34\r\n    execution time (avg\/stddev):   9.9991\/0.01\r\n<\/pre>\n
Step 3: Running the Memory Benchmark<\/h2>\n
To test the memory read and write speed, use the following command:<\/p>\n
sysbench memory run<\/pre>\n
Example:<\/p>\n
\r\nsysbench 1.0.20 (using bundled LuaJIT 2.1.0-beta2)\r\n\r\nRunning the test with following options:\r\nNumber of threads: 1\r\nMemory block size: 1K\r\n\r\nMemory operations type: write\r\nScope: global\r\n\r\nInitializing worker threads...\r\n\r\nThreads started!\r\n\r\nTotal operations: 3000000 (299999.70 per second)\r\n\r\n30000.00 MiB transferred (2999.99 MiB\/sec)\r\n\r\n\r\nGeneral statistics:\r\n    total time:                          10.0001s\r\n    total number of events:              3000000\r\n\r\nLatency (ms):\r\n         min:                                  0.00\r\n         avg:                                  0.00\r\n         max:                                  0.01\r\n         95th percentile:                      0.00\r\n         sum:                                  10.00\r\n\r\nThreads fairness:\r\n    events (avg\/stddev):           3000000.0000\/0.00\r\n    execution time (avg\/stddev):   10.0000\/0.00\r\n<\/pre>\n
By default, Sysbench tests the memory read operations. If you want to test write operations, use the –memory-oper option:<\/p>\n
sysbench memory --memory-oper=write run<\/pre>\n
Example:<\/p>\n
\r\nsysbench 1.0.20 (using bundled LuaJIT 2.1.0-beta2)\r\n\r\nRunning the test with following options:\r\nNumber of threads: 1\r\nMemory block size: 1K\r\n\r\nMemory operations type: write\r\nScope: global\r\n\r\nInitializing worker threads...\r\n\r\nThreads started!\r\n\r\nTotal operations: 4000000 (399999.60 per second)\r\n\r\n40000.00 MiB transferred (3999.96 MiB\/sec)\r\n\r\n\r\nGeneral statistics:\r\n    total time:                          10.0001s\r\n    total number of events:              4000000\r\n\r\nLatency (ms):\r\n         min:                                  0.00\r\n         avg:                                  0.00\r\n         max:                                  0.01\r\n         95th percentile:                      0.00\r\n         sum:                                  10.00\r\n\r\nThreads fairness:\r\n    events (avg\/stddev):           4000000.0000\/0.00\r\n    execution time (avg\/stddev):   10.0000\/0.00\r\n<\/pre>\n
Step 4: Interpreting the Results<\/h2>\n
A shorter total time can indicate better system performance, especially when comparing similar tests. However, it’s essential to consider this metric in conjunction with others, as a shorter test time with a high error rate, for instance, isn’t indicative of better performance.<\/p>\n
Ops\/sec is a direct indicator of your system’s throughput. A higher ops\/sec value typically means your system can handle more operations in a given time frame, leading to better performance. For instance, if you’re running a database server, a higher ops\/sec means your server can handle more queries per second, leading to faster response times for end-users.<\/p>\n
Latency is crucial when it comes to user experience. Lower latency means operations are completed faster, which is especially vital for tasks that require real-time responses, like video streaming or online gaming. If you’re hosting a website, lower latency can lead to faster page load times, enhancing user experience.<\/p>\n
1. CPU Test (Single Thread)<\/strong>:<\/p>\n