| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
v1.15.0
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)
|
|
|
|
A command-line benchmarking tool.
Features:
-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.
-Statistical outlier detection to detect interference from other programs and
caching effects.
-Export results to various formats: CSV, JSON, Markdown, AsciiDoc.
-Parameterized benchmarks (e.g. vary the number of threads).
|
