-
Updated
Sep 23, 2021 - Go
benchmarking
Here are 962 public repositories matching this topic...
-
Updated
Oct 27, 2021 - Python
-
Updated
Oct 24, 2021 - C
-
Updated
Oct 26, 2021 - Jupyter Notebook
-
Updated
Sep 16, 2021 - Go
-
Updated
Oct 23, 2021 - C
-
Updated
Jul 11, 2021 - Go
-
Updated
Apr 7, 2021 - Erlang
-
Updated
Oct 28, 2021 - Python
-
Updated
Apr 2, 2020
-
Updated
Oct 26, 2021 - PHP
-
Updated
Oct 26, 2021 - PHP
-
Updated
Jun 23, 2021 - JavaScript
-
Updated
Oct 26, 2021 - C
For different use cases, like bencheeorg/benchee_html#10 it'd be great to have statistics about statistics - what I'd call "meta statistics" - although there's probably some better real statistics name for this :)
What should be in there (that I know of so far):
- job size (how many jobs are in there)
- minimum of run times over all jobs
- maximum of run times over all jobs
This should be
-
Updated
Feb 15, 2021
-
Updated
Aug 26, 2021 - Jupyter Notebook
-
Updated
Jun 14, 2021 - Python
-
Updated
Oct 8, 2021 - Go
-
Updated
Oct 5, 2021 - Swift
-
Updated
Oct 27, 2021 - Python
-
Updated
Sep 17, 2021 - Go
We can wrap some import in a try ... catch statement so the user is not necessarily forced to install all the libraries, especially for the ones needed only by a specific strategy/logger.
e.g. quadprog, wandb, ...
-
Updated
Nov 28, 2018 - JavaScript
-
Updated
May 18, 2021 - C
-
Updated
Oct 19, 2021 - Python
-
Updated
Oct 12, 2021 - Python
-
Updated
Feb 28, 2021 - Go
-
Updated
Mar 4, 2021 - Clojure
Improve this page
Add a description, image, and links to the benchmarking topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the benchmarking topic, visit your repo's landing page and select "manage topics."
The original issue was reported in dotnet/performance#1701: