We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sometimes it is helpful to test the behavior of a system under different loads. For example, testing scale up and scale down behavior.
To do this, it is useful to be able to run multiple plans, one after the other.
The workaround for now is to do something like:
drill --benchmark 1 && \ drill --benchmark 2 && \ drill --benchmark 3
However, the downside of this approach is that such a test has to be documented externally from the benchmark file.
It would be nice to use the multi-doc feature of yaml to just define the 3 plans in a single benchmark file e.g.:
concurrency: 1 iterations: 100 plan: ... --- concurrency: 10 iterations: 100 plan: ... --- concurrency: 5 iterations: 100 plan: ...
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Sometimes it is helpful to test the behavior of a system under different loads. For example, testing scale up and scale down behavior.
To do this, it is useful to be able to run multiple plans, one after the other.
The workaround for now is to do something like:
However, the downside of this approach is that such a test has to be documented externally from the benchmark file.
It would be nice to use the multi-doc feature of yaml to just define the 3 plans in a single benchmark file e.g.:
The text was updated successfully, but these errors were encountered: