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

Oracle DevServices: limit CPU to 2 to avoid excessive memory consumption #25009

Merged
merged 1 commit into from
Apr 20, 2022

Conversation

Sanne
Copy link
Member

@Sanne Sanne commented Apr 19, 2022

Might fix #24939 , but can't verify it myself.

Replaces #24975

@Sanne Sanne merged commit 731abc3 into quarkusio:main Apr 20, 2022
@quarkus-bot quarkus-bot bot added this to the 2.9 - main milestone Apr 20, 2022
@Sanne Sanne deleted the OracleDevImprovements2 branch April 20, 2022 08:13
@Felk
Copy link
Contributor

Felk commented Apr 20, 2022

I suppose this means you were able to verify that the changes work as expected? I can still try it out on our gitlab runner if that's helpful to you. I might do it anyway with the nightly snapshot

@gsmet
Copy link
Member

gsmet commented Apr 20, 2022

@Felk please do. If you confirm it fixes your issues, I will backport it to 2.8.2.Final.

@Sanne
Copy link
Member Author

Sanne commented Apr 20, 2022

I suppose this means you were able to verify that the changes work as expected?

I was able to verify that my changes obtain the same effect as running the image with --cpus=2 . Since that works and shouldn't have drawbacks I decided to merge it, but I don't know for sure if that would fix your particular issue on a 100 core machine.

Should facilitate your testing with a snapshot, or the next release.

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

Successfully merging this pull request may close these issues.

Oracle Devservice fails to launch on hosts with over 100 CPU cores
4 participants