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

chore(build): increase Gradle memory limits #6334

Merged
merged 1 commit into from
Jan 6, 2025

Conversation

yuri1969
Copy link
Contributor

@yuri1969 yuri1969 commented Dec 5, 2024

What changes are being made and why?

By default the daemon is limited to 512MiB heap. Increasing that to 2GiB shaved around 10sec off the full build.

By default the daemon is limited to 512MiB heap. Increasing that to 2GiB
shaved around 10sec off the full build.
@yuri1969
Copy link
Contributor Author

yuri1969 commented Jan 3, 2025

This PR should prevent Gradle warnings, such as:

The Daemon will expire after the build after running out of JVM heap space.
The project memory settings are likely not configured or are configured to an insufficient value.
The daemon will restart for the next build, which may increase subsequent build times.
These settings can be adjusted by setting 'org.gradle.jvmargs' in 'gradle.properties'.
The currently configured max heap space is '512 MiB' and the configured max metaspace is '384 MiB'.
For more information on how to set these values, please refer to https://docs.gradle.org/8.10.1/userguide/build_environment.html#sec:configuring_jvm_memory in the Gradle documentation.
To disable this warning, set 'org.gradle.daemon.performance.disable-logging=true'.
Daemon will be stopped at the end of the build after running out of JVM heap space

Copy link
Member

@loicmathieu loicmathieu left a comment

Choose a reason for hiding this comment

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

LGTM, thanks

@loicmathieu loicmathieu merged commit 2307b24 into kestra-io:develop Jan 6, 2025
8 checks passed
@yuri1969 yuri1969 deleted the gradle-tuning branch January 6, 2025 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants