Run Unixbench Benchmark: Difference between revisions

From Leo's Notes
This page was last edited on 11 May 2023, at 06:17.
m Text replacement - "{{Highlight" to "{{highlight"
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
Unixbench is a benchmark program for unix based systems which was originally from Byte magazine.
Unixbench is a benchmark program for unix based systems which was originally from Byte magazine.


For more information, see https://code.google.com/p/byte-unixbench/
A copy of the source code can be found at https://git.steamr.com/others/byte-unixbench


== Linux ==
== Linux ==
On a clean installation of CentOS (or any other RedHat derivative), run the following:
Run the following:
   
   
{{highlight|lang=terminal|code=
{{highlight
# yum install -y mesa-libGL-devel libXext-devel libX11-devel perl-Time-HiRes make gcc wget glibc-devel git
| lang = terminal
# git clone https://github.com/kdlucas/byte-unixbench.git
| code = ## CentOS / Red Hat / Fedora
# yum install -y mesa-libGL-devel libXext-devel libX11-devel perl-Time-HiRes perl-FindBin make gcc wget glibc-devel git
## Or on Alpine Linux:
## apk add libc-dev perl make gcc wget libc-dev git libxext-dev libx11-dev perl-time-hires
# git clone https://git.steamr.com/others/byte-unixbench.git
# cd byte-unixbench/UnixBench
# cd byte-unixbench/UnixBench
# ./Run
# ./Run
}}
}}


{{Info|The benchmark takes time!|The benchmark will run once on one core. If your system has multiple cores, it will run again across all cores. This can take anywhere from 10s of minutes to nearly an hour.
{{Info|The benchmark takes time!|The benchmark will run once on one core. If your system has multiple cores, it will run again across all cores. This can take anywhere from tens of minutes to over an hour, depending on the system. I recommend you run this inside a {{code|screen}} session.


For the best result, run the benchmark on an idle system.}}
For the best result, run the benchmark on an idle system.}}
=== Docker ===
If for whatever reason you want to benchmark from within a container, the Unixbench Benchmark image is available at: https://git.steamr.com/docker/alpine-unixbench


=== Issues ===
=== Issues ===
Line 33: Line 41:
You should be able to run this on other Unix based systems including FreeBSD. Just make sure you have the proper dependencies installed.
You should be able to run this on other Unix based systems including FreeBSD. Just make sure you have the proper dependencies installed.


[[Category:Linux]]
{{Navbox Linux}}[[Category:Linux]]
[[Category:Benchmarks]]
[[Category:Benchmarks]]
[[Category:Guides]]
[[Category:Guides]]

Latest revision as of 06:17, 11 May 2023

Unixbench is a benchmark program for unix based systems which was originally from Byte magazine.

A copy of the source code can be found at https://git.steamr.com/others/byte-unixbench

Linux

Run the following:

## CentOS / Red Hat / Fedora
# yum install -y mesa-libGL-devel libXext-devel libX11-devel perl-Time-HiRes perl-FindBin make gcc wget glibc-devel git
## Or on Alpine Linux:
## apk add libc-dev perl make gcc wget libc-dev git libxext-dev libx11-dev perl-time-hires
# git clone https://git.steamr.com/others/byte-unixbench.git
# cd byte-unixbench/UnixBench
# ./Run
The benchmark takes time!
The benchmark will run once on one core. If your system has multiple cores, it will run again across all cores. This can take anywhere from tens of minutes to over an hour, depending on the system. I recommend you run this inside a screen session. For the best result, run the benchmark on an idle system.


Docker

If for whatever reason you want to benchmark from within a container, the Unixbench Benchmark image is available at: https://git.steamr.com/docker/alpine-unixbench


Issues

If you run this under Qemu, you might get:

gcc: error: missing argument to ‘-march=’
make: *** [pgms/arithoh] Error 1

You will need to add an extra option to in the Makefile:

-march=native

Other Systems

You should be able to run this on other Unix based systems including FreeBSD. Just make sure you have the proper dependencies installed.