How to benchmark your Linux system - hallaliedids

In the world of consumer electronics, benchmarks are everything. To a greater extent than specs, or account accounts, and certainly more than merchandising materials, benchmarks generate you meaningful information about the capabilities of a given piece of hardware, be IT a single subsystem—like a PC's GPU—or several subsystems in concert.

Unfortunately, many common benchmarks (peculiarly those built into games) only hunt in Windows. Cinebench, PCMark, 3DMark, and CrystalDiskMark are popular Windows tests, but have no Linux equivalent.

If you exit looking PC bench mark results, in that location's a very strong chance the tests won't perfectly interpret to public presentation under Linux, since they were equiprobable run in Windows. This is particularly true if certain hardware has small support in the Linux kernel. However, in that location are still slew of tests you can run in Linux, and the vast legal age of them are free.

Testing in Linux

Linux users can witness an easy-to-use test for their systems in the Gnome Disks utility, which comes with both the Gnome 3 and Ubuntu's Unity desktops. Though the utility is most ofttimes used to administer disk partitions and software Foray into, information technology features a built-in benchmark. It's beautiful basic, merely testament suffice for a general overview. Simply research for Disks in Ubuntu's dart (or Gnomes Activities panel) to find the utility.

The Disks utility benchmark operative on the Gnome 3 desktop.

A quick search for benchmark in Ubuntu's Software Marrow leave yield a few interesting entries. The first will prospective be the System Profiler and Benchmark application. This program is really useful for getting detailed system information via a GUI, simply the benchmarks are a bit lacking and not necessarily modality of real-world custom. There are six benchmarks total, all of which run the CPU.

There are several entries for benchmarking tools in Ubuntu's Software program Center.

The Computer software Midpoint list will as wel admit individual tests. These can be fine to use, but they can be tedious to open and configure manually. Keep your oculus down for an entry called Phoronix Test Suite, or PTS for short. The Phoronix Test Suite is a powerful program that can run a single tryout, or an entire battery. PTS offers any intrinsical suites (compendium of tests), operating room you can design your own entourage. When tests are realised, you can choose to upload the test results to openbenchmarking.org, where other users can see your results and even run the exact same tests happening their PC.

The System Profiler coating leaves a lot to constitute desired in the benchmarking

The prizewinning part of PTS is the automation. Tests and suites are altogether defined in XML files that you can edit American Samoa you see fit. If you mess up piece creating a custom suite on the program line line, don't worry about information technology; you can simply open the cortege XML file located in the folder ~/.phoronix-test-suite/test-suites/local . When you run a test or rooms for the first time, PTS leave attempt to fetch the test for you. If a test requires a dependency, PTS will let you know, but will still allow you to continue. If the dependency is non installed, the test that requires it volition non run.

Phoronix Test Retinue wish essay to download and instal the test software the commencement time it runs.

Testing with the Dell XPS 13 Developer Edition

To ostentate what PTS can do, I ran a custom rooms of tests on a 2015 Dell XPS 13 Developer Edition that came preloaded with Ubuntu Desktop 14.04 LTS.

To make the suite, I opening installed Phoronix Test Suite, which required the packages php5-CLI and php5-gadolinium. Once PTS was installed, I created my suite using the command phoronix-test-suite build-suite. PTS presents a list of all the supported tests. Most of the tests are give up to use, only any require purchase (mostly retail games same BioShock: Unnumberable), which I avoided.

My completed suite consists of 10 tests (though some tests ravel multiple times with different settings) that I felt reflect an norm screen background experience. For instance I chose IOZone to mental test the read and write performance of computer storage devices; Unigen's Shangri-la to test artwork performance; RAMspeed for memory; versatile encoding and decoding tests; a Linux kernal compiling; a test for file cabinet compaction; and single for encoding.

Once I added all of the tests I hot, I preserved and exited, only larboard the terminal window open. Just to make in for everything was on the up-and-high, I opened the XML file to look for typos or tests that I power take in added in error.

When everything checked out, I only ran phoronix-test-entourage persist <rooms name>. On the first attempt, PTS let me know that I needful to fulfill some dependencies, and so I made sure to install the requisite packages. After that, PTS was all set to run the tests.

PTS graphs the results of the unshared tests in a entourage.

If you're interested, you can check stunned the terminal results at openbenchmarking.org.

One time you have your benchmark results, you can purpose them as a baseline. When you swap computer hardware or make tweaks to your system settings, run the claim same tests again to measure the shock of that change.

A few notes about benchmarking

Running benchmarks can seem straightforward at first, but on that point are whole lot of things that dismiss flip off your results. Foremost, it's a good idea to keep a PC plugged in, as anti to spurting on battery; turn off any power-saving options; and turn off its hibernate and sopor functions for the plugged-in power profile while running tests. (The exception would beryllium if you're specifically performing a battery run-bolt down test.) It's also a good idea to close any other unprotected applications to maximize the RAM and CPU resources available for testing. If performing tests happening your storage devices, make a point they have ample free blank space for the test files.

If you prefer to extend to tests outside of the Phoronix Test Suite, the important thing to remember is that the build of the screen computer software and the console command misused to race it remain the same across systems. Keeping copies of your test software and a list of the relevant commands on an external hard drive in will save boatloads of fourth dimension when it comes to testing, and bequeath allow you to run tests on machines without an internet connectedness (provided you have any necessary dependencies on the drive as well). Always remember: Consistency is key to testing.

And finally, it's always epochal to know what benchmarks matter to you. If you're a spreadsheet power substance abuser, you probably put on't care astir gambling performance, and bench vise-versa. Design your tests for your needs, and you'll gain better insight into vindicatory how well your machine is working for you.

Source: https://www.pcworld.com/article/410691/how-to-benchmark-your-linux-system.html

Posted by: hallaliedids.blogspot.com

Share this post