kcbenchrate - Man Page

Linux kernel compile benchmark, rate edition (still experimental)


kcbenchrate [options]


On each CPU in a system compile one Linux kernel to benchmark the throughput of a system or test its stability. It will measure how long it took to compile these kernels and will use this to calculate how many kernels the machine can build this way per hour.

Kcbenchrate compliments kcbench. Both are quite similar, but work slightly different:

NOTE: The optimal number of workers ('-w') that delivers the best result depends on the machine being benched. See the section "On the Default Number of Workers" below for details.

IMPORTANT: To get comparable results from different machines you should use the exact same operating system on all of them. There are multiple reasons for this recommendation, but one of the main reasons is: the Linux source code automatically downloaded to compile depends on the compiler being used.

If you choose to ignore this recommendation at least make sure to hard code the Linux version to compile ('-s 5.4'), as for example compiling 5.7 will take longer than 5.4 or 4.19 and thus lead to results one cannot compare. Also, make sure the compiler used on the systems you want to compare is from similar, as for example gcc10 will try harder to optimize the code than gcc8 or gcc9 and thus take more time.


-b,  --bypass

After starting a worker wait just a tenths of a second before launching the next to start the workers a lot faster than usualy. This can he useful to create a lot of load quickly, but the benchmark result might be slightly inaccurate due to caching effects.

-h,  --help

Show usage.

-i,  --iterations int

Determines the number of kernels that each worker will compile before the end result it printed. Default: 2

-j,  --jobs int(,int, int, ...)

Number of jobs to use when compiling a kernel('make -j #'). In kcbenchrate the default is '1' and normally should not be changed.

-m,  --modconfig

Instead of using a config generated with 'defconfig' use one built by 'allmodconfig' and compile modules as well. Takes a lot longer to compile, which is more suitable for machines with a lot of fast CPU cores.

-o,  --outputdir dir

Use path to compile Linux. Passes 'O=dir/kcbench-worker/' to make when calling it to compile a kernel; use a temporary directory if not given.

-s,  --src path|version

Look for sources in path, ~/.cache/kcbench/linux-version or /usr/share/kcbench/linux-version. If not found try to download version automatically unless '--no-download' was specified.

-v,  --verbose

Increase verboselevel; option can be given multiple times.

-w,  --workers int

Number of workers to use. Default: Number of CPUs. The optimal setting will depend on the particual machine. See On the Default Number of Workers for details.

-V,  --version

Output program version.

--cc exec

Use exec as target compiler.

--cross-compile arch

EXPERIMENTAL: Cross compile the Linux kernel. Cross compilers for this task are packaged in some Linux distribution. There are also for pre-compiled compilers available on the internet, for example here: https://mirrors.edge.kernel.org/pub/tools/crosstool/

Values of arch that kcbench/kcbenchrate understand: arm arm64 aarch64 riscv riscv64 powerpc powerpc64 x86_64

Building for archs not directly supported by kcbench/kcbenchrate should work, too, if you export ARCH= and CROSS_COMPILE= just like you would when normally cross compiling a Linux kernel. Do not use '--cross-compile' in that case and keep in mind that kcbench/kcbenchrate configure the compiled Linux kernel with the make target 'defconfig' (or 'allmodconfig', if you specify '-m'), which might be unusual for the arch in question, but normally should be good enough for benchmarking.

Be aware there is a bigger risk running into compile errors (see below) when cross compiling.

--crosscomp-scheme scheme

On Linux distributions that are known to ship cross compilers kcbench/kcbenchrate will assume you want to use those. This parameter allows to use a one of the various different scheme in cases this automatic detection fails or work you want kcbench/kcbenchrate to find them using a 'generic' scheme that should work with compilers from various sources, which is the default on unknown distributions.

Valid values of scheme: debian fedora generic redhat ubuntu

--hostcc exec

Use exec as host compiler.


Run endlessly to create system load.


Set LLVM=1 to use clang as compiler and LLVM utilities as GNU binutils substitute.

--add-make-args string

Pass additional flags found in string to make when creating the config or building the kernel. This option is meant for experts that want to try unusual things, like specifing a special linker (--add-make-args 'LD=ld.lld'). Use with caution!


Never download Linux kernel sources from the web automatically.

--savefailedlogs path

Save log of failed compile runs to path.

On the Default Number of Workers

The optimal number of workers (-w) depends on the machine being benched. On most systems you will achieve the best result if the number of workers matches the number of CPU cores, that's why this is the default. But some systems are a bit faster if they are oversubscribed a little. Others are quicker if only the real cores are utilized and those supported thanks to SMT (Simultaneous Multi-Threading, also called Hyper-threading/HT by Intel) are left idle. For details and some results that show this see the kcbench man page in the section ON THE DEFAULT NUMBER OF JOBS. Ideally kcbenchrate would do what kcbench does and try a few settings to narrow down the optimal setting. As this would take quite a while this exercise is left to the user. Impatient users should consider finding the optimal number of jobs with kcbench and and then start kernbenchrate with as many workers, as that likely will lead to a quite good or even the optimal setting for kcbenchrate.

On Failed Runs Due to Compilation Errors

As long as you are using a settled GCC version to natively compile the source of a current Linux kernel for popular architectures like ARM, ARM64/Aarch64, or x86_64 the compilation is unlikely to fail. For other cases there is a bigger risk that compilation will fail due to factors outside of what kcbench/kcbenchrate control. They nevertheless try to catch a few common problems and warn, but they can not catch them all, as there are to many factors involved:


Running benchmarks is very tricky. Here are a few of the aspects you should keep mind when doing so:

If you want to work against that consider using '-m' to build an allmodconfig configuration with modules; comping a newer, more complex Linux kernel version can also help.


To let kcbenchrate decide everything automatically simply run:

$ kcbenchrate


By default the line you are looking for is this:

4 workers completed 8 kernels so far (avrg: 1100.75 s/run) with a rate of 13.08 kernels/hour.

On this quad-core processor four workers each compiled two kernels. On average, it took each worker 1100.77 seconds to compile one kernel image. With a speed like this the machine can compile 13.08 kernels per hour (3600/1100.75*4).

Missing Features

See Also

kcbench(1), time(1)


Thorsten Leemhuis <linux [AT] leemhuis [DOT] info>

Referenced By


Version 0.9