apache / apache/grails-intellij-plugin
Performance issue on large grails gradle multi project build
- Dominant language
- Java
- Stars
- 17
- Forks
- 4
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 4
Description
Hi,
we had massive performance issues on our large grails multi project. The problem occurs every startup or if we change something in the gradle.properties.
The problem is unrelated to OS or machine.
After investigation, we found out, that every module starts a java thread with`JetBrains/Toolbox/apps/IDEA-U/ch-0/231.8109.175/IntelliJ%20IDEA.app.plugins/groovy-grails/lib/groovy-grails-rt.jar!/idea-injected-traits.groovy`.
Which lead to 78 additional java threads which are freezing nearly the complete system.
It would be nice if we somehow can limit the max thread count to prevent the system from freezing.
IU-231.8109.175, JRE 17.0.6+10-b829.5x64 JetBrains s.r.o., OS Mac OS X(x86_64) v12.2.1, screens 3440.0x1440.0, 3584.0x2240.0; Retina
---
*Imported from [IDEA-319475](https://youtrack.jetbrains.com/issue/IDEA-319475) · Type: Bug · Votes: 0*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported startup and gradle.properties-change behavior in a large Grails multi-project build, then inspect the referenced groovy-grails-rt.jar and idea-injected-traits.groovy path. Done means the build no longer creates one excessive Java thread per module or freezes the system, with the thread count appropriately limited.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100