-
-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: save data directories for each run (run index as format specifier in the command) #683
Comments
Hacky patch to expose the run index as an environment variable
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
I have a benchmark use-case where I want to save extra data files for each run, for a more detailed analysis later.
I want to benchmark the number of garbage collection events in a program profile.
My run-tool can easily take the parameter I'm scanning as one argument and the directory as another.
But it is a little convoluted to do today.
Attempts
One attempt is to forgo
--runs
and use a--parameter-scan
for the runsWorking solution as a command executor. Though the time benchmark breaks as we set runs to 1.
Else it does both the default number of runs, and the parameter-list for runs.
Using two parameter-lists instead works:
This is okay, as I do not care about warmups today, but ideally a warmup should be used.
Then a two-dimensional parameter list could be
--parameter-list run WARMUP{1,2} $(seq 5)
or something.One can also hack the code to save the index
For the reference: I also hacked in the index into the run function,
and the run can be taken from the environment.
If someone wants a stricter API.
And my use case then looks like this, the environment variable is expanded in the run-shell.
The text was updated successfully, but these errors were encountered: