Skip to content

Dramatic performance degrade from build-info-extractor-gradle-4.4.9 to 4.4.10 #107

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ncabanis opened this issue Jan 18, 2017 · 2 comments

Comments

@ncabanis
Copy link

When upgrading the build-info-extractor-gradle from version 4.4.9 to 4.4.10, the Gradle configuration time is trippled from 10 seconds to over 30 seconds. Our build has 230 projects. We are using Gradle 3.3.

In another build, its even worse. 299 projects, Gradle 2.4 --> from 30 seconds to over 2.5 minutes.

Find attached, a screenshot from the profiler.

2017-01-18_09h45_52

@ncabanis ncabanis changed the title Dramatic performance impact from build-info-extractor-gradle-4.4.9 to 4.4.10 Dramatic performance degrade from build-info-extractor-gradle-4.4.9 to 4.4.10 Jan 18, 2017
@eyalbe4
Copy link
Contributor

eyalbe4 commented Jan 18, 2017

@ncabanis,
We are aware of this issue and it is the result of a critical fix added in 4.4.10. The fix resolved an issue that caused the artifactoryPublish task to be skipped for some sub projects when using the gradle daemon.
This is the commit which resolved the issue, and as a result, the addProjectEvaluationListener is added for every project applied. We're trying to figure out a way to improve the performance issue caused by this change.

@jochenberger
Copy link

jochenberger commented Feb 10, 2017

Could this be related to https://www.jfrog.com/jira/browse/HAP-860?

RobiNino pushed a commit to RobiNino/build-info that referenced this issue Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants