-
Updated
Jul 29, 2021 - Go
benchmarking
Here are 922 public repositories matching this topic...
-
Updated
Jul 31, 2021 - Python
-
Updated
Jul 24, 2021 - Jupyter Notebook
-
Updated
Jul 25, 2021 - C
-
Updated
Jul 27, 2021 - Go
-
Updated
Jul 11, 2021 - Go
-
Updated
Jul 30, 2021 - C
-
Updated
Apr 7, 2021 - Erlang
-
Updated
Apr 2, 2020
-
Updated
Jul 31, 2021 - PHP
-
Updated
Jul 30, 2021 - PHP
-
Updated
Jun 23, 2021 - JavaScript
-
Updated
Jul 27, 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
Jul 30, 2021 - Jupyter Notebook
-
Updated
Jun 14, 2021 - Python
-
Updated
Feb 5, 2021 - Swift
-
Updated
Jul 30, 2021 - Python
-
Updated
Jul 20, 2021 - Go
-
Updated
May 22, 2021 - Go
-
Updated
Nov 28, 2018 - JavaScript
By exploiting the callbacks before_forward and similar it is very easy to log samples of the training dataset, number of patterns, features statistics and other metrics.
We can discuss in here what it could be useful to add.
-
Updated
May 18, 2021 - C
-
Updated
Feb 28, 2021 - Go
-
Updated
Jul 23, 2021 - Python
-
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: