public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rutger Lubbers <ripat@xs4all.nl>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] compile time statistics
Date: Sat, 26 Jul 2003 15:34:13 +0200	[thread overview]
Message-ID: <200307261534.13208.ripat@xs4all.nl> (raw)
In-Reply-To: <200307261105.43699.stuart@gentoo.org>

> > I believe gentoo-stats is already sampling a lot of the needed
> > information. An estimate could primarly be based on some "major"
> > factors; perhaps cpu-type and clock frequency. Then, if enough
> > statistics is available for the current architecture, on other settings
> > as well, sucb as -O flags and size of main memory (MAKEOPTS?). A kind of
> > hierarchical estimate... Could perhaps be hard to implement in practice
> > though (?).
> >
> > But I believe there probably is some limited set of factors that could
> > provide a reasonably good estimate.
>
> Whoever actually implements these ideas, please don't forget that you need
> a solution for capturing accurate stats on machines that use Portage's
> distcc support.  Because otherwise, your stats will not be as accurate as
> you'd like.

Yeah, this crossed my mind also. I believe that using distcc would "void" 
those stats, perhaps we can store it and maybe possible analyze if we can use 
any of it.

Rutger


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-07-26 13:33 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 [this message]
2003-07-26 13:50       ` Chris Gianelloni
2003-08-05 16:03         ` Stewart Honsberger
2003-07-25 18:54   ` Chris Gianelloni
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=200307261534.13208.ripat@xs4all.nl \
    --to=ripat@xs4all.nl \
    --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