News:
- BenchExec 1.9 adds a container mode that isolates each run from the host system and from other runs (disabled by now, will become default in BenchExec 2.0).
- We have published a paper titled Benchmarking and Resource Measurement on BenchExec and its background at SPIN 2015. It also contains a list of rules that you should always follow when doing benchmarking (and which BenchExec handles for you).
BenchExec provides three major features:
- execution of arbitrary commands with precise and reliable measurement and limitation of resource usage (e.g., CPU time and memory), and isolation against other running processes
- an easy way to define benchmarks with specific tool configurations and resource limits, and automatically executing them on large sets of input files
- generation of interactive tables and plots for the results
Contrary to other benchmarking frameworks, it is able to reliably measure and limit resource usage of the benchmarked tool even if it spawns subprocesses. In order to achieve this, it uses the cgroups feature of the Linux kernel to correctly handle groups of processes. For proper isolation of the benchmarks, it uses Linux user namespaces and an overlay filesystem to create a container that restricts interference of the executed tool with the benchmarking host. BenchExec is intended for benchmarking non-interactive tools on Linux systems. It measures CPU time, wall time, and memory usage of a tool, and allows to specify limits for these resources. It also allows to limit the CPU cores and (on NUMA systems) memory regions, and the container mode allows to restrict filesystem and network access. In addition to measuring resource usage, BenchExec can verify that the result of the tool was as expected, and extract further statistical data from the output. Results from multiple runs can be combined into CSV and interactive HTML tables, of which the latter provide scatter and quantile plots (have a look at our demo table).
BenchExec works only on Linux and needs a one-time setup of cgroups by the machine's administrator. The actual benchmarking can be done by any user and does not need root access.
BenchExec was originally developed for use with the software verification framework CPAchecker and is now developed as an independent project at the Software Systems Lab at the University of Passau.
- Documentation
- Demo of a result table
- Downloads
- Changelog
- BenchExec GitHub Repository, use this for reporting issues and asking questions
- BenchExec at PyPI
- Paper Benchmarking and Resource Measurement about BenchExec (supplementary webpage)
Maintainer: Philipp Wendler
Contributors:
- Dirk Beyer
- Montgomery Carter
- Andreas Donig
- Karlheinz Friedberger
- Peter Häring
- George Karpenkov
- Mike Kazantsev
- Thomas Lemberger
- Stefan Löwe
- Alexander von Rhein
- Alexander Schremmer
- Andreas Stahlbauer
- Thomas Stieglmaier
- and lots of more people who integrated tools into BenchExec
BenchExec was successfully used for benchmarking in all four instances of the International Competition on Software Verification with a wide variety of benchmarked tools and hundreds of thousands benchmark runs.
The developers of the following tools use BenchExec:
- CPAchecker, also for regression testing
- SMACK
If you would like to be listed here, contact us.