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

High rate of compilation requests after caches full #20618

Closed
JamesKingdon opened this issue Nov 18, 2024 · 4 comments
Closed

High rate of compilation requests after caches full #20618

JamesKingdon opened this issue Nov 18, 2024 · 4 comments

Comments

@JamesKingdon
Copy link
Contributor

Version: reproduced with 17.0.12.1 on Power, but likely applies to all versions and platforms.

While working on #20615 I noticed that after the code caches are marked full performance is degraded well below the rate seen with -Xint, and a possible explanation is that there is a very high rate of compilation request/compilation failure messages generated that show no sign of slowing down. Using verbose option compile* generated just under one million failure messages in a little over 1 minute of runtime:

tail failures.txt
#FAILURE:  t=68025 <WARNING: JIT Compilations are suspended>
#FAILURE:  t=68025 <WARNING: JIT Compilations are suspended>
#FAILURE:  t=68025 <WARNING: JIT Compilations are suspended>
#FAILURE:  t=68025 <WARNING: JIT Compilations are suspended>
#FAILURE:  t=68025 <WARNING: JIT Compilations are suspended>
#FAILURE:  t=68025 <WARNING: JIT Compilations are suspended>
#FAILURE:  t=68025 <WARNING: JIT Compilations are suspended>
#FAILURE:  t=68025 <WARNING: JIT Compilations are suspended>
#FAILURE:  t=68025 <WARNING: JIT Compilations are suspended>
Copy link

Issue Number: 20618
Status: Open
Recommended Components: comp:vm, comp:build, comp:gc

@mpirvu
Copy link
Contributor

mpirvu commented Nov 19, 2024

Fixed by #20511

@mpirvu mpirvu closed this as completed Nov 19, 2024
Copy link

Issue Number: 20618
Status: Closed
Actual Components: None :(
Actual Assignees: No one :(
PR Assignees: No one :(

@JamesKingdon
Copy link
Contributor Author

Thanks Marius, sorry I missed the existing fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants