-
Updated
Feb 25, 2021 - Go
benchmarking
Here are 857 public repositories matching this topic...
-
Updated
Mar 12, 2021 - Python
-
Updated
Mar 13, 2021 - Jupyter Notebook
-
Updated
Mar 12, 2021 - C
-
Updated
Feb 26, 2021 - Go
-
Updated
Mar 13, 2021 - C++
What RedrawInterval is being constant is a problem. Support the --redraw-interval option to make it configurable.
-
Updated
Nov 16, 2020 - Erlang
-
Updated
Apr 2, 2020
-
Updated
Mar 11, 2021 - PHP
-
Updated
Mar 13, 2021 - PHP
-
Updated
Sep 11, 2020 - JavaScript
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
Mar 12, 2021 - C
-
Updated
Feb 15, 2021
-
Updated
Feb 26, 2021 - Jupyter Notebook
-
Updated
Mar 12, 2021 - Python
-
Updated
Feb 5, 2021 - Swift
-
Updated
Mar 13, 2021 - Python
-
Updated
Feb 25, 2021 - Go
-
Updated
Feb 22, 2021 - Go
-
Updated
Nov 28, 2018 - JavaScript
-
Updated
Feb 19, 2021 - C
-
Updated
Mar 4, 2021 - Clojure
-
Updated
Feb 28, 2021 - Go
There seem to be some vulnerabilities in our code that might fail easily. I suggest adding more unit tests for the following:
- Custom agents (there's only VPG and PPO on CartPole-v0 as of now. We should preferably add more to cover discrete-offpolicy, continuous-offpolicy and continuous-onpolicy)
- Evaluation for the Bandits and Classical agents
- Testing of convergence of agents as proposed i
-
Updated
Mar 9, 2021 - Python
-
Updated
Jan 28, 2021 - Python
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: