search

eclipse-openj9 / openj9-website

openj9-website
24 stars 28 forks source link

Update latest release section for 0.43.0 #363

Closed Sreekala-Gopakumar closed 5 months ago

Sreekala-Gopakumar commented 6 months ago

What's New update for the website, for 0.43.0 (February 2024)

Sreekala-Gopakumar commented 6 months ago

First draft (0.42.0 content is live at https://www.eclipse.org/openj9). Note: this isn't an exhaustive list of all the changes, just the main ones:

Eclipse OpenJ9 version 0.43.0 released

February 2024

We're pleased to announce the availability of Eclipse OpenJ9™ v0.43.0.

This release supports OpenJDK 8, 11, 17, and 21. For more information about supported platforms and OpenJDK versions, see Supported environments.

Other updates in this release include the following:

  • Linux® x86 64-bit, Linux on POWER® LE 64-bit, and Linux on IBM Z® 64-bit builds on OpenJDK 8, 11, and 17 now use gcc 11.2 compiler. Linux AArch64 64-bit moved to gcc 10.3 compiler from gcc 7.5 compiler on OpenJDK 8 and 11.
  • A new option, -XX:[+|-]CRIUSecProvider is added to enable or disable CRIUSECProvider during the checkpoint phase. You can choose to continue to use all the existing security providers during the checkpoint phase instead of the CRIUSECProvider.
  • A new option, -XX:Compatibility is added to enable a compatibility mode that OpenJ9 can run in to support applications that require specific capabilities. In release 0.43.0, the compatibility mode is provided for the Elasticsearch application only.
  • A new option, -XX:[+|-]CpuLoadCompatibility is added to enable or disable the OpenJDK behavior of the getProcessCpuLoad() and getSystemCpuLoad() methods in OpenJ9 so that these methods return 0 when called in OpenJ9 for the first time. This change in the method return value makes it easier to differentiate between the first call behavior and an error that needs further investigation.
  • The large page memory allocation is made based on the size of the total code cache for JIT. If the configured large page size is greater than the size of the total code cache for JIT, then the page size that is used for code cache allocation is recalculated. The next available lower page size on the platform is used for the code cache allocation.

To read more about these and other changes, see the OpenJ9 user documentation.

Performance highlights include:

  • CRIU supports dynamic garbage collection (GC) heap resizing that adapts to different physical memory or container size between checkpoint and restore environments.
Sreekala-Gopakumar commented 6 months ago

@pshipton @vijaysun-omr - Are there any performance updates that you want to highlight in the website? Any other what's new update to be added here? Thanks!

vijaysun-omr commented 6 months ago

You may want to consider saying that CRIU support for Power/IBM Z is available in Java11/Java17 as well in this release (in addition to Java21, where CRIU support was made available in 0.42)

vijaysun-omr commented 6 months ago

@tajila should we be documenting the CRIU support behavior where we (GC) adapt to different physical memory or container size between checkpoint and restore environments ? I am unsure if that was done before the code complete date for 0.43 is the other question.

Sreekala-Gopakumar commented 6 months ago

You may want to consider saying that CRIU support for Power/IBM Z is available in Java11/Java17 as well in this release (in addition to Java21, where CRIU support was made available in 0.42)

@vijaysun-omr - In 0.38.0 release, we are already mentioning that the CRIU tool is available for OpenJDK 11 and later running on Linux® x86, Linux on POWER® (Little Endian), and Linux on IBM Z® only.

https://eclipse.dev/openj9/docs/version0.38/#technical-preview-of-criu-support

So, do we have to add anything else in this release? Thanks!

Sreekala-Gopakumar commented 6 months ago

@tajila should we be documenting the CRIU support behavior where we (GC) adapt to different physical memory or container size between checkpoint and restore environments ? I am unsure if that was done before the code complete date for 0.43 is the other question.

@tajila @vijaysun-omr - Any update on this? Thanks!

tajila commented 6 months ago

should we be documenting the CRIU support behavior where we (GC) adapt to different physical memory or container size between checkpoint and restore environments ? I am unsure if that was done before the code complete date for 0.43 is the other question.

The changes are in 0.43. We have a description of the feature here: https://github.com/eclipse-openj9/openj9/issues/18217#issuecomment-1790807574

Sreekala-Gopakumar commented 6 months ago

should we be documenting the CRIU support behavior where we (GC) adapt to different physical memory or container size between checkpoint and restore environments ? I am unsure if that was done before the code complete date for 0.43 is the other question.

The changes are in 0.43. We have a description of the feature here: eclipse-openj9/openj9#18217 (comment)

@tajila @vijaysun-omr - I have updated the Performance highlights included section with this change. Could you please check if the description is correct. Anything else to be added? Thanks!

Sreekala-Gopakumar commented 6 months ago

should we be documenting the CRIU support behavior where we (GC) adapt to different physical memory or container size between checkpoint and restore environments ? I am unsure if that was done before the code complete date for 0.43 is the other question.

The changes are in 0.43. We have a description of the feature here: eclipse-openj9/openj9#18217 (comment)

@tajila @vijaysun-omr - I have updated the Performance highlights included section with this change. Could you please check if the description is correct. Anything else to be added? Thanks!

@tajila @vijaysun-omr - Can I finalise the content added in the Performance highlights included section? Thanks!

vijaysun-omr commented 6 months ago

Looks fine to me, @Sreekala-Gopakumar

Sreekala-Gopakumar commented 5 months ago

Published