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

JDK-8306768: CodeCache Analytics reports wrong threshold #1295

Conversation

AntonKozlov
Copy link
Member

@AntonKozlov AntonKozlov commented Apr 25, 2023

Jcmd CodeCache_Analytics uses own implementation of threshold calculation, allowing an error to creep in, making report invalid. The suggestion is to use the existing method for free ratio calculation. After the fix, the reported values become sane.

java -XX:InitialCodeCacheSize=1G -XX:ReservedCodeCacheSize=1G ...

cmd jdk.compiler/com.sun.tools.javac.launcher.Main  Compiler.CodeHeap_Analytics | grep -A 2 "Threshold for method to be considered 'cold'"

Threshold for method to be considered 'cold':    -2037.960
min. hotness =   1016
avg. hotness =   2048
--
Threshold for method to be considered 'cold':    -2037.960
min. hotness =   1016
avg. hotness =   2048
--
Threshold for method to be considered 'cold':    -2037.960
No hotness data available

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-8306768: CodeCache Analytics reports wrong threshold

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/1295/head:pull/1295
$ git checkout pull/1295

Update a local copy of the PR:
$ git checkout pull/1295
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/1295/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1295

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/1295.diff

Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 25, 2023

👋 Welcome back akozlov! 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 openjdk bot added the rfr Pull request is ready for review label Apr 25, 2023
@mlbridge
Copy link

mlbridge bot commented Apr 25, 2023

Webrevs

Copy link
Member

@phohensee phohensee left a comment

Choose a reason for hiding this comment

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

Lgtm.

@openjdk
Copy link

openjdk bot commented Apr 25, 2023

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

8306768: CodeCache Analytics reports wrong threshold

Reviewed-by: phh

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:

  • e132605: 8296545: C2 Blackholes should allow load optimizations
  • d5cbf22: 8306658: GHA: MSVC installation could be optional since it might already be pre-installed
  • bf0606a: 8283566: G1: Improve G1BarrierSet::enqueue performance
  • e6e6bed: 8252990: Intrinsify Unsafe.storeStoreFence
  • 24e91c1: 8302594: use-after-free in Node::destruct
  • d964229: 8302172: [JVMCI] HotSpotResolvedJavaMethodImpl.canBeInlined must respect ForceInline
  • 3e0e4f0: 8301338: Identical branch conditions in CompileBroker::print_heapinfo
  • ee63f83: 8296412: Special case infinite loops with unmerged backedges in IdealLoopTree::check_safepts

Please see this link for an up-to-date comparison between the source branch of this pull request and 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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@phohensee) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Apr 25, 2023
@AntonKozlov
Copy link
Member Author

Thanks for review! The bug is also approved by the label.

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Apr 26, 2023
@openjdk
Copy link

openjdk bot commented Apr 26, 2023

@AntonKozlov
Your change (at version d1bb171) is now ready to be sponsored by a Committer.

@phohensee
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Apr 26, 2023

Going to push as commit 243e643.
Since your change was applied there have been 8 commits pushed to the master branch:

  • e132605: 8296545: C2 Blackholes should allow load optimizations
  • d5cbf22: 8306658: GHA: MSVC installation could be optional since it might already be pre-installed
  • bf0606a: 8283566: G1: Improve G1BarrierSet::enqueue performance
  • e6e6bed: 8252990: Intrinsify Unsafe.storeStoreFence
  • 24e91c1: 8302594: use-after-free in Node::destruct
  • d964229: 8302172: [JVMCI] HotSpotResolvedJavaMethodImpl.canBeInlined must respect ForceInline
  • 3e0e4f0: 8301338: Identical branch conditions in CompileBroker::print_heapinfo
  • ee63f83: 8296412: Special case infinite loops with unmerged backedges in IdealLoopTree::check_safepts

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Apr 26, 2023
@openjdk openjdk bot closed this Apr 26, 2023
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Apr 26, 2023
@openjdk
Copy link

openjdk bot commented Apr 26, 2023

@phohensee @AntonKozlov Pushed as commit 243e643.

💡 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
integrated Pull request has been integrated
2 participants