-
-
Notifications
You must be signed in to change notification settings - Fork 376
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
Allow several --parameter-list flags to set #273
Comments
#253 is what I want to have, actually, it does not interfere 😄 I see that you still not sure about syntax and flags for it, but semantically that's exactly I want to achieve - a way to create different variables and assign to them different values, so I could expand it while benchmarking. For now, I made a workaround as an array of commands to run in Bash script: SCRIPTS=(
"${NPM_INSTALL} && ${NPM_BUILD}"
"${NPM_INSTALL} --prefer-offline && ${NPM_BUILD}"
"${NPM_INSTALL} --prefer-online && ${NPM_BUILD}"
"${YARN_INSTALL} && ${YARN_BUILD}"
"${PNPM_INSTALL} && ${PNPM_BUILD}"
"${PNPM_INSTALL} --prefer-offline && ${PNPM_BUILD}"
)
hyperfine \
--prepare "${CLEAN_ARTIFACTS} && ${CLEAN_CACHE}" \
--export-json cold_cache_without_node_modules.json \
"${SCRIPTS[@]}" |
closing this in favor of #253 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Right now, we can use
--parameter-list
and that's great. I like the idea of parametrised benchmarks. Though, sometimes, you need to specify several parameter lists with different values.Expected Behaviour
When calling hyperfine:
I expect to have a possibility to parametrise different clients, that expect different flags. Surely, I can do it manually by duplicating commands for each flag, but why when you have such great flag.
Current Behaviour
When calling the command like above, I'm getting:
Notes
I had a look into your code and seems like you does not support
--parameter-list
flag as collection, but as single possible value.Is there any way to implement such kind of behaviour?
The text was updated successfully, but these errors were encountered: