[
https://issues.apache.org/jira/browse/IGNITE-19922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17749935#comment-17749935
]
Kirill Sizov commented on IGNITE-19922:
----------------------------------------
Some low-hanging fruits on configuring Gradle to reduce the pressure on the OS.
The reason why the daemons don't go away is the way Gradle was designed:
??These worker daemon processes will persist across builds and can be reused
during subsequent builds. If system resources get low, however, Gradle will
stop any unused worker daemons.??
[https://docs.gradle.org/current/userguide/worker_api.html#creating_a_worker_daemon]
Starting the build with {{--no-daemon}} parameter should help.
There is a way to limit the number of parallel workers to any desired number:
[https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_configuration_properties]
Either by passing an extra command line argument {{--max-workers}}
Or by setting {{org.gradle.workers.max}} property in
{{~/.gradle/gradle.properties}}
> Gradle checkstyle tasks are greedy
> ----------------------------------
>
> Key: IGNITE-19922
> URL: https://issues.apache.org/jira/browse/IGNITE-19922
> Project: Ignite
> Issue Type: New Feature
> Reporter: Mikhail Pochatkin
> Priority: Major
> Labels: ignite-3
> Attachments: image-2023-07-06-11-18-40-515.png, screenshot-1.png
>
>
> This is memory consumption during {{gradlew checkstyleMain}} execution -
> goes from ~10 GB to 30. All CPU cores are also at 100%. This causes chrome
> tabs to unload and overall stress on the system.
> Also, RAM usage does not go down after this command unless I kill/stop Gradle
> daemons
> !image-2023-07-06-11-18-40-515.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
