Adjust heap size and stack size of JVM of GitHub workflow #201
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Is 64 MB small or large? I'm not very sure.
Okay, 64 MB is quite large...
chengluyu
changed the title
LPTK
approved these changes
Dec 31, 2023
FYI I run things locally with 1M, which should be amply sufficient. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After pushing commits to PR, sometimes the CI would time out due to spending too much time on GC. The root of the cause is its insufficient memory. Considering that the built-in runner on GitHub has 7 GB of memory, this issue should be improvable. So, I set the maximum memory of JVM that sbt runs on to 4 GB in the GitHub workflow.
I also found that the default stack size (512 KB) is small for some test cases. Therefore, I also increase the stack size to 64 MB.