[GRADLE-3102] Performance regression with Java 8 Created: 06/Jun/14  Updated: 24/Jan/17  Resolved: 24/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: 2.0-rc-1
Fix Version/s: None

Type: Bug
Reporter: Radim Kubacki Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Known Issue Of:
2.0

 Description   

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:
1. It happens only if Gradle is run using Java 8 JVM.
2. It doesn't happen if daemon is used.
3. It affects all major platforms.
4. It happens with all Gradle versions.
5. Some short non-trivial builds are affected.

Currently it is suspected that while the JVM is asked to exit using 

System.exit(int)

it still performs JIT background compilation that cannot be interrupted and the process completion waits for this task.

 Comments   
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:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

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.

Generated at Wed Jun 30 12:40:01 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.