Hi Steve I find this feature very useful and hope it makes it into the Gradle head.
Etienne On 28.09.2010, at 18:51, Steve Appling wrote: > I've been working on making one of my builds faster and added a simple build > profiling report to gradle to help with my investigation. I think this may > be useful to others and I would like some feedback on it. It is currently > checked in to the profile branch. > > Profiling is triggered by using the --profile option. It writes an html > report to <build_dir>/reports/profile/. The reports are named based off of > the time when the report was run. > > As an example, I ran it twice on gradle itself. The first time was "gradlew > -xtest build --profile" after a clean (but with scripts and buildSrc built). > <profile-2010-09-28-09-00-01.html> > Configuration times and execution times are sorted with most expensive first. > > The second run was "gradlew -xtest build --profile" again, now that most > things should be up to date. > <profile-2010-09-28-09-14-27.html> > With everything up to date, it is now obvious that the checkstyle tasks are > not appropriately participating in the up-to-date checking. They probably > shouldn't run if the compile task doesn't need to run. Checkstyle tasks > account for over half of the task execution time. Additionally, buildSrc > also generates a profile report (not attached). It takes 3.4 seconds even > with nothing to do. > > I would appreciate any feedback. Does this seem useful? Is this format OK? > Is there any additional information that would be useful? > > -- > Steve Appling > Automated Logic Research Team > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email Etienne Studer Senior Software Developer Canoo Engineering AG Kirschgartenstrasse 5 CH-4051 Basel T +41 61 228 94 44 F +41 61 228 94 49 [email protected] www.canoo.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
