Ansible
PS DSC
Downloads:
7,036
Downloads of v 1.18.0:
1,676
Last Update:
23 Oct 2023
Package Maintainer(s):
Software Author(s):
- David Peter
Tags:
command-line tool benchmark rust cli terminal foss- Software Specific:
- Software Site
- Software Source
- Software License
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
hyperfine
- 1
- 2
- 3
1.18.0 | Updated: 23 Oct 2023
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
7,036
Downloads of v 1.18.0:
1,676
Maintainer(s):
Software Author(s):
- David Peter
hyperfine 1.18.0
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by David Peter. The inclusion of David Peter trademark(s), if any, upon this webpage is solely to identify David Peter goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Deployment Method: Individual Install, Upgrade, & Uninstall
To install hyperfine, run the following command from the command line or from PowerShell:
>
To upgrade hyperfine, run the following command from the command line or from PowerShell:
>
To uninstall hyperfine, run the following command from the command line or from PowerShell:
>
Deployment Method:
NOTE
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download hyperfine --internalize --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade hyperfine -y --source="'INTERNAL REPO URL'" [other options]See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade hyperfine -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install hyperfine
win_chocolatey:
name: hyperfine
version: '1.18.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'hyperfine' do
action :install
source 'INTERNAL REPO URL'
version '1.18.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller hyperfine
{
Name = "hyperfine"
Version = "1.18.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'hyperfine':
ensure => '1.18.0',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
Package Approved
This package was approved as a trusted package on 30 Oct 2024.
Description
A command-line benchmarking tool.
Demo: Benchmarking fd and
find:
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).
- Cross-platform
Usage
Basic benchmark
To run a benchmark, you can simply call hyperfine <command>.... The argument(s) can be any
shell command. For example:
hyperfine 'sleep 0.3'
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:
hyperfine --min-runs 5 'sleep 0.2' 'sleep 3.2'
Warmup runs and preparation commands
If the program execution time is limited by disk I/O, the benchmarking results can be heavily
influenced by disk caches and whether they are cold or warm.
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:
hyperfine --warmup 3 'grep -R TODO *'
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
sync; echo 3 | sudo tee /proc/sys/vm/drop_caches
To use this specific command with Hyperfine, call sudo -v to temporarily gain sudo permissions
and then call:
hyperfine --prepare 'sync; echo 3 | sudo tee /proc/sys/vm/drop_caches' 'grep -R TODO *'
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:
hyperfine --prepare 'make clean' --parameter-scan num_threads 1 12 'make -j {num_threads}'
This also works with decimal numbers. The -D/--parameter-step-size option can be used
to control the step size:
hyperfine --parameter-scan delay 0.3 0.7 -D 0.2 'sleep {delay}'
This runs sleep 0.3, sleep 0.5 and sleep 0.7.
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:
| Command | Mean [s] | Min [s] | Max [s] | Relative |
|---|---|---|---|---|
find . -iregex '.*[0-9]\.jpg$' |
2.275 ± 0.046 | 2.243 | 2.397 | 9.79 ± 0.22 |
find . -iname '*[0-9].jpg' |
1.427 ± 0.026 | 1.405 | 1.468 | 6.14 ± 0.13 |
fd -HI '.*[0-9]\.jpg$' |
0.232 ± 0.002 | 0.230 | 0.236 | 1.00 |
The JSON output is useful if you want to analyze the benchmark results in more detail. See the
scripts/ folder for some examples.
Files
tools\chocolateyinstall.ps1
tools\x64\hyperfine.exe
md5: 7F3BD415368A884F0DDE5F523454B42A | sha1: 1DAED2DCE4A1B4E16A4AE2C57E31607ED24628E4 | sha256: E223294856559E0CE38FFC941B0420B562F18E51E780163C0B091FA15752E326 | sha512: D94543C8902777C647B33F9A5C3179E3E7DE095A9DDB8435D7449184B3895B85C43FC8135EE316467C0E384EE9BE6B1FFCEDB8B28060E4111FFDA8690D6E5205
tools\x86\hyperfine.exe
md5: 3C70DF56998F74FEDF99E74AAA93D7FE | sha1: 8E6C1B12C1C587F81DE3070DE441639E0E9B74E9 | sha256: 75CD63B84CD2265154D7C17174B5EB316BBD0C62B6C5370D51A00CBA8767FB61 | sha512: 626C5859AE6C3F02788C160B0AB884B5A8BD9705AEEC1CB8575CDB9269C51999AEBBD5235E0660C4E38E3FA051DDF36C1064C5B4588613D35DF0204FA3BACBB3
tools\autocompletions.ps1
using namespace System.Management.Automation
using namespace System.Management.Automation.Language
Register-ArgumentCompleter -Native -CommandName 'hyperfine' -ScriptBlock {
param($wordToComplete, $commandAst, $cursorPosition)
$commandElements = $commandAst.CommandElements
$command = @(
'hyperfine'
for ($i = 1; $i -lt $commandElements.Count; $i++) {
$element = $commandElements[$i]
if ($element -isnot [StringConstantExpressionAst] -or
$element.StringConstantType -ne [StringConstantType]::BareWord -or
$element.Value.StartsWith('-') -or
$element.Value -eq $wordToComplete) {
break
}
$element.Value
}) -join ';'
$completions = @(switch ($command) {
'hyperfine' {
[CompletionResult]::new('-w', 'w', [CompletionResultType]::ParameterName, 'Perform NUM warmup runs before the actual benchmark. This can be used to fill (disk) caches for I/O-heavy programs.')
[CompletionResult]::new('--warmup', 'warmup', [CompletionResultType]::ParameterName, 'Perform NUM warmup runs before the actual benchmark. This can be used to fill (disk) caches for I/O-heavy programs.')
[CompletionResult]::new('-m', 'm', [CompletionResultType]::ParameterName, 'Perform at least NUM runs for each command (default: 10).')
[CompletionResult]::new('--min-runs', 'min-runs', [CompletionResultType]::ParameterName, 'Perform at least NUM runs for each command (default: 10).')
[CompletionResult]::new('-M', 'M ', [CompletionResultType]::ParameterName, 'Perform at most NUM runs for each command. By default, there is no limit.')
[CompletionResult]::new('--max-runs', 'max-runs', [CompletionResultType]::ParameterName, 'Perform at most NUM runs for each command. By default, there is no limit.')
[CompletionResult]::new('-r', 'r', [CompletionResultType]::ParameterName, 'Perform exactly NUM runs for each command. If this option is not specified, hyperfine automatically determines the number of runs.')
[CompletionResult]::new('--runs', 'runs', [CompletionResultType]::ParameterName, 'Perform exactly NUM runs for each command. If this option is not specified, hyperfine automatically determines the number of runs.')
[CompletionResult]::new('-s', 's', [CompletionResultType]::ParameterName, 'Execute CMD before each set of timing runs. This is useful for compiling your software with the provided parameters, or to do any other work that should happen once before a series of benchmark runs, not every time as would happen with the --prepare option.')
[CompletionResult]::new('--setup', 'setup', [CompletionResultType]::ParameterName, 'Execute CMD before each set of timing runs. This is useful for compiling your software with the provided parameters, or to do any other work that should happen once before a series of benchmark runs, not every time as would happen with the --prepare option.')
[CompletionResult]::new('-p', 'p', [CompletionResultType]::ParameterName, 'Execute CMD before each timing run. This is useful for clearing disk caches, for example.
The --prepare option can be specified once for all commands or multiple times, once for each command. In the latter case, each preparation command will be run prior to the corresponding benchmark command.')
[CompletionResult]::new('--prepare', 'prepare', [CompletionResultType]::ParameterName, 'Execute CMD before each timing run. This is useful for clearing disk caches, for example.
The --prepare option can be specified once for all commands or multiple times, once for each command. In the latter case, each preparation command will be run prior to the corresponding benchmark command.')
[CompletionResult]::new('-c', 'c', [CompletionResultType]::ParameterName, 'Execute CMD after the completion of all benchmarking runs for each individual command to be benchmarked. This is useful if the commands to be benchmarked produce artifacts that need to be cleaned up.')
[CompletionResult]::new('--cleanup', 'cleanup', [CompletionResultType]::ParameterName, 'Execute CMD after the completion of all benchmarking runs for each individual command to be benchmarked. This is useful if the commands to be benchmarked produce artifacts that need to be cleaned up.')
[CompletionResult]::new('-P', 'P ', [CompletionResultType]::ParameterName, 'Perform benchmark runs for each value in the range MIN..MAX. Replaces the string ''{VAR}'' in each command by the current parameter value.
Example: hyperfine -P threads 1 8 ''make -j {threads}''
This performs benchmarks for ''make -j 1'', ''make -j 2'', …, ''make -j 8''.
To have the value increase following different patterns, use shell arithmetics.
Example: hyperfine -P size 0 3 ''sleep $((2**{size}))''
This performs benchmarks with power of 2 increases: ''sleep 1'', ''sleep 2'', ''sleep 4'', …
The exact syntax may vary depending on your shell and OS.')
[CompletionResult]::new('--parameter-scan', 'parameter-scan', [CompletionResultType]::ParameterName, 'Perform benchmark runs for each value in the range MIN..MAX. Replaces the string ''{VAR}'' in each command by the current parameter value.
Example: hyperfine -P threads 1 8 ''make -j {threads}''
This performs benchmarks for ''make -j 1'', ''make -j 2'', …, ''make -j 8''.
To have the value increase following different patterns, use shell arithmetics.
Example: hyperfine -P size 0 3 ''sleep $((2**{size}))''
This performs benchmarks with power of 2 increases: ''sleep 1'', ''sleep 2'', ''sleep 4'', …
The exact syntax may vary depending on your shell and OS.')
[CompletionResult]::new('-D', 'D ', [CompletionResultType]::ParameterName, 'This argument requires --parameter-scan to be specified as well. Traverse the range MIN..MAX in steps of DELTA.
Example: hyperfine -P delay 0.3 0.7 -D 0.2 ''sleep {delay}''
This performs benchmarks for ''sleep 0.3'', ''sleep 0.5'' and ''sleep 0.7''.')
[CompletionResult]::new('--parameter-step-size', 'parameter-step-size', [CompletionResultType]::ParameterName, 'This argument requires --parameter-scan to be specified as well. Traverse the range MIN..MAX in steps of DELTA.
Example: hyperfine -P delay 0.3 0.7 -D 0.2 ''sleep {delay}''
This performs benchmarks for ''sleep 0.3'', ''sleep 0.5'' and ''sleep 0.7''.')
[CompletionResult]::new('-L', 'L ', [CompletionResultType]::ParameterName, 'Perform benchmark runs for each value in the comma-separated list VALUES. Replaces the string ''{VAR}'' in each command by the current parameter value.
Example: hyperfine -L compiler gcc,clang ''{compiler} -O2 main.cpp''
This performs benchmarks for ''gcc -O2 main.cpp'' and ''clang -O2 main.cpp''.
The option can be specified multiple times to run benchmarks for all possible parameter combinations.
')
[CompletionResult]::new('--parameter-list', 'parameter-list', [CompletionResultType]::ParameterName, 'Perform benchmark runs for each value in the comma-separated list VALUES. Replaces the string ''{VAR}'' in each command by the current parameter value.
Example: hyperfine -L compiler gcc,clang ''{compiler} -O2 main.cpp''
This performs benchmarks for ''gcc -O2 main.cpp'' and ''clang -O2 main.cpp''.
The option can be specified multiple times to run benchmarks for all possible parameter combinations.
')
[CompletionResult]::new('-S', 'S ', [CompletionResultType]::ParameterName, 'Set the shell to use for executing benchmarked commands. This can be the name or the path to the shell executable, or a full command line like "bash --norc". It can also be set to "default" to explicitly select the default shell on this platform. Finally, this can also be set to "none" to disable the shell. In this case, commands will be executed directly. They can still have arguments, but more complex things like "sleep 0.1; sleep 0.2" are not possible without a shell.')
[CompletionResult]::new('--shell', 'shell', [CompletionResultType]::ParameterName, 'Set the shell to use for executing benchmarked commands. This can be the name or the path to the shell executable, or a full command line like "bash --norc". It can also be set to "default" to explicitly select the default shell on this platform. Finally, this can also be set to "none" to disable the shell. In this case, commands will be executed directly. They can still have arguments, but more complex things like "sleep 0.1; sleep 0.2" are not possible without a shell.')
[CompletionResult]::new('--style', 'style', [CompletionResultType]::ParameterName, 'Set output style type (default: auto). Set this to ''basic'' to disable output coloring and interactive elements. Set it to ''full'' to enable all effects even if no interactive terminal was detected. Set this to ''nocolor'' to keep the interactive output without any colors. Set this to ''color'' to keep the colors without any interactive output. Set this to ''none'' to disable all the output of the tool.')
[CompletionResult]::new('--sort', 'sort', [CompletionResultType]::ParameterName, 'Specify the sort order of the speed comparison summary and the exported tables for markup formats (Markdown, AsciiDoc, org-mode):
* ''auto'' (default): the speed comparison will be ordered by time and
the markup tables will be ordered by command (input order).
* ''command'': order benchmarks in the way they were specified
* ''mean-time'': order benchmarks by mean runtime
')
[CompletionResult]::new('-u', 'u', [CompletionResultType]::ParameterName, 'Set the time unit to be used. Possible values: microsecond, millisecond, second. If the option is not given, the time unit is determined automatically. This option affects the standard output as well as all export formats except for CSV and JSON.')
[CompletionResult]::new('--time-unit', 'time-unit', [CompletionResultType]::ParameterName, 'Set the time unit to be used. Possible values: microsecond, millisecond, second. If the option is not given, the time unit is determined automatically. This option affects the standard output as well as all export formats except for CSV and JSON.')
[CompletionResult]::new('--export-asciidoc', 'export-asciidoc', [CompletionResultType]::ParameterName, 'Export the timing summary statistics as an AsciiDoc table to the given FILE. The output time unit can be changed using the --time-unit option.')
[CompletionResult]::new('--export-csv', 'export-csv', [CompletionResultType]::ParameterName, 'Export the timing summary statistics as CSV to the given FILE. If you need the timing results for each individual run, use the JSON export format. The output time unit is always seconds.')
[CompletionResult]::new('--export-json', 'export-json', [CompletionResultType]::ParameterName, 'Export the timing summary statistics and timings of individual runs as JSON to the given FILE. The output time unit is always seconds')
[CompletionResult]::new('--export-markdown', 'export-markdown', [CompletionResultType]::ParameterName, 'Export the timing summary statistics as a Markdown table to the given FILE. The output time unit can be changed using the --time-unit option.')
[CompletionResult]::new('--export-orgmode', 'export-orgmode', [CompletionResultType]::ParameterName, 'Export the timing summary statistics as an Emacs org-mode table to the given FILE. The output time unit can be changed using the --time-unit option.')
[CompletionResult]::new('--output', 'output', [CompletionResultType]::ParameterName, 'Control where the output of the benchmark is redirected. Note that some programs like ''grep'' detect when standard output is /dev/null and apply certain optimizations. To avoid that, consider using ''--output=pipe''.
<WHERE> can be:
null: Redirect output to /dev/null (the default).
pipe: Feed the output through a pipe before discarding it.
inherit: Don''t redirect the output at all (same as ''--show-output'').
<FILE>: Write the output to the given file.')
[CompletionResult]::new('--input', 'input', [CompletionResultType]::ParameterName, 'Control where the input of the benchmark comes from.
<WHERE> can be:
null: Read from /dev/null (the default).
<FILE>: Read the input from the given file.')
[CompletionResult]::new('-n', 'n', [CompletionResultType]::ParameterName, 'Give a meaningful name to a command. This can be specified multiple times if several commands are benchmarked.')
[CompletionResult]::new('--command-name', 'command-name', [CompletionResultType]::ParameterName, 'Give a meaningful name to a command. This can be specified multiple times if several commands are benchmarked.')
[CompletionResult]::new('--min-benchmarking-time', 'min-benchmarking-time', [CompletionResultType]::ParameterName, 'Set the minimum time (in seconds) to run benchmarks. Note that the number of benchmark runs is additionally influenced by the `--min-runs`, `--max-runs`, and `--runs` option.')
[CompletionResult]::new('-N', 'N ', [CompletionResultType]::ParameterName, 'An alias for ''--shell=none''.')
[CompletionResult]::new('-i', 'i', [CompletionResultType]::ParameterName, 'Ignore non-zero exit codes of the benchmarked programs.')
[CompletionResult]::new('--ignore-failure', 'ignore-failure', [CompletionResultType]::ParameterName, 'Ignore non-zero exit codes of the benchmarked programs.')
[CompletionResult]::new('--show-output', 'show-output', [CompletionResultType]::ParameterName, 'Print the stdout and stderr of the benchmark instead of suppressing it. This will increase the time it takes for benchmarks to run, so it should only be used for debugging purposes or when trying to benchmark output speed.')
[CompletionResult]::new('--debug-mode', 'debug-mode', [CompletionResultType]::ParameterName, 'Enable debug mode which does not actually run commands, but returns fake times when the command is ''sleep <time>''.')
[CompletionResult]::new('-h', 'h', [CompletionResultType]::ParameterName, 'Print help')
[CompletionResult]::new('--help', 'help', [CompletionResultType]::ParameterName, 'Print help')
[CompletionResult]::new('-V', 'V ', [CompletionResultType]::ParameterName, 'Print version')
[CompletionResult]::new('--version', 'version', [CompletionResultType]::ParameterName, 'Print version')
break
}
})
$completions.Where{ $_.CompletionText -like "$wordToComplete*" } |
Sort-Object -Property ListItemText
}
legal\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
Package can be verified like this:
1. Go to https://github.com/sharkdp/hyperfine, enter to releases and download from there.
x86_64: https://github.com/sharkdp/hyperfine/releases/download/v1.18.0/hyperfine-v1.18.0-i686-pc-windows-msvc.zip
to download the zip files. You may wish to rename one of the files.
2. You can use one of the following methods to obtain the SHA512 checksum:
- Use powershell function 'Get-FileHash'
- Use Chocolatey utility 'checksum.exe'
checksum64: f08d3c65d62786c56f9450a68957c292e9c041c9e43c8c218013c516932ca08624baeec1be846e1e7ce2c74a96223c278e22337f52fba03c27d47b9bfe63af0b
File 'LICENSE.txt' obtained from:
https://github.com/sharkdp/hyperfine/blob/v1.18.0/LICENSE-MIT
and
https://github.com/sharkdp/hyperfine/blob/v1.18.0/LICENSE-APACHE
legal\LICENSE.txt
MIT License
Copyright (c) 2018-2020 The hyperfine developers
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
-------------------------------------------------------------------------------
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Virus Scan Results
Log in or click on link to see number of positives.
- hyperfine.1.18.0.nupkg (3a526eb98296) - ## / 66
- hyperfine.exe (e22329485655) - ## / 72
- hyperfine.exe (75cd63b84cd2) - ## / 72
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Version History
| Add to Builder | Version | Downloads | Last Updated | Status |
|---|---|---|---|---|
| hyperfine 1.18.0 | 1676 | Monday, October 23, 2023 | Approved | |
| hyperfine 1.17.0 | 123 | Wednesday, October 11, 2023 | Approved | |
| hyperfine 1.16.1 | 363 | Wednesday, August 2, 2023 | Approved | |
| hyperfine 1.16.0 | 645 | Monday, March 27, 2023 | Approved | |
| hyperfine 1.15.0 | 525 | Saturday, October 8, 2022 | Approved | |
| hyperfine 1.14.0 | 1175 | Thursday, May 19, 2022 | Approved | |
| hyperfine 1.13.0 | 830 | Tuesday, March 8, 2022 | Approved | |
| hyperfine 1.12.0 | 350 | Sunday, October 17, 2021 | Approved | |
| hyperfine 1.11.0 | 348 | Monday, October 19, 2020 | Approved | |
| hyperfine 1.10.0 | 136 | Monday, October 19, 2020 | Approved | |
| hyperfine 1.9.0 | 138 | Monday, October 19, 2020 | Approved | |
| hyperfine 1.8.0 | 117 | Monday, October 19, 2020 | Approved | |
| hyperfine 1.7.0 | 133 | Monday, October 19, 2020 | Approved | |
| hyperfine 1.6.0 | 119 | Friday, October 9, 2020 | Approved | |
| hyperfine 1.5.0 | 123 | Friday, October 9, 2020 | Approved | |
| hyperfine 1.4.0 | 113 | Friday, October 9, 2020 | Approved | |
| hyperfine 1.3.0 | 122 | Friday, October 2, 2020 | Approved |
Copyright
Copyright © 2018-2023 David Peter & The hyperfine developers
Dependencies
-
- chocolatey-core.extension (≥ 1.3.5.1)
- vcredist140 (≥ 14.20.27508.1)
Discussion for the hyperfine Package
Ground Rules:
- This discussion is only about hyperfine and the hyperfine package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or hyperfine, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.