Files
hyperfine/README.md
T

139 lines
4.6 KiB
Markdown
Raw Normal View History

2018-01-13 20:27:24 +01:00
# hyperfine
2018-01-18 19:19:13 +01:00
[![Build Status](https://travis-ci.org/sharkdp/hyperfine.svg?branch=master)](https://travis-ci.org/sharkdp/hyperfine)
2018-02-13 21:16:45 +01:00
[![Build status](https://ci.appveyor.com/api/projects/status/pdqq5frgkcj0smrs?svg=true)](https://ci.appveyor.com/project/sharkdp/hyperfine)
2018-01-18 19:19:13 +01:00
[![Version info](https://img.shields.io/crates/v/hyperfine.svg)](https://crates.io/crates/hyperfine)
2018-10-19 21:35:21 +02:00
[中文](https://github.com/chinanf-boy/hyperfine-zh)
2018-01-13 20:27:24 +01:00
2018-01-14 22:26:39 +01:00
A command-line benchmarking tool (*inspired by [bench](https://github.com/Gabriel439/bench)*).
2018-01-13 20:27:24 +01:00
2018-01-18 18:13:12 +01:00
**Demo**: Benchmarking [`fd`](https://github.com/sharkdp/fd) and
[`find`](https://www.gnu.org/software/findutils/):
2018-01-14 22:19:52 +01:00
2018-01-14 22:12:02 +01:00
![hyperfine](https://i.imgur.com/5OqrGWe.gif)
2018-01-13 21:31:51 +01:00
2018-01-13 20:27:24 +01:00
## Features
2018-01-20 14:22:26 +01:00
* Statistical analysis across multiple runs.
* Support for arbitrary shell commands.
* Constant feedback about the benchmark progress and current estimates.
* Warmup runs can be executed before the actual benchmark.
* Cache-clearing commands can be set up before each timing run.
2018-01-30 22:31:31 +01:00
* Statistical outlier detection.
* Export results to various formats: CSV, JSON, Markdown.
* Parameterized benchmarks.
2018-02-13 21:17:27 +01:00
* Cross-platform
2018-01-13 21:07:28 +01:00
2018-01-16 22:03:50 +01:00
## Usage
### Basic benchmark
2018-01-18 18:13:12 +01:00
To run a benchmark, you can simply call `hyperfine <command>...`. The argument(s) can be any
shell command. For example:
2018-01-16 22:03:50 +01:00
``` bash
2018-01-24 08:32:11 +01:00
hyperfine 'sleep 0.3'
2018-01-16 22:03:50 +01:00
```
2018-01-18 18:13:12 +01:00
Hyperfine will automatically determine the number of runs to perform for each command. By default,
it will perform *at least* 10 benchmarking runs. To change this, you can use the `-m`/`--min-runs`
option:
2018-01-16 22:03:50 +01:00
``` bash
2018-01-24 08:32:11 +01:00
hyperfine --min-runs 5 'sleep 0.2' 'sleep 3.2'
2018-01-16 22:03:50 +01:00
```
### I/O-heavy programs
2018-01-18 18:13:12 +01:00
If the program execution time is limited by disk I/O, the benchmarking results can be heavily
2018-01-30 22:33:00 +01:00
influenced by disk caches and whether they are cold or warm.
2018-01-16 22:03:50 +01:00
2018-01-18 18:13:12 +01:00
If you want to run the benchmark on a warm cache, you can use the `-w`/`--warmup` option to perform
a certain number of program executions before the actual benchmark:
2018-01-16 22:03:50 +01:00
``` bash
2018-01-24 08:32:11 +01:00
hyperfine --warmup 3 'grep -R TODO *'
2018-01-16 22:03:50 +01:00
```
2018-01-18 18:13:12 +01:00
Conversely, if you want to run the benchmark for a cold cache, you can use the `-p`/`--prepare`
option to run a special command before *each* timing run. For example, to clear harddisk caches
on Linux, you can run
2018-01-16 22:03:50 +01:00
``` bash
sync; echo 3 | sudo tee /proc/sys/vm/drop_caches
```
2018-01-22 22:21:48 +00:00
To use this specific command with Hyperfine, call `sudo -v` to temporarily gain sudo permissions
2018-01-18 18:13:12 +01:00
and then call:
2018-01-16 22:03:50 +01:00
``` bash
2018-01-18 18:13:12 +01:00
hyperfine --prepare 'sync; echo 3 | sudo tee /proc/sys/vm/drop_caches' 'grep -R TODO *'
2018-01-16 22:03:50 +01:00
```
### Parameterized benchmarks
If you want to run a benchmark where only a single parameter is varied (say, the number of
threads), you can use the `-P`/`--parameter-scan` option and call:
``` bash
hyperfine --prepare 'make clean' --parameter-scan num_threads 1 12 'make -j {num_threads}'
```
### Export results
Hyperfine has multiple options for exporting benchmark results: CSV, JSON, Markdown (see `--help`
text for details). To export results to Markdown, for example, you can use the `--export-markdown`
option that will create tables like this:
2018-03-24 21:13:51 +01:00
| Command | Mean [ms] | Min…Max [ms] |
|:---|---:|---:|
| `find . -iregex '.*[0-9]\.jpg$'` | 506.0 ± 8.1 | 495.4…518.6 |
| `find . -iname '*[0-9].jpg'` | 304.9 ± 3.1 | 299.8…309.3 |
| `fd -HI '.*[0-9]\.jpg$'` | 66.2 ± 5.8 | 62.5…86.3 |
2018-12-12 20:37:51 +01:00
The JSON output is useful if you want to analyze the benchmark results in more detail. See the
[`scripts/`](https://github.com/sharkdp/hyperfine/tree/master/scripts) folder for some examples.
2018-01-13 21:07:28 +01:00
## Installation
2018-06-10 15:53:21 +02:00
### On macOS
Hyperfine can be installed via [Homebrew](https://brew.sh):
```
brew install hyperfine
```
2018-03-24 22:06:03 +01:00
### On Ubuntu
2018-01-20 14:22:26 +01:00
Download the appropriate `.deb` package from the [Release page](https://github.com/sharkdp/hyperfine/releases)
and install it via `dpkg`:
```
2018-12-12 23:41:30 +01:00
wget https://github.com/sharkdp/hyperfine/releases/download/v1.5.0/hyperfine_1.5.0_amd64.deb
sudo dpkg -i hyperfine_1.5.0_amd64.deb
2018-01-20 14:22:26 +01:00
```
2018-03-24 22:06:03 +01:00
### On Arch Linux
On Arch Linux, hyperfine can be installed [from the AUR](https://aur.archlinux.org/packages/hyperfine):
```
yaourt -S hyperfine
```
### On Void Linux
2018-01-30 18:55:26 -05:00
Hyperfine can be installed via xbps
```
xbps-install -S hyperfine
```
2018-01-20 14:22:26 +01:00
2018-03-24 22:06:03 +01:00
### With cargo (Linux, macOS, Windows)
Hyperfine can be installed via [cargo](https://doc.rust-lang.org/cargo/):
```
cargo install hyperfine
```
2018-12-28 20:33:31 +01:00
Make sure that you use Rust 1.30 or higher.
2018-07-18 18:11:05 +02:00
2018-09-28 22:02:24 +02:00
### From binaries (Linux, macOS, Windows)
2018-03-24 22:06:03 +01:00
Download the corresponding archive from the [Release page](https://github.com/sharkdp/hyperfine/releases).
2018-01-13 20:27:24 +01:00
## Origin of the name
The name *hyperfine* was chosen in reference to the hyperfine levels of caesium 133 which play a crucial role in the
2018-09-04 19:44:59 +10:00
[definition of our base unit of time](https://en.wikipedia.org/wiki/Second#History_of_definition)
2018-01-13 20:27:24 +01:00
— the second.