[MINOR][FLINK] Enable parallel Maven builds (-T 1C) in Flink CI#12365
Closed
zhanglistar wants to merge 1 commit into
Closed
[MINOR][FLINK] Enable parallel Maven builds (-T 1C) in Flink CI#12365zhanglistar wants to merge 1 commit into
zhanglistar wants to merge 1 commit into
Conversation
Use all available CPU cores for Maven module compilation by adding -T 1C (one thread per core) to all mvn invocations. Also bump MAVEN_OPTS heap from 2g to 4g to accommodate the higher memory pressure from concurrent module builds.
Contributor
Author
|
Seems useless. |
This file contains hidden or 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
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.
What changes are proposed in this pull request?
Use all available CPU cores for Maven module compilation by adding -T 1C (one thread per core) to all mvn invocations. Also bump MAVEN_OPTS heap from 2g to 4g to accommodate the higher memory pressure from concurrent module builds.
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?