Do you want another profile snapshot from us now that your fix has been applied?
If so, is sampling ok?
Hans Dockter wrote:
On Nov 20, 2009, at 8:05 PM, Steve Appling wrote:
After Hans' dependency resolution performance fix, the huge performance problem we saw
has been fixed (thanks Hans!). I still find, however, that the overhead of all the up to
date checking is not worth it. When everything is up to date and there is nothing to do,
running "build -xtest" for our big project in the 0.8 version takes about 1:11
(min:sec) and doing the same thing with the current trunk version takes 1:24.
In my test project I had the following profiling results. For a build were nothing needed to be done, 40 percent of the time consumed Ivy for coming up with the dependencies. The state change checking needs the classpath to do comparisons. 10 percent of the time was consumed by our Ivy result translation (we might be able to improve this). This test project did not have many source files. It will be interesting to see whether with a larger codebase source change detection will play an important role here.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
Is there a way to disable the up to date checks for particular tasks? I don't
think it is currently useful for compileJava or Copy type of tasks and would
like to try disabling it there.
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
