Skip to content
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

Define a Common Command Line Interface to run any container #18

Open
rouvoy opened this issue Jan 22, 2016 · 2 comments
Open

Define a Common Command Line Interface to run any container #18

rouvoy opened this issue Jan 22, 2016 · 2 comments

Comments

@rouvoy
Copy link
Member

rouvoy commented Jan 22, 2016

Instead of dealing with specific command line interfaces (CLIs), it would be relevant to define a standard CLI to run benchmark containers.

Such a CLI should include:

  • Introspection commands to list the benchmarks, workloads and other parameters (e.g., threads) available and their value.
  • Execution commands to run the benchmark with a specific workload and set of parameters.

This CLI should be exposed by all the available containers.

@MensObscura
Copy link
Collaborator

Hello,

Must i copy the run of NPB, and adapt it to all done benchmarks?
Or make a new run ?

Currently the run of NPB contains :

  *a generic help.
  *The help of each benchmark.
  *And if the first param is not -help', it's assumed that the user want to run the benchmark.

So should we add a "-bench", a "-run" , or just continue with the same idea as NPB?

You are the final users, so you can choose or propose your favorite way. =)

@rouvoy
Copy link
Member Author

rouvoy commented Feb 13, 2016

You can take inspiration from NPB, but it is expected to have a new script with the same syntax (parameters, options) for all the containers of this project that will delegate to the specific script provided by the benchmark suite (whenever it exists and parameters/options can be mapped).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants