An open API service providing package, version and dependency metadata of many open source software ecosystems and registries.

Top 9.9% on proxy.golang.org

proxy.golang.org : github.com/j178/benchdiff

Benchstat computes and compares statistics about benchmarks. Usage: Each input file should contain the concatenated output of a number of runs of “go test -bench.” For each different benchmark listed in an input file, benchstat computes the mean, minimum, and maximum run time, after removing outliers using the interquartile range rule. If invoked on a single input file, benchstat prints the per-benchmark statistics for that file. If invoked on a pair of input files, benchstat adds to the output a column showing the statistics from the second file and a column showing the percent change in mean from the first to the second file. Next to the percent change, benchstat shows the p-value and sample sizes from a test of the two distributions of benchmark times. Small p-values indicate that the two distributions are significantly different. If the test indicates that there was no significant change between the two benchmarks (defined as p > 0.05), benchstat displays a single ~ instead of the percent change. The -delta-test option controls which significance test is applied: utest (Mann-Whitney U-test), ttest (two-sample Welch t-test), or none. The default is the U-test, sometimes also referred to as the Wilcoxon rank sum test. If invoked on more than two input files, benchstat prints the per-benchmark statistics for all the files, showing one column of statistics for each file, with no column for percent change or statistical significance. The -html option causes benchstat to print the results as an HTML table. The -sort option specifies an order in which to list the results: none (input order), delta (percent improvement), or name (benchmark name). A leading “-” prefix, as in “-delta”, reverses the order. Suppose we collect results from running a set of benchmarks twenty times before a particular change: And the same benchmarks twenty times after: The file old.txt contains: The file new.txt contains: The order of the lines in the file does not matter, except that the output lists benchmarks in order of appearance. If run with just one input file, benchstat summarizes that file: If run with two input files, benchstat summarizes and compares: Note that the JSONEncode result is reported as statistically insignificant instead of a -0.93% delta.

Registry - Source - Documentation - JSON
purl: pkg:golang/github.com/j178/benchdiff
License: BSD-3-Clause
Latest release: over 2 years ago
First release: over 2 years ago
Namespace: github.com/j178
Stars: 2 on GitHub
Forks: 0 on GitHub
See more repository details: repos.ecosyste.ms
Last synced: 22 days ago

    Loading...
    Readme
    Loading...