From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] compile time statistics
Date: 25 Jul 2003 14:54:56 -0400 [thread overview]
Message-ID: <1059159296.4089.6.camel@vertigo> (raw)
In-Reply-To: <1059160421.2178.5.camel@sergey.swdevelopers.net>
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@gentoo.org mailing list
--
Chris Gianelloni
Developer, Gentoo Linux
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-25 18:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 17:56 [gentoo-dev] compile time statistics Rutger Lubbers
2003-07-25 18:49 ` Chris Gianelloni
2003-07-25 19:13 ` Svyatogor
2003-07-25 18:46 ` Rutger Lubbers
2003-07-25 18:51 ` Werner Van Belle
2003-07-26 9:56 ` Håvard Wall
2003-07-26 10:05 ` Stuart Herbert
2003-07-26 10:11 ` Håvard Wall
2003-07-26 13:34 ` Rutger Lubbers
2003-07-26 13:50 ` Chris Gianelloni
2003-08-05 16:03 ` Stewart Honsberger
2003-07-25 18:54 ` Chris Gianelloni [this message]
2003-07-26 10:35 ` Håvard Wall
2003-07-26 8:47 ` FRLinux
2003-07-26 14:50 ` Rutger Lubbers
2003-07-26 15:13 ` Lisa Marie Seelye
2003-07-26 15:21 ` Tal Peer
2003-07-26 15:30 ` Rutger Lubbers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1059159296.4089.6.camel@vertigo \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox