Ah interesting! I think i need to unit test more...
Thanks Christoph. Come back so we can go get a beer. :D
austen
On 9/13/05, Christoph Lofi <[EMAIL PROTECTED]> wrote:
>
>
>
> > Hi Austen.
> >
> > Well, a neat summary can be found at the hackyCGQM analysis page; just
> select the extras panel, look for hackyCGQM, seect buildFailures,
> hacky2004-all and the date you are interested in and you get a 14-days
> summary.
> > There, you will see that for example Julie spent around 14 hours of
> building between Aug-27 and Sep-10 while you just had 2.8 hours. We can also
> see that you are just compiling while Julie runs checkstyle and junit very
> frequently (thats the reason for this difference in wasted time for
> building).
> >
> > My experience to build time:
> > The buildtime of quickstart on my machine varies between 1:30 and 8:00
> minutes (!!). The influence factors seem to be a) actual memory load b)
> actual hard disk activity. As soon as I start doing anything which requires
> the hard disk to work, build time jump up like crazy. Also, a high memory
> load slows the build down ('cause then the system will start swapping which
> leads to new hard disk activities). I think the main problem here is the
> slow speed of my harddisk (4200rpm). Aarron, who is using those hard disks
> from hell (15000rpm) doesn't have any problem with that. I am clomplety
> convinced that the hard drive is the bottleneck during the builds (its not
> processor or something because the average processor load is around 7 or 8
> percent).
> > -> Use faster hard drives and don't do anything which distracts your hard
> drive (like starting other programs, watching movies, etc). Prevent context
> switching (which will force your system to swap memory to/from the
> harddrive). Then your (or Julies) build will speed up.
> >
> > Cheers,
> > Christoph
> >
> >
> >
> > On 9/10/05, Austen Itsuji Ito <[EMAIL PROTECTED] > wrote:
> > > Tonight I was thinking about how long Hackystat takes to build locally,
> > > (I think Professor Johnson did something to me so that I would think
> > > about Hackystat on a Friday night) and was wondering how the ant build
> > > sensor collects data. I know that Hackystat collects data on how many
> > > times you invoke a build, but does the sensor collect information on how
> > > long the build takes?
> > >
> > > The reason why I am asking this question is because I was wondering how
> > > much of Julie and my time was spent waiting for the build process to
> > > finish before we actually test our changes. I wanted to see how much
> > > time was spent building/testing as compared to earlier hackyInstaller
> > > development where changes could be tested immediately in Eclipse.
> > >
> > > I know that lots of time is saved by integrating hackyInstaller into
> > > Hackystat, but I was just curious to see if our active time was an
> > > indication that we spent 15 hours building and only 5 hours hacking
> away.
> > >
> > > I know for a fact that Julie's system would take a very long time just
> > > to run a "ant -q cleanAll quickStart", where my laptop would build much
> > > faster. I believe this was due to my development being done on linux,
> > > where Julie is running Windows XP. If the active time does include how
> > > long a build takes, then perhaps Julie didn't work double my hours ;p
> > >
> > > Thanks and sorry if the question I am asking has been brought up before.
> > >
> > > Cheers,
> > > austen
> > >
> >
> >
>
>
