Hi Steve, I just took a look at the profile feature. This is a really cool feature I think. I would love to see this in the gradle trunk.
We're running quite complex gradle based build jobs on our Hudson. If the reporting would allow other (more formal) formats like e.g. xml, it would be very easy to integrate this profiling option into the gradle plugin for hudson. I'm dreaming about a checkbox in my hudson job configuration, that enables build job profiling and presents the profiling output on my job result view. What did you think about this? regards, René Am 28.09.10 18:51, schrieb Steve Appling: > 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). > > > > 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. > > > > 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 -- ------------------------------------ Rene Groeschke [email protected] http://www.breskeby.com http://twitter.com/breskeby ------------------------------------
