-
Notifications
You must be signed in to change notification settings - Fork 87
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
[Bug]: Performance Regression in OpenSearch 2.19.1
with OpenSearch Benchmark 1.12.0
(Not Observed with 1.11.0
)
#786
Comments
2.19.1
with OpenSearch Benchmark 1.12.0
2.19.1
with OpenSearch Benchmark 1.12.0
2.19.1
with OpenSearch Benchmark 1.12.0
2.19.1
with OpenSearch Benchmark 1.12.0
2.19.1
with OpenSearch Benchmark 1.12.0
2.19.1
with OpenSearch Benchmark 1.12.0
(Not Observed with 1.11.0
)
Adding @rishabh6788 @gkamat to please take a look. |
Created a single node cluster on
OSB version is 1.12:
Merged down to 10 segments:
It is more or less in line with 1.11 numbers.
|
@rishabh6788 has very good points above. One way to confirm whether there is indeed an issue is to install the two OSB versions on two separate (but identical) load-generation instances and target the same cluster in separate query-only tests (after ingestion and segment merge has completed.) Please try this out and update the issue with your findings. Thanks. |
Describe the bug
I've observed a significant performance drop in OpenSearch
2.19.1
when tested with OpenSearch Benchmark1.12.0
. However, the same OpenSearch version (2.19.1
) performs consistent with benchmark1.11.0
in par with OS2.19.0
.Coming from opensearch-project/OpenSearch#17404 to fix the regression in
desc_sort_timestamp
for 3.0.0, I have taken2.19.1
as baseline, but when used benchmark version1.12.0
I can see a Performance Regression but does not see when used benchmark1.11.0
.I was able to get this issue consistently on 5 Ec2 instances.
To reproduce
Created an
r5.xlarge
Ec2ami-05b10e08d247fb927
. Using EBS Gp3 16000 IOPS, 500Gb and 1000 throughput. I have seen the same results with EBS defaults 3000 IOPS and 125 throughput, so increasing dint help.Install java
sudo yum install -y https://corretto.aws/downloads/latest/amazon-corretto-21-x64-linux-jdk.rpm
.sudo yum install -y pip
.pip install opensearch-benchmark
which installs the latest1.12.0
.sudo yum install -y git
.Download OS
2.19.1
withwget https://artifacts.opensearch.org/releases/core/opensearch/2.19.1/opensearch-min-2.19.1-linux-x64.tar.gz
.Update the bash profile to use jdk21 as default.
mkdir DataDir
and update theopensearch-2.19.1/config/opensearch.yml
to use this directory. Exampleopensearch-2.19.1/config/jvm.options
Coming from https://opensearch.org/docs/latest/getting-started/quickstart/ , disabled memory paging and swapping
sudo swapoff -a
and updated the/etc/sysctl.conf
tovm.max_map_count=262144
.Ensure the cluster is up and running
opensearch-benchmark execute-test --target-hosts http://127.0.0.1:9200 --workload big5 --client-options timeout:120 --kill-running-processes --include-tasks desc_sort_timestamp
.Expected behavior
With opensearch-benchmark
1.11.0
.Additional context
DataDir
) which has thebig5
index data created by benchmark with @expani and running benchmark cli on his host shows the same issue.The text was updated successfully, but these errors were encountered: