-
Updated
Apr 8, 2021 - Python
benchmark
Here are 2,575 public repositories matching this topic...
-
Updated
Apr 7, 2021
The original issue was reported in dotnet/performance#1701:
// Benchmark Process Environment Information:
// Runtime=.NET 6.0.0 (6.0.21.11801), X64 RyuJIT
// GC=Concurrent Workstation
// Job: Job-AQTFSE(PowerPlanMode=00000000-0000-0000-0000-000000000000, IterationTime=250.0000 ms, MaxIterationCount=20, MinIterationCount=15, WarmupCount=1)
OverheadJitting
-
Updated
Apr 11, 2021 - Java
-
Updated
Apr 11, 2021 - PHP
In #466 a description about how to "disable" CPU performance scaling on Linux was added. It works by setting the cpufreq governor to performance (which is arguably not the only way to stabilize CPU frequency) and, later after the benchmark is done, setting that to powersave.
I personally think it's more appropriate to memorize what the previous governor was by a simple shell variable, and l
-
Updated
Jul 20, 2020
- I have marked all applicable categories:
- exception-raising bug
- RL algorithm bug
- documentation request (i.e. "X is missing from the documentation.")
- new feature request
- I have visited the [source website], and in particular read the [known issues]
- I have searched through the [issue tracker] and [issue categories] for duplicates
- [ ]
-
Updated
Apr 6, 2021 - Python
-
Updated
Apr 7, 2021 - Erlang
-
Updated
Mar 22, 2021
-
Updated
Nov 6, 2020 - Python
-
Updated
Apr 10, 2021 - Rust
-
Updated
Feb 24, 2021 - Go
-
Updated
Apr 9, 2021 - PHP
-
Updated
Sep 11, 2020 - JavaScript
-
Updated
Dec 19, 2018 - Swift
-
Updated
Nov 30, 2017 - Objective-C
-
Updated
Apr 8, 2021 - Python
-
Updated
Feb 15, 2021
-
Updated
Jun 11, 2018 - C
-
Updated
Mar 5, 2021 - Python
Improve this page
Add a description, image, and links to the benchmark topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the benchmark topic, visit your repo's landing page and select "manage topics."


I would like to parameterize the command name based on the parameters from the parameter list
Currently the
--command-nameonly seem to take into account the first one in the list it would be nice if we could parametrerize the--command-namewith the<VAR>as we do in the actual commandHere is a concrete example I'm running