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
The benchmark test script can be used locally with a few additional steps, but there is no written instruction. Adding the instruction will benefit other developers who wants to run performance test automatically. Current document: https://github.com/opensearch-project/opensearch-build/tree/2.9.0/src/test_workflow#benchmarking-tests Code: https://github.com/opensearch-project/opensearch-build/tree/2.9.0/src/test_workflow/benchmark_test
Add the instruction to use the benchmark test script locally at https://github.com/opensearch-project/opensearch-build/tree/2.9.0/src/test_workflow#benchmarking-tests
n/a
No response
The text was updated successfully, but these errors were encountered:
@rishabh6788 Can you look in to this issue?
Sorry, something went wrong.
rishabh6788
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe
The benchmark test script can be used locally with a few additional steps, but there is no written instruction.
Adding the instruction will benefit other developers who wants to run performance test automatically.
Current document: https://github.com/opensearch-project/opensearch-build/tree/2.9.0/src/test_workflow#benchmarking-tests
Code: https://github.com/opensearch-project/opensearch-build/tree/2.9.0/src/test_workflow/benchmark_test
Describe the solution you'd like
Add the instruction to use the benchmark test script locally at https://github.com/opensearch-project/opensearch-build/tree/2.9.0/src/test_workflow#benchmarking-tests
Describe alternatives you've considered
n/a
Additional context
No response
The text was updated successfully, but these errors were encountered: