The Wayback Machine - https://web.archive.org/web/20200706020859/https://github.com/topics/benchmark
Skip to content
#

benchmark

Here are 2,141 public repositories matching this topic...

BenchmarkDotNet
simonech
simonech commented Jun 24, 2019

For each Job, it adds plots about density, cumulative mean, and so on. But two files are named BenchmarkDotNet.Artifacts/results/MyBench.Sleeps-Time50--density.png and BenchmarkDotNet.Artifacts/results/MyBench.Sleeps-Time50--facetDensity.png, with the -- instead of single. Like some iteration variable is empty (since later there are names with -Default-
![image](https://user-images.github

amichair
amichair commented May 4, 2019

I think the explanations/requirements surrounding the parameter (e.g. in multiple and update tests) could be clarified a bit, e.g. in updates-ii 'query' is highlighted as a symbol, but in iii 'queries' is highlighted as a symbol, which is confusing as to what the correct parameter name is. I think the former might be a formatting typo.

Also, it refers to it as a query parameter, whereas in mult

zou000
zou000 commented Mar 10, 2020

Describe the bug
We are using clang 8 with libc++ with libc++'s thread annotation enabled by -D_LIBCPP_ENABLE_THREAD_SAFETY_ANNOTATIONS globally. However, it conflicts with benchmark's mutex wrapper's thread annotation.

System
Which OS, compiler, and compiler version are you using:

  • OS: Linux
  • Compiler and version: clang 8 with libc++

To reproduce
Steps to reproduc

anderspapitto
anderspapitto commented Dec 15, 2018

I changed a benchmark to do twice as much work per iteration, and added a multiplier of 2 in the .throughput() to account for this. Time taken per iteration went up, but so did throughput. However criterion reported this as a regression, which is wrong/misleading.

When throughput is provided, "regression" and "improvement" labels should probably be based on throughput rather than time per ite

lorentey
lorentey commented Mar 1, 2017

There should be a more intuitive way to select the size range on which benchmarks are run.

The chart has an option to highlight the active range. We could make that highlight interactive, for example: let me drag the endpoints of the highlighted range to change it.

We should still display the exact numerical value of the current size range somewhere on the toolbar, but the current popup butt

gkossakowski
gkossakowski commented Sep 21, 2016

If you modify jmh-extras and run the with-FlightRecorderProfiler scripted test, the local modifications won't be picked up. The reason is that the scripted test doesn't set the version of extras so the default (non snapshot) version is used.

The workaround is:

diff --git a/plugin/src/sbt-test/sbt-jmh/with-FlightRecorderProfiler/build.sbt b/plugin/src/sbt-test/sbt-jmh/with-FlightRecor

Improve this page

Add a description, image, and links to the benchmark topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the benchmark topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.