Date: Fri 04 Apr 2025 04:11:53 PM PDT
Test set: performance
Kernel: 6.14.0-63.fc42.x86_64
Release: Fedora release 42 (Adams)
Result: PASS
Failed Tests: None
Warned Tests: None
============================================================
Starting test ./secureboot/check_SB_signature
pesign is required to check the secure boot signature
Starting test ./performance/lmbench3
cd src && make
make[1]: Entering directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src'
gmake[2]: Entering directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src'
gmake[2]: Nothing to be done for 'all'.
gmake[2]: Leaving directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src'
gmake[2]: Entering directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src'
gmake[2]: Nothing to be done for 'opt'.
gmake[2]: Leaving directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src'
make[1]: Leaving directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src'
cd src && make results
make[1]: Entering directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src'
gmake[2]: Entering directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src'
gmake[2]: Nothing to be done for 'all'.
gmake[2]: Leaving directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src'
gmake[2]: Entering directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src'
gmake[2]: Nothing to be done for 'opt'.
gmake[2]: Leaving directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src'
=====================================================================
L M B E N C H C ON F I G U R A T I O N
----------------------------------------
You need to configure some parameters to lmbench. Once you have configured
these parameters, you may do multiple runs by saying
"make rerun"
in the src subdirectory.
NOTICE: please do not have any other activity on the system if you can
help it. Things like the second hand on your xclock or X perfmeters
are not so good when benchmarking. In fact, X is not so good when
benchmarking.
=====================================================================
Hang on, we are calculating your timing granularity.
OK, it looks like you can time stuff down to 5000 usec resolution.
Hang on, we are calculating your timing overhead.
OK, it looks like your gettimeofday() costs 0 usecs.
Hang on, we are calculating your loop overhead.
OK, it looks like your benchmark loop costs 0.00000000 usecs.
=====================================================================
If you are running on an MP machine and you want to try running
multiple copies of lmbench in parallel, you can specify how many here.
Using this option will make the benchmark run 100x slower (sorry).
NOTE: WARNING! This feature is experimental and many results are
known to be incorrect or random!
MULTIPLE COPIES [default 1] Options to control job placement
1) Allow scheduler to place jobs
2) Assign each benchmark process with any attendent child processes
to its own processor
3) Assign each benchmark process with any attendent child processes
to its own processor, except that it will be as far as possible
from other processes
4) Assign each benchmark and attendent processes to their own
processors
5) Assign each benchmark and attendent processes to their own
processors, except that they will be as far as possible from
each other and other processes
6) Custom placement: you assign each benchmark process with attendent
child processes to processors
7) Custom placement: you assign each benchmark and attendent
processes to processors
Note: some benchmarks, such as bw_pipe, create attendent child
processes for each benchmark process. For example, bw_pipe
needs a second process to send data down the pipe to be read
by the benchmark process. If you have three copies of the
benchmark process running, then you actually have six processes;
three attendent child processes sending data down the pipes and
three benchmark processes reading data and doing the measurements.
Job placement selection: =====================================================================
Several benchmarks operate on a range of memory. This memory should be
sized such that it is at least 4 times as big as the external cache[s]
on your system. It should be no more than 80% of your physical memory.
The bigger the range, the more accurate the results, but larger sizes
take somewhat longer to run the benchmark.
MB [default 21997] Checking to see if you have 21997 MB; please wait for a moment...
Hang on, we are calculating your cache line size.
OK, it looks like your cache line is 64 bytes.
=====================================================================
lmbench measures a wide variety of system performance, and the full suite
of benchmarks can take a long time on some platforms. Consequently, we
offer the capability to run only predefined subsets of benchmarks, one
for operating system specific benchmarks and one for hardware specific
benchmarks. We also offer the option of running only selected benchmarks
which is useful during operating system development.
Please remember that if you intend to publish the results you either need
to do a full run or one of the predefined OS or hardware subsets.
SUBSET (ALL|HARWARE|OS|DEVELOPMENT) [default all] =====================================================================
This benchmark measures, by default, file system latency. That can
take a long time on systems with old style file systems (i.e., UFS,
FFS, etc.). Linux' ext2fs and Sun's tmpfs are fast enough that this
test is not painful.
If you are planning on sending in these results, please don't do a fast
run.
If you want to skip the file system latency tests, answer "yes" below.
SLOWFS [default no] =====================================================================
If you are running on an idle network and there are other, identically
configured systems, on the same wire (no gateway between you and them),
and you have rsh access to them, then you should run the network part
of the benchmarks to them. Please specify any such systems as a space
separated list such as: ether-host fddi-host hippi-host.
REMOTE [default none] =====================================================================
Calculating mhz, please wait for a moment...
I think your CPU mhz is
4503 MHz, 0.2221 nanosec clock
but I am frequently wrong. If that is the wrong Mhz, type in your
best guess as to your processor speed. It doesn't have to be exact,
but if you know it is around 800, say 800.
Please note that some processors, such as the P4, have a core which
is double-clocked, so on those processors the reported clock speed
will be roughly double the advertised clock rate. For example, a
1.8GHz P4 may be reported as a 3592MHz processor.
Processor mhz [default 4503 MHz, 0.2221 nanosec clock] =====================================================================
We need a place to store a 21997 Mbyte file as well as create and delete a
large number of small files. We default to /usr/tmp. If /usr/tmp is a
memory resident file system (i.e., tmpfs), pick a different place.
Please specify a directory that has enough space and is a local file
system.
FSDIR [default /usr/tmp] =====================================================================
lmbench outputs status information as it runs various benchmarks.
By default this output is sent to /dev/tty, but you may redirect
it to any file you wish (such as /dev/null...).
Status output file [default /dev/tty] =====================================================================
There is a database of benchmark results that is shipped with new
releases of lmbench. Your results can be included in the database
if you wish. The more results the better, especially if they include
remote networking. If your results are interesting, i.e., for a new
fast box, they may be made available on the lmbench web page, which is
http://www.bitmover.com/lmbench
Mail results [default yes] OK, no results mailed.
=====================================================================
Confguration done, thanks.
There is a mailing list for discussing lmbench hosted at BitMover.
Send mail to majordomo@bitmover.com to join the list.
make[1]: Leaving directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src'
L M B E N C H 3 . 0 S U M M A R Y
------------------------------------
(Alpha software, do not distribute)
Basic system parameters
------------------------------------------------------------------------------
Host OS Description Mhz tlb cache mem scal
pages line par load
bytes
--------- ------------- ----------------------- ---- ----- ----- ------ ----
muamba-te Linux 6.7.1-2 x86_64-linux-gnu 4488 64 1
muamba-te Linux 6.8.1-3 x86_64-linux-gnu 4488 64 1
muamba-te Linux 6.9.1-2 x86_64-linux-gnu 4488 64 1
muamba-te Linux 6.11.0- x86_64-linux-gnu 4488 64 1
muamba-te Linux 6.11.0- x86_64-linux-gnu 4488 64 1
muamba-te Linux 6.12.1- x86_64-linux-gnu 4488 64 1
muamba-te Linux 6.13.1- x86_64-linux-gnu 4488 64 1
mwamba.TE Linux 6.14.0- x86_64-linux-gnu 4503 64 1
Processor, Processes - times in microseconds - smaller is better
------------------------------------------------------------------------------
Host OS Mhz null null open slct sig sig fork exec sh
call I/O stat clos TCP inst hndl proc proc proc
--------- ------------- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
muamba-te Linux 6.7.1-2 4488 0.15 0.25 1.97 3.82 6.09 0.29 2.17 720. 3103 4485
muamba-te Linux 6.8.1-3 4488 0.12 0.21 1.68 3.02 4.14 0.18 1.41 386. 1790 2516
muamba-te Linux 6.9.1-2 4488 0.14 0.22 1.82 3.27 4.38 0.20 1.52 445. 1986 2563
muamba-te Linux 6.11.0- 4488 0.26 0.43 3.64 6.62 9.27 0.39 3.06 985. 4143 5770
muamba-te Linux 6.11.0- 4488 0.12 0.20 1.76 3.19 4.29 0.18 1.46 405. 1922 2730
Context switching - times in microseconds - smaller is better
-------------------------------------------------------------------------
Host OS 2p/0K 2p/16K 2p/64K 8p/16K 8p/64K 16p/16K 16p/64K
ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw
--------- ------------- ------ ------ ------ ------ ------ ------- -------
muamba-te Linux 6.7.1-2 2.6300 2.8100 3.2000 3.5500 3.8900 3.87000 3.97000
muamba-te Linux 6.8.1-3 2.9300 2.9000 2.9300 3.2500 3.7300 3.66000 3.94000
muamba-te Linux 6.9.1-2 3.0400 2.6800 3.0000 3.4400 3.4100 3.67000 3.82000
muamba-te Linux 6.11.0- 2.6400 4.6400 5.4400 36.0 39.5 22.0 38.4
muamba-te Linux 6.11.0- 2.6000 2.0200 2.4000 2.6600 4.9100 4.79000 5.65000
muamba-te Linux 6.12.1- 3.1000 2.7500 2.8900 3.3000 3.2200 3.69000 3.81000
muamba-te Linux 6.13.1- 2.9400 2.7500 2.8900 3.4700 3.2100 4.62000 6.35000
mwamba.TE Linux 6.14.0- 3.2900 2.9500 3.2700 3.7800 6.1700 4.21000 3.63000
*Local* Communication latencies in microseconds - smaller is better
---------------------------------------------------------------------
Host OS 2p/0K Pipe AF UDP RPC/ TCP RPC/ TCP
ctxsw UNIX UDP TCP conn
--------- ------------- ----- ----- ---- ----- ----- ----- ----- ----
muamba-te Linux 6.7.1-2 2.630 10.6 12.0 14.0 16.5 30.
muamba-te Linux 6.8.1-3 2.930 7.323 7.55 13.0 15.3 30.
muamba-te Linux 6.9.1-2 3.040 8.082 9.00 16.6 17.5 32.
muamba-te Linux 6.11.0- 2.640 12.3 13.2 26.4 31.2 68.
muamba-te Linux 6.11.0- 2.600 6.574 7.11 12.5 15.7 31.
muamba-te Linux 6.12.1- 3.100 13.9 15.7 30.
muamba-te Linux 6.13.1- 2.940 13.8 16.3 29.
mwamba.TE Linux 6.14.0- 3.290 15.7 19.3 32.
File & VM system latencies in microseconds - smaller is better
-------------------------------------------------------------------------------
Host OS 0K File 10K File Mmap Prot Page 100fd
Create Delete Create Delete Latency Fault Fault selct
--------- ------------- ------ ------ ------ ------ ------- ----- ------- -----
muamba-te Linux 6.7.1-2 40.6 20.2 28.2 24.3 1619.0K 0.633 0.00680 1.621
muamba-te Linux 6.8.1-3 18.5 22.3 26.1 25.1 969.2K 0.389 0.00550 1.090
muamba-te Linux 6.9.1-2 101.3 437.1 57.5 55.8 2339.8K 0.407 0.00640 1.138
muamba-te Linux 6.11.0- 24.6 33.0 27.8 27.2 2163.4K 0.682 0.00610 2.317
muamba-te Linux 6.11.0- 19.8 23.5 27.5 26.7 2222.8K 0.278 0.00620 1.103
muamba-te Linux 6.12.1- 55.3 21.0 28.3 26.2 2235.9K
muamba-te Linux 6.13.1- 27.2 22.5 28.2 25.3 2630.7K
mwamba.TE Linux 6.14.0- 20.3 21.2 30.6 25.4 3410.4K
*Local* Communication bandwidths in MB/s - bigger is better
-----------------------------------------------------------------------------
Host OS Pipe AF TCP File Mmap Bcopy Bcopy Mem Mem
UNIX reread reread (libc) (hand) read write
--------- ------------- ---- ---- ---- ------ ------ ------ ------ ---- -----
muamba-te Linux 6.7.1-2 4030 10.K 6348 11.9K 20.7K 13.2K 8383.1 18.K 4652.
muamba-te Linux 6.8.1-3 3744 7820 7158 12.2K 22.1K 13.8K 8583.4 19.K 5113.
muamba-te Linux 6.9.1-2 3574 7838 4392 11.6K 20.5K 13.5K 6684.3 17.K 4552.
muamba-te Linux 6.11.0- 1986 7496 1876 12.0K 22.2K 13.7K 7679.3 18.K 5077.
muamba-te Linux 6.11.0- 3811 8053 5801 11.4K 22.1K 13.7K 7793.9 18.K 4766.
muamba-te Linux 6.12.1- 3354 7086 6323 12.2K 18.7K 11.1K 5839.4 16.K 4362.
muamba-te Linux 6.13.1- 3765 7029 6221 12.0K 21.8K 12.7K 7654.6 18.K 4896.
mwamba.TE Linux 6.14.0- 3482 6316 4932 3426.4 20.3K 9852.7 6879.4 18.K 4898.