-
Updated
Jul 29, 2021 - Go
benchmarking
Here are 941 public repositories matching this topic...
-
Updated
Sep 11, 2021 - Python
-
Updated
Jul 24, 2021 - Jupyter Notebook
-
Updated
Sep 10, 2021 - C
-
Updated
Sep 10, 2021 - Go
-
Updated
Jul 11, 2021 - Go
-
Updated
Sep 11, 2021 - C
-
Updated
Apr 7, 2021 - Erlang
-
Updated
Apr 2, 2020
-
Updated
Sep 8, 2021 - PHP
-
Updated
Sep 7, 2021 - PHP
-
Updated
Jun 23, 2021 - JavaScript
-
Updated
Sep 8, 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
Sep 10, 2021 - Swift
-
Updated
Sep 9, 2021 - Python
-
Updated
Aug 24, 2021 - Go
-
Updated
May 22, 2021 - Go
I noticed it is quite tricky at the moment to generate a benchmark with an unbalanced number of examples for each step.
It would be nice to have an option in ni_scenario, nc_scenario and similar to set the number of examples for each step.
-
Updated
Nov 28, 2018 - JavaScript
-
Updated
May 18, 2021 - C
-
Updated
Sep 4, 2021 - Python
-
Updated
Feb 28, 2021 - Go
-
Updated
Mar 4, 2021 - Clojure
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
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: