ituietst312-5.14.0-362.24.1.0.1.el9_3

MBW

This is a basic/simple memory (RAM) bandwidth benchmark for memory copy operations. Learn more via the OpenBenchmarking.org test page.

t-test1

This is a test of t-test1 for basic memory allocator benchmarks. Note this test profile is currently very basic and the overall time does include the warmup time of the custom t-test1 compilation. Improvements welcome. Learn more via the OpenBenchmarking.org test page.

Tinymembench

This benchmark tests the system memory (RAM) performance. Learn more via the OpenBenchmarking.org test page.

ctx_clock

Ctx_clock is a simple test program to measure the context switch time in clock cycles. Learn more via the OpenBenchmarking.org test page.

Hackbench

This is a benchmark of Hackbench, a test of the Linux kernel scheduler. Learn more via the OpenBenchmarking.org test page.

Count: 1 - Type: Thread

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: /oracle/lib/phoronix-test-suite/installed-tests/pts/hackbench-1.0.0/hackbench: line 2: ./hackbench_bin: No such file or directory

Count: 2 - Type: Thread

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: /oracle/lib/phoronix-test-suite/installed-tests/pts/hackbench-1.0.0/hackbench: line 2: ./hackbench_bin: No such file or directory

Count: 4 - Type: Thread

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: /oracle/lib/phoronix-test-suite/installed-tests/pts/hackbench-1.0.0/hackbench: line 2: ./hackbench_bin: No such file or directory

Count: 8 - Type: Thread

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: /oracle/lib/phoronix-test-suite/installed-tests/pts/hackbench-1.0.0/hackbench: line 2: ./hackbench_bin: No such file or directory

Count: 1 - Type: Process

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: /oracle/lib/phoronix-test-suite/installed-tests/pts/hackbench-1.0.0/hackbench: line 2: ./hackbench_bin: No such file or directory

Count: 16 - Type: Thread

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: /oracle/lib/phoronix-test-suite/installed-tests/pts/hackbench-1.0.0/hackbench: line 2: ./hackbench_bin: No such file or directory

Count: 2 - Type: Process

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: /oracle/lib/phoronix-test-suite/installed-tests/pts/hackbench-1.0.0/hackbench: line 2: ./hackbench_bin: No such file or directory

Count: 32 - Type: Thread

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: /oracle/lib/phoronix-test-suite/installed-tests/pts/hackbench-1.0.0/hackbench: line 2: ./hackbench_bin: No such file or directory

Count: 4 - Type: Process

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: /oracle/lib/phoronix-test-suite/installed-tests/pts/hackbench-1.0.0/hackbench: line 2: ./hackbench_bin: No such file or directory

Count: 8 - Type: Process

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: /oracle/lib/phoronix-test-suite/installed-tests/pts/hackbench-1.0.0/hackbench: line 2: ./hackbench_bin: No such file or directory

Count: 16 - Type: Process

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: /oracle/lib/phoronix-test-suite/installed-tests/pts/hackbench-1.0.0/hackbench: line 2: ./hackbench_bin: No such file or directory

Count: 32 - Type: Process

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: /oracle/lib/phoronix-test-suite/installed-tests/pts/hackbench-1.0.0/hackbench: line 2: ./hackbench_bin: No such file or directory

Stress-NG

Test: IO_uring

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: stress-ng: error: [3578280] io-uring: [3578288] terminated with an error, exit status=2 (stressor failed)

IPC_benchmark

IPC_benchmark is a Linux inter-process communication benchmark. Learn more via the OpenBenchmarking.org test page.

OSBench

OSBench is a collection of micro-benchmarks for measuring operating system primitives like time to create threads/processes, launching programs, creating files, and memory allocation. Learn more via the OpenBenchmarking.org test page.

perf-bench

This test profile is used for running Linux perf-bench, the benchmark support within the Linux kernel's perf tool. Learn more via the OpenBenchmarking.org test page.

pmbench

Pmbench is a Linux paging and virtual memory benchmark. This test profile will report the average page latency of the system. Learn more via the OpenBenchmarking.org test page.

Schbench

This is a benchmark of Schbench, a Linux kernel scheduler benchmark developed by Facebook/Meta. Learn more via the OpenBenchmarking.org test page.

WireGuard + Linux Networking Stack Stress Test

This is a benchmark of the WireGuard secure VPN tunnel and Linux networking stack stress test. The test runs on the local host but does require root permissions to run. The way it works is it creates three namespaces. ns0 has a loopback device. ns1 and ns2 each have wireguard devices. Those two wireguard devices send traffic through the loopback device of ns0. The end result of this is that tests wind up testing encryption and decryption at the same time -- a pretty CPU and scheduler-heavy workflow. Learn more via the OpenBenchmarking.org test page.

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status.

PostMark

This is a test of NetApp's PostMark benchmark designed to simulate small-file testing similar to the tasks endured by web and mail servers. This test profile will set PostMark to perform 25,000 transactions with 500 files simultaneously with the file sizes ranging between 5 and 512 kilobytes. Learn more via the OpenBenchmarking.org test page.

Ethr

Ethr is a cross-platform Golang-written network performance measurement tool developed by Microsoft that is capable of testing multiple protocols and conducting different measurements. Learn more via the OpenBenchmarking.org test page.

Server Address: localhost - Protocol: UDP - Test: Latency - Threads: 1

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Test: "Latency" for Protocol: "UDP" is not supported.

Server Address: localhost - Protocol: UDP - Test: Latency - Threads: 8

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Test: "Latency" for Protocol: "UDP" is not supported.

Server Address: localhost - Protocol: HTTP - Test: Latency - Threads: 1

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Invalid value "http" specified for parameter "-p".

Server Address: localhost - Protocol: HTTP - Test: Latency - Threads: 8

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Invalid value "http" specified for parameter "-p".

Server Address: localhost - Protocol: UDP - Test: Latency - Threads: 32

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Test: "Latency" for Protocol: "UDP" is not supported.

Server Address: localhost - Protocol: UDP - Test: Latency - Threads: 64

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Test: "Latency" for Protocol: "UDP" is not supported.

Server Address: localhost - Protocol: HTTP - Test: Latency - Threads: 32

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Invalid value "http" specified for parameter "-p".

Server Address: localhost - Protocol: HTTP - Test: Latency - Threads: 64

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Invalid value "http" specified for parameter "-p".

Server Address: localhost - Protocol: HTTP - Test: Bandwidth - Threads: 1

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Invalid value "http" specified for parameter "-p".

Server Address: localhost - Protocol: HTTP - Test: Bandwidth - Threads: 8

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Invalid value "http" specified for parameter "-p".

Server Address: localhost - Protocol: HTTP - Test: Bandwidth - Threads: 32

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Invalid value "http" specified for parameter "-p".

Server Address: localhost - Protocol: HTTP - Test: Bandwidth - Threads: 64

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Invalid value "http" specified for parameter "-p".

Server Address: localhost - Protocol: UDP - Test: Connections/s - Threads: 1

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Test: "Connections/s" for Protocol: "UDP" is not supported.

Server Address: localhost - Protocol: UDP - Test: Connections/s - Threads: 8

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Test: "Connections/s" for Protocol: "UDP" is not supported.

Server Address: localhost - Protocol: HTTP - Test: Connections/s - Threads: 1

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Invalid value "http" specified for parameter "-p".

Server Address: localhost - Protocol: HTTP - Test: Connections/s - Threads: 8

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Invalid value "http" specified for parameter "-p".

Server Address: localhost - Protocol: UDP - Test: Connections/s - Threads: 32

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Test: "Connections/s" for Protocol: "UDP" is not supported.

Server Address: localhost - Protocol: UDP - Test: Connections/s - Threads: 64

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Test: "Connections/s" for Protocol: "UDP" is not supported.

Server Address: localhost - Protocol: HTTP - Test: Connections/s - Threads: 32

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Invalid value "http" specified for parameter "-p".

Server Address: localhost - Protocol: HTTP - Test: Connections/s - Threads: 64

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: Error: Invalid value "http" specified for parameter "-p".

iPerf

iPerf is a network bandwidth throughput testing software. This test profile is used for automated testing of an iperf client and requires you have access to an iperf server. Learn more via the OpenBenchmarking.org test page.

BenchmarkMutex

BenchmarkMutex is a mutex benchmark created by Malte Skarupke. Learn more via the OpenBenchmarking.org test page.

Apache HTTP Server

This is a test of the Apache HTTPD web server. This Apache HTTPD web server benchmark test profile makes use of the wrk program for facilitating the HTTP requests over a fixed period time with a configurable number of concurrent clients. Learn more via the OpenBenchmarking.org test page.

Concurrent Requests: 4

ituietst312-5.14.0-362.24.1.0.1.el9_3: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status.