Skip to content

Conversation

@jsikstro
Copy link
Member

@jsikstro jsikstro commented Oct 23, 2025

Hello,

Please see the CSR for a more detailed explanation and specific information regarding the deprecation of the flag. To summarize, the JVM is well-equiped to detect system memory and handle potential truncation errors (see JDK-8367413 ), making MaxRAM largely redundant. Removing the default value from MaxRAM mainly impacts systems with more memory than the default (128GB on 64-bit systems and 4GB on 32-bit systems) that are running with -XX:-UseCompressedOops or -XX:+UseZGC, which disable compressed oops. We recommend users to use well-supported flags such as -Xms and -Xmx to influence heap sizing instead.

MaxRAM is used to a very small extent to influence memory allocation in JDK tests, where MaxRAMPercentage is much more common. When MaxRAM is eventually obsoleted, the few affected tests will need to be updated or use alternative flags.

Testing:

  • Oracle's tier1-8

Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change requires CSR request JDK-8369347 to be approved

Issues

  • JDK-8369346: Remove default value of and deprecate the MaxRAM flag (Enhancement - P4)
  • JDK-8369347: Remove default value of and deprecate the MaxRAM flag (CSR)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27952/head:pull/27952
$ git checkout pull/27952

Update a local copy of the PR:
$ git checkout pull/27952
$ git pull https://git.openjdk.org/jdk.git pull/27952/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27952

View PR using the GUI difftool:
$ git pr show -t 27952

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27952.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Oct 23, 2025

👋 Welcome back jsikstro! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Oct 23, 2025

@jsikstro This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8369346: Remove default value of and deprecate the MaxRAM flag

Reviewed-by: ayang, lkorinth

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot added graal graal-dev@openjdk.org hotspot hotspot-dev@openjdk.org labels Oct 23, 2025
@openjdk
Copy link

openjdk bot commented Oct 23, 2025

@jsikstro The following labels will be automatically applied to this pull request:

  • graal
  • hotspot

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added the rfr Pull request is ready for review label Oct 23, 2025
@jsikstro
Copy link
Member Author

/label remove graal
/label add hotspot-gc

@openjdk openjdk bot removed the graal graal-dev@openjdk.org label Oct 23, 2025
@openjdk
Copy link

openjdk bot commented Oct 23, 2025

@jsikstro
The graal label was successfully removed.

@openjdk openjdk bot added the hotspot-gc hotspot-gc-dev@openjdk.org label Oct 23, 2025
@openjdk
Copy link

openjdk bot commented Oct 23, 2025

@jsikstro
The hotspot-gc label was successfully added.

@mlbridge
Copy link

mlbridge bot commented Oct 23, 2025

Webrevs

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Oct 23, 2025
Copy link
Contributor

@lkorinth lkorinth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@jsikstro
Copy link
Member Author

Thank you for the reviews! @albertnetymk @lkorinth
/integrate

@openjdk
Copy link

openjdk bot commented Oct 29, 2025

Going to push as commit 6964ced.
Since your change was applied there have been 4 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Oct 29, 2025
@openjdk openjdk bot closed this Oct 29, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Oct 29, 2025
@openjdk
Copy link

openjdk bot commented Oct 29, 2025

@jsikstro Pushed as commit 6964ced.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hotspot hotspot-dev@openjdk.org hotspot-gc hotspot-gc-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants