Re: [gentoo-dev] compile time statistics

[Chris Gianelloni]

Creating your own unit of measure is probably the best way to go about
it.  There are simply so many variables that can affect the build time
of an ebuild... CPU type/speed, number of CPUs, USE flags, CFLAGS.  We
would definitely have to base the default USE/CFLAGS of the GRP.

On Fri, 2003-07-25 at 15:13, Svyatogor wrote:
> I was actually thinking of making this proposal :)
> Just a small comment. In LFS you can find estimate compile time in SBU
> (Standart Bash Units - time required to compile bash). It would be nice
> if we could include this kind of information into ebuild. Any ideas on
> whether that would be possible to do?
>
> ÷ ?? 25.07.2003, × 20:56, Rutger Lubbers ÐÉÛÅÔ:
> > People,
> >
> > This mail is about a question. The question is "how long does package x.y.z
> > take to compile on my machine?" Now my idea is, we have the emerge.log file
> > and can obtain some data from it, so we might "predict" that compile time for
> > that user.
> >
> > To get a fairly good prediction I need data. To get data I perhaps need a
> > prediction. Which needs data. So at the moment I don't know what to do.
> >
> > One part I have finished right now, I can get the compile times from the
> > emerge.log and submit it to a central database (see http://ripat.xs4all.nl).
> > Some "basic" querying I can do too.
> >
> > My questions to you is:
> > - would this be a nice feature to have?
> > - would you be willing to provide me with compile time statistics?
> > - do you have any hints / ideas what I can do to get this from a no dataless
> > project to a data having project?
> >
> > Thanks,
> >
> >
> > Rutger Lubbers
> >
> >
> > --
> > gentoo-dev@g.o mailing list
-- 
Chris Gianelloni
Developer, Gentoo Linux


--
gentoo-dev@g.o mailing list