Features

• Add a new --reference <cmd> option to specify a reference command for the relative speed comparison, see #579, #577 and #744 (@JanEricNitschke)
• Add --conclude argument (analog to --prepare), see #565 and #719 as well as the docs here (@jackoconnordev)
• Allow --output=… to appear once for each command, enabling use cases like hyperfine --output=null my-cmd --output=./file.log my-cmd, see #529 and #775 (@sharkdp)
• The environment variable $HYPERFINE_ITERATION will now contain the current iteration number for each benchmarked command, see #775 (@sharkdp)
• Add iteration information to failure error message, see #771 and #772 (@sharkdp)
• Python scripts:
  • legend modification parameters and output DPI, see #758 (@Spreadcat)
  • Nicer whiskers plot, see #727 (@serpent7776)

Bugfixes

• ETA not clearly visible on terminals with a block cursor, see #698 and #699 (@overclockworked64)
• Fix zsh completions, see #717 (@xzfc)

Other

• Build binaries for aarch64-apple-darwin, see #728 (@Phault)
• Various cleanups (@hamirmahal, @one230six)

Features

• Add support for microseconds via --time-unit microsecond, see #684 (@sharkdp)

Bugfixes

• Proper argument quoting on Windows CMD, see #296 and #678 (@PedroWitzel)

Features

• Add new --sort option to control the order in the rel. speed comparison and in markup export formats, see #601, #614, #655 (@sharkdp)
• Parameters which are unused in the command line are now displayed in parentheses, see #600 and #644 (@sharkdp).
• Added --log-count option for histogram plots, see scripts/plot_histogram.py (@sharkdp)

Changes

• Updated hyperfine to use windows-sys instead of the unmaintained winapi, see #624, #639, #636, #641 (@clemenswasser)
• Silenced deprecation warning in Python scripts, see #633 (@nicovank)
• Major update of the man page, see 0ce6578, #647 (@sharkdp)

Bugfixes

• Do not export intermediate results to stdout when using - as a file name, see #640 and #643 (@sharkdp)
• Markup exporting does not fail if benchmark results are zero, see #642 (@sharkdp)

Bugfixes

• Fix line-wrapping of --help text (@sharkdp)
• Fix --input=null (@sharkdp)

Features

• Added new --input option, see #541 and #563 (@snease)
• Added possibility to specify - as the filename in the --export-* options, see #615 and #623 (@humblepenguinn)

Changes

• Improve hints for outlier warnings if --warmup or --prepare are in use already, see #570 (@sharkdp)

Bugfixes

• Fix uncolored output on Windows if TERM is not set, see #583 (@nabijaczleweli)
• On Windows, only run cmd.exe with the /C option. Use -c for all other shells, see #568 and #582 (@FilipAndersson245)

Other

• Thanks to @berombau for working on dependency upgrades, see #584
• Fixed installationm on Windows, see #595 and #596 (@AntoniosBarotsis)

Features

• Disable colorized output in case of TERM=dumb or NO_COLOR=1, see #542 and #555 (@nabijaczleweli)
• Add new (experimental) --min-benchmarking-time <secs> option, see #527 (@sharkdp)

Bugfixes

• Fix user and kernel times on Windows, see #368 and #538 (@clemenswasser)

Other

• Improve --help texts of --export-* options, see #506 and #522 (@Engineer-of-Efficiency)

• Add a new --output={null,pipe,inherit,<FILE>} option to control
  where the output of the benchmarked program is redirected (if at all),
  see #377 and #509 (@tavianator, originally suggested by @BurntSushi)
• Add Emacs org-mode as a new export format, see #491 (@ppaulweber)
• Relax glibc requirements, see #508 and #512 (@sharkdp)

Features

• Added a new --shell=none/-N option to disable the intermediate
  shell for executing the benchmarked commands. Hyperfine normally
  measures and subtracts the shell spawning time, but the intermediate
  shell always introduces a certain level of measurement noise. Using
  --shell=none/-N allows users to benchmark very fast commands
  (with a runtime on the order of a few milliseconds). See #336, #429,
  and #487 (@cipriancraciun and @sharkdp)
• Added --setup/-s option that can be used to run make all or
  similar. It runs once per set of tests, like --cleanup/-c (@avar)
• Added new plot_progression.py script to debug background
  interference effects.

Changes

• Breaking change: the -s short option for --style is now used for
  the new --setup option.
• The environment offset randomization is now also available on Windows,
  see #484

Other

• Improved documentation and test coverage, cleaned up code base for
  future improvements.

Features

• --command-name can now take parameter names from --parameter-* options, see #351 and #391 (@silathdiir)
• Exit codes (or signals) are now printed in cases of command failures, see #342 (@KaindlJulian)
• Exit codes are now part of the JSON output, see #371 (@JordiChauzi)
• Colorized output should now be enabled on Windows by default, see #427

Changes

• When --export-* commands are used, result files are created before benchmark execution
  to fail early in case of, e.g., wrong permissions. See #306 (@s1ck).
• When --export-* options are used, result files are written after each individual
  benchmark command instead of writing after all benchmarks have finished. See #306 (@s1ck).
• Reduce number of shell startup time measurements from 200 to 50, generally speeding up benchmarks. See #378
• User and system time are now in consistent time units, see #408 and #409 (@film42)

Features

• The -L/--parameter-list option can now be specified multiple times to
  evaluate all possible combinations of the listed parameters:

  hyperfine -L number 1,2 -L letter a,b,c \
      "echo {number}{letter}" \
      "printf '%s\n' {number}{letter}"
  # runs 12 benchmarks: 2 commands (echo and printf) times 6 combinations of
  # the "letter" and "number" parameters

  See: #253, #318 (@wchargin)

• Add CLI option to identify a command with a custom name, see #326 (@scampi)

Changes

• When parameters are used with --parameter-list or --parameter-scan, the JSON export format
  now contains a dictionary parameters instead of a single key parameter. See #253, #318.
• The plot_parametrized.py script now infers the parameter name, and its --parameter-name
  argument has been deprecated. See #253, #318.

Bugfixes

• Fix a bug in the outlier detection which would only detect "slow outliers" but not the fast
  ones (runs that are much faster than the rest of the benchmarking runs), see #329
• Better error messages for very fast commands that would lead to inf/nan results in the relative
  speed comparison, see #319
• Show error message if --warmup or --*runs arguments can not be parsed, see #337
• Keep output colorized when the output is not interactive and --style=full or --style=color is used.