Add properties to improve build speed

[henni99]

Optimize build performance by adding caching, parallel execution, and configure-on-demand settings

[gemini-code-assist]

Hello @henni99, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request aims to improve build speed by adding several properties to the gradle.properties file. Specifically, it increases the JVM memory allocation, enables the Gradle build cache, enables parallel builds, and sets other JVM arguments for performance tuning.

Highlights

• JVM Memory Increase: The org.gradle.jvmargs property is updated to increase the maximum heap size to 4GB and sets other JVM options for memory management and garbage collection.
• Gradle Build Cache: The org.gradle.caching property is enabled to reuse outputs from previous builds, potentially speeding up subsequent builds.
• Parallel Builds: The org.gradle.parallel property is enabled to allow Gradle to run tasks in parallel, which can significantly reduce build times for multi-module projects.

Changelog

• gradle.properties
  • Increased JVM memory allocation to -Xmx4g.
  • Added -XX:+HeapDumpOnOutOfMemoryError to generate heap dumps on out-of-memory errors.
  • Added -XX:+UseParallelGC to use the parallel garbage collector.
  • Set -XX:MaxMetaspaceSize=512m to limit the maximum metaspace size.
  • Added -Dkotlin.daemon.jvm.options=-XX:MaxMetaspaceSize=1g to configure the Kotlin daemon JVM options.
  • Added -Dlint.nullness.ignore-deprecated=true to ignore deprecated nullness lint checks.
  • Enabled Gradle's build cache with org.gradle.caching=true.
  • Enabled parallel builds with org.gradle.parallel=true.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

---

A Gradle build, slow and vast,
With tweaks and settings, speed amassed.
Cache enabled,
Parallel staged,
Faster builds arrive at last.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to improve build speed by adding several properties to the gradle.properties file. The changes include increasing the JVM memory, enabling parallel garbage collection, setting maximum metaspace sizes, ignoring deprecated lint nullness checks, enabling the Gradle build cache, and enabling parallel builds. Overall, these changes seem reasonable and should contribute to faster build times.

Merge Readiness

The changes introduced in this pull request appear to be beneficial for improving build speed. I don't see any immediate critical issues that would block merging. However, it would be beneficial to monitor the build performance after these changes are deployed to ensure the desired improvements are realized and that no regressions are introduced. I am unable to directly approve this pull request, and recommend that others review and approve this code before merging.