[GRADLE-3102] Performance regression with Java 8 Created: 06/Jun/14 Updated: 24/Jan/17 Resolved: 24/Jan/17
|Known Issue Of:|
There is a know problem where Gradle process can take noticeable time to exit the JVM after the build is finished. The extra time that is out of control of Gradle can be 1-2s.
Some known facts:
Currently it is suspected that while the JVM is asked to exit using
it still performs JIT background compilation that cannot be interrupted and the process completion waits for this task.
|Comment by Nathan Green [ 01/Jul/14 ]|
I see this same behavior with Maven 3.2, so I suspect the problem lies with the JDK itself.
|Comment by Benjamin Muschko [ 15/Nov/16 ]|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.
We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.
Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
|Comment by Benjamin Muschko [ 24/Jan/17 ]|
A lot of performance work has been performed in Gradle 2.x and 3.x so I am not even sure it is still an issue. Please open an issue on GitHub if you still think there's an issue.