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

build: Test on JDK 21 #64

Merged
merged 5 commits into from
Feb 22, 2024
Merged

build: Test on JDK 21 #64

merged 5 commits into from
Feb 22, 2024

Conversation

johanandren
Copy link
Member

No description provided.

Copy link
Member

@patriknw patriknw left a comment

Choose a reason for hiding this comment

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

LGTM

@johanandren
Copy link
Member Author

Seems like some consistent starvation detector test failures to look in to on JDK 21

@johanandren johanandren merged commit 1f03728 into main Feb 22, 2024
6 checks passed
@johanandren johanandren deleted the wip-jdk-21-tests branch February 22, 2024 16:16
@johanandren johanandren added this to the 2.1.1 milestone Feb 22, 2024
@@ -80,7 +80,7 @@ lazy val common: Seq[Setting[_]] =
val openModules =
if (isJdk17orHigher) Seq("--add-opens=java.base/java.util.concurrent=ALL-UNNAMED")
else Nil
"-Xms1G" :: "-Xmx1G" :: "-XX:MaxDirectMemorySize=256M" :: akkaProperties ++ openModules
"-Xms1G" :: "-Xmx16G" :: "-XX:MaxDirectMemorySize=256M" :: akkaProperties ++ openModules
Copy link
Member

Choose a reason for hiding this comment

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

What is the reason for this, what is taking that much memory? If it's about reducing risk of gc that cause flakiness in starvation test it should probably bump both -Xms and -Xmx, but I doubt 16G would be any better than for example 4G.

Copy link
Member Author

Choose a reason for hiding this comment

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

It's the test loop where it tries to simulate blocking on disk, on our modern macs it will hit OOM with smaller heaps, way before it manages to trigger slow enough IO. I'm sure it could be possible to come up with some other strategy, but this was the shortest path to make it work. On a slower disk/machine it will anyway not reach those amounts of heap, Xms is still 1G.

Copy link
Member

Choose a reason for hiding this comment

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

alright, thanks

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

Successfully merging this pull request may close these issues.

2 participants