-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Tune Cassandra options for faster startup #4309
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new heap defaults should also provide better OOTB support for some CI providers, correct?
@@ -58,8 +58,15 @@ public CassandraContainer(DockerImageName dockerImageName) { | |||
dockerImageName.assertCompatibleWith(DEFAULT_IMAGE_NAME); | |||
|
|||
addExposedPort(CQL_PORT); | |||
setStartupAttempts(3); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was never necessary and only hid the problem
@kiview yep! (are you also thinking about BitBucket? ;)) |
withEnv("HEAP_NEWSIZE", "128M"); | ||
withEnv("MAX_HEAP_SIZE", "1024M"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
by default, Cassandra will be allocating 10Gb of RAM or so - obviously not necessary for testing
We never attempted at tuning Cassandra options to make it start faster. Apparently, there are a few low hanging fruits (focused on single-node scenario) that make it start significantly faster:
Before:
After: