-
Notifications
You must be signed in to change notification settings - Fork 484
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
Using different Java runtimes with OpenSearch. #670
Conversation
d0fd32e
to
9e41bed
Compare
|
||
### Benchmarking JDKs | ||
|
||
TODO |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Benchmarking tests were run across JDK 8, 11, 14, 15, and 17 with both the x64 and arm versions of OpenSearch. Latency and throughput were the primary metrics recorded. JDK 17 consistently performed superior to the rest for both versions. JDK 15 was the closest to the metrics of JDK 17, followed by JDK 8 and 11. Meanwhile, JDK 14 was significantly slower than the other choices. Based on the results, JDK 17 is decisively the best option for running OpenSearch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added almost as is and linked to OpenSearch#1276 for details.
Do you have a meaty example of how much better JDK 17 is? Something like "For example, searching through an index with XYZ data in such and such cluster reduced latency by X% and increased throughput by Z%."?
nice. Can we share more details on the tests with JDK17? Did it perform better irrespective GC type (CMS or G1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made a few comments. I happened to come across this issue and noticed that you tagged dvenable
in it. I assume you meant to tag me - @dlvenable .
@dblock How far out is this blog post? |
|
@stockholmux This is ready. |
Thanks @dblock I'll review. Next publish ideal date will be on Tuesday. Sound good? |
Adjusted date to Monday. |
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
Signed-off-by: dblock <[email protected]>
@stockholmux Can we please ship this? Updated the date to today. |
I was hoping to get community feedback for opensearch-project/opensearch-plugins#132 out of this, too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks complete and ready to publish. Apologies for the delay.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love me a technical blog post, nice work everyone
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: dblock [email protected]
Description
A draft for a blog post to be published with 1.3.0 on Java Runtimes.
Requesting feedback and additions from @reta @smortex @dvenable @martin-gaievski and others.
Issues Resolved
#628
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.