-
Updated
Jul 29, 2021 - Go
benchmarking
Here are 944 public repositories matching this topic...
-
Updated
Sep 15, 2021 - Python
-
Updated
Sep 12, 2021 - Jupyter Notebook
-
Updated
Sep 14, 2021 - C
-
Updated
Sep 16, 2021 - Go
-
Updated
Jul 11, 2021 - Go
-
Updated
Sep 18, 2021 - C
-
Updated
Apr 7, 2021 - Erlang
-
Updated
Apr 2, 2020
-
Updated
Sep 11, 2021 - PHP
-
Updated
Sep 17, 2021 - PHP
-
Updated
Jun 23, 2021 - JavaScript
-
Updated
Sep 14, 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 17, 2021 - Python
-
Updated
Aug 24, 2021 - Go
-
Updated
Sep 17, 2021 - Go
For the moment, the nc_benchmark generator function allows for a nc_first_task option, which is good for pre-training in the class-incremental learning scenario. However, the same kind of option is not available if one wants to pretrain in the task-incremental scenario. It would be nice to have an option that could be used together with task_labels=True and allows for pretraining on multiple tasks
-
Updated
Nov 28, 2018 - JavaScript
-
Updated
May 18, 2021 - C
-
Updated
Sep 16, 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: