Skip to content

Conversation

@minborg
Copy link
Contributor

@minborg minborg commented Apr 8, 2025

This PR proposes to use an anonymous class rather than a lambda in order to improve startup time.

We need to make sure the regression is fixed by this. It might be the case that the regression is there because JDK-8347047 actually fixed an issue so that the segments could be collected by the GC.


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

Issue

  • JDK-8354121: Use a record class rather than a lambda in AbstractMemorySegmentImpl::cleanupAction (Enhancement - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 24514

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 8, 2025

👋 Welcome back pminborg! 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 Apr 8, 2025

@minborg 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:

8354121: Use a record class rather than a lambda in AbstractMemorySegmentImpl::cleanupAction

Reviewed-by: liach

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 8 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this 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 the rfr Pull request is ready for review label Apr 8, 2025
@openjdk
Copy link

openjdk bot commented Apr 8, 2025

@minborg The following label will be automatically applied to this pull request:

  • core-libs

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

@openjdk openjdk bot added the core-libs core-libs-dev@openjdk.org label Apr 8, 2025
@mlbridge
Copy link

mlbridge bot commented Apr 8, 2025

Webrevs

@minborg minborg changed the title 8348978: Regression ~8% on J2dBench-vimg_text_aa-ParGC only on linux aarch64 8354121: Use an anonymous class rather than a lambda in AbstractMemorySegmentImpl::cleanupAction Apr 9, 2025
@liach
Copy link
Member

liach commented Apr 9, 2025

@minborg Can we just use a local record to avoid accidental local captures (which caused the issue fixed by JDK-8347407)

Copy link
Member

@liach liach left a comment

Choose a reason for hiding this comment

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

Thanks for this error-proof improvement. Remember to update the JBS issue and PR titles.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Apr 9, 2025
@minborg minborg changed the title 8354121: Use an anonymous class rather than a lambda in AbstractMemorySegmentImpl::cleanupAction 8354121: Use a record class rather than a lambda in AbstractMemorySegmentImpl::cleanupAction Apr 9, 2025
@openjdk openjdk bot added ready Pull request is ready to be integrated and removed ready Pull request is ready to be integrated labels Apr 9, 2025
@minborg
Copy link
Contributor Author

minborg commented Apr 9, 2025

/integrate

@openjdk
Copy link

openjdk bot commented Apr 9, 2025

Going to push as commit c3e0439.
Since your change was applied there have been 8 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 Apr 9, 2025
@openjdk openjdk bot closed this Apr 9, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Apr 9, 2025
@openjdk
Copy link

openjdk bot commented Apr 9, 2025

@minborg Pushed as commit c3e0439.

💡 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

core-libs core-libs-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants