Skip to content
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

Evaluate Early Access builds of JDK 22.0.2 #107980

Open
2 of 3 tasks
ChrisHegarty opened this issue Apr 27, 2024 · 4 comments
Open
2 of 3 tasks

Evaluate Early Access builds of JDK 22.0.2 #107980

ChrisHegarty opened this issue Apr 27, 2024 · 4 comments
Labels
:Core/Infra/Core Core issues without another label :Performance All issues related to Elasticsearch performance including regressions and investigations Team:Core/Infra Meta label for core/infra team Team:Performance Meta label for performance team

Comments

@ChrisHegarty
Copy link
Contributor

ChrisHegarty commented Apr 27, 2024

This issue is intended to help track the evaluation of JDK 22.0.2 Early Access builds, in order to:

The motivation for this work is to enable Elasticsearch to bundle the JDK 22.0.2 when it is released ( expected 2024-07-16, see https://www.java.com/releases/ )

relates #106987

@ChrisHegarty ChrisHegarty added :Core/Infra/Core Core issues without another label Team:Core/Infra Meta label for core/infra team Team:Delivery Meta label for Delivery team labels Apr 27, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@elasticsearchmachine elasticsearchmachine removed the Team:Delivery Meta label for Delivery team label Apr 27, 2024
@ChrisHegarty
Copy link
Contributor Author

The G1 issue is reproducible on Linux x64 with the nyc_taxis benchmark, see https://github.com/elastic/elasticsearch-benchmarks/issues/1989.

We're currently running this benchmark with a locally built JDK 22.0.2 that includes the JDK bug fix https://bugs.openjdk.org/browse/JDK-8329528. The benchmark is run over and over in a loop, just evaluating that Elasticsearch does not crash. So far, it passes successfully. This issue will be updated with more specifics when they are available.

@ChrisHegarty ChrisHegarty added the Team:Performance Meta label for performance team label Apr 27, 2024
@elasticsearchmachine elasticsearchmachine removed the Team:Performance Meta label for performance team label Apr 27, 2024
@gareth-ellis gareth-ellis added the :Performance All issues related to Elasticsearch performance including regressions and investigations label Apr 27, 2024
@elastic elastic deleted a comment from Infectious-Smile Apr 27, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-perf (Team:Performance)

@elasticsearchmachine elasticsearchmachine added the Team:Performance Meta label for performance team label Apr 27, 2024
@gareth-ellis
Copy link
Member

gareth-ellis commented Apr 29, 2024

We've run about 40 iterations so far of the benchmark, even lowering the heap further, however the issue has not reoccurred.

Update 30/4 - 67 iterations and still going

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label :Performance All issues related to Elasticsearch performance including regressions and investigations Team:Core/Infra Meta label for core/infra team Team:Performance Meta label for performance team
Projects
None yet
Development

No branches or pull requests

3 participants