Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We recently updated default volume type to
gp3
. This caused regression in indexing latency forvectorsearch
workload.Upon debugging we realized that this is happening due to reduced disk throughput on gp3.
The default throughput for gp3 volume type is 125Mb/s, where as for gp2 it was 250Mb/s.
Setting the
throughput
property in CDK code for gp3 volume didn't work as it is not currently supported out of the box, see aws/aws-cdk#24107. They have provided a work around which is not a clean way.Given OpenSearch is an IOPS heavy application it makes more sense to use the best available EBS volume type to get maximum performance.
IO1
volume type requiresiops
property to be set and it is calculated based on disk size,IOPS=50*Disk size in GB
. Seeio1
in https://aws.amazon.com/ebs/volume-types/.Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.