[PR #1072] [MERGED] Improve GRADLE build Performance #1027

New issue

Closed

opened 2026-02-26 01:32:40 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 01:32:40 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/jberkel/sms-backup-plus/pull/1072
Author: @ChenZhangg
Created: 10/13/2021
Status: ✅ Merged
Merged: 10/26/2021
Merged by: @kurahaupo

Base: master ← Head: Modify_GRADLE_3

📝 Commits (2)

5043216 Improve GRADLE build Performance
9131202 merge those changes in one task

📊 Changes

1 file changed (+7 additions, -0 deletions)

View changed files

📝 build.gradle (+7 -0)

📄 Description

Parallel test execution maxParallelForks, running multiple test cases in parallel is useful and helpful when there are several CPU cores.

According to Process forking options, Gradle will run all tests in a single forked VM by default. This can be problematic if there are a lot of tests or some very memory-hungry ones.
one option is to fork a new test VM after a certain number of tests have run. So our recommendation is to configure "forkEvery" and we give a specific value of 100

Disable report generation, Gradle will automatically create test reports by default which will slowing down the overall build. So it's better to disable the test reports while we don't need it

=====================
If there are any inappropriate modifications in this PR, please give me a reply and I will change them.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/jberkel/sms-backup-plus/pull/1072 **Author:** [@ChenZhangg](https://github.com/ChenZhangg) **Created:** 10/13/2021 **Status:** ✅ Merged **Merged:** 10/26/2021 **Merged by:** [@kurahaupo](https://github.com/kurahaupo) **Base:** `master` ← **Head:** `Modify_GRADLE_3` --- ### 📝 Commits (2) - [`5043216`](https://github.com/jberkel/sms-backup-plus/commit/504321683df06623f7017260716da53542610557) Improve GRADLE build Performance - [`9131202`](https://github.com/jberkel/sms-backup-plus/commit/913120283e11c3e6ba36975c7459a259cad04b97) merge those changes in one task ### 📊 Changes **1 file changed** (+7 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `build.gradle` (+7 -0) </details> ### 📄 Description [Parallel test execution maxParallelForks](https://docs.gradle.org/current/userguide/performance.html#parallel_test_execution), running multiple test cases in parallel is useful and helpful when there are several CPU cores. According to [Process forking options](https://docs.gradle.org/current/userguide/performance.html#forking_options), Gradle will run all tests in a single forked VM by default. This can be problematic if there are a lot of tests or some very memory-hungry ones. one option is to fork a new test VM after a certain number of tests have run. So our recommendation is to configure "forkEvery" and we give a specific value of 100 [Disable report generation](https://docs.gradle.org/current/userguide/performance.html#report_generation), Gradle will automatically create test reports by default which will slowing down the overall build. So it's better to disable the test reports while we don't need it ===================== If there are any inappropriate modifications in this PR, please give me a reply and I will change them. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>