Linux Benchmarking made easy
No longer do you need to get lots of tools and software to benchmark a system. With something like Phoronix Test Suite, the whole process has become a lot easier.
So what is Phoronix Test Suite
It's a free and open-source benchmark software that is cross-compatible with multiple operating systems.
Installing Phoronix Test Suite
Installation on Ubuntu and Derivatives
- Download the
.deb
file from the link. - Navigate to the location of the file and run.
$ sudo dpkg -i phoronix-test-suite*.deb
Installation on Other Linux Distributions
- Download the Universal
.tar.gz
file. - Extract the folder and navigate to the extracted folder.
- Run the following command.
$ sudo ./install-sh
Getting Started
Run the Phoronix Test Suite running by executing
$ phoronix-test-suite
Accept the EULA and conditions and wait for the dependencies to finish installing.
To get System Info
$ phoronix-test-suite system-info
Pretty self-explanatory! The result will be similar to shown in the image above.
To get sensors data
$ phoronix-test-suite system-sensors
To view all tests run
$ phoronix-test-suite list-all-tests
To view all available test suites.
$ phoronix-test-suite list-available-suites
Run your first benchmark
Let's try to run a simple benchmark like webp
, to run enter the command given below
$ phoronix-test-suite benchmark webp
You will be presented with several configuration options for the benchmark. The following options will be shown for the webp benchmark. Choose the appropriate option using the indexes of the options and press enter.
After the test is completed, press Enter to open the result in a browser.
The benchmark result file would open in the browser.
Configuring The results to see different types of graphs
The more test configurations you run, the more options you will get for graphs that you want to display.
You can also export benchmark data in various formats including CSV, PDFs, HTML, etc.
That's all for now. This article is part of a series on benchmarking with Phoronix Test Suite.
Top comments (1)
One additional step I needed to take was to run the command
to install necessary dependencies (after going down the .deb route)