OpenSearch Benchmark is the macrobenchmarking framework for OpenSearch.
What is OpenSearch Benchmark?
If you are looking to performance test OpenSearch, then OpenSearch Benchmark is for you. It can help you with the following tasks:
- Running performance benchmarks and recording results
- Setting up and tearing down OpenSearch clusters for benchmarking
- Managing benchmark data and specifications across OpenSearch versions
- Discovering performance problems by attaching so-called telemetry devices
- Comparing performance results
- Creating customized workloads
We have also put considerable effort into OpenSearch Benchmark to ensure that benchmarking data are reproducible.
Documentation
Official documentation for OpenSearch Benchmark is available online.
Quick Start
Want to get started with OpenSearch Benchmark quickly? See OpenSearch Benchmark's Quick Start guide in the documentation.
Getting help
- Quick help:
opensearch-benchmark --help - Want to contribute? Look at OpenSearch Benchmark's Developer Guide for more information
- For any questions or answers, visit our community forum and Slack community channel #performance-benchmarking.
- File improvements or bug reports in our Github repo.
How to Contribute
See all details in the contributor guidelines.
License
This software is licensed under the Apache License, version 2 ("ALv2"), quoted below.
Copyright 2015-2022 OpenSearch https://opensearch.org/
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
1 maintainer
Release files for opensearch-benchmark 2.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| opensearch_benchmark-2.4.0.tar.gz | 515.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opensearch_benchmark-2.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.1 MB
Release files / opensearch_benchmark-2.4.0.tar.gz
| Download URL | opensearch_benchmark-2.4.0.tar.gz |
|---|---|
| Size | 515.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
075235ddda837c827f0aa76517a6e7e77f096ac46735a36086bb42982dd5191a
|
|
BLAKE2b-256 checksum How to use checksums |
7594e6e5617ef08549093b8b5034c6a111fb15dd599fcadda33091bb36ef3059
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 21, 2026.
Transparency logRelease files / opensearch_benchmark-2.4.0-py3-none-any.whl
| Download URL | opensearch_benchmark-2.4.0-py3-none-any.whl |
|---|---|
| Size | 615.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aed333e7c9dedfd93965c81ff440424c151a82c84d814b755f902b1074fbe7c0
|
|
BLAKE2b-256 checksum How to use checksums |
7b60a2ec5721df4a43cd5d41d940546b1b4f7f1311fd5bfc67830caa4c65d0cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 21, 2026.
Transparency log
