public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: "Håvard Wall" <haavardw@ifi.uio.no>
Cc: gentoo-dev@gentoo.org, werner.van.belle@vub.ac.be
Subject: Re: [gentoo-dev] compile time statistics
Date: 26 Jul 2003 09:50:42 -0400	[thread overview]
Message-ID: <1059227442.24877.25.camel@vertigo> (raw)
In-Reply-To: <3F22506A.8050902@ifi.uio.no>

On Sat, 2003-07-26 at 05:56, Håvard Wall wrote:
> 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 (?).

To be anywhere near the correct answer you would need to know:
- CPU type
- CPU speed
- Number of CPUs
- MAKEOPTS
- USE flags
- Some of the CFLAGS, particularly -march and -O

You would also have to cancel out any data gotten from a machine with
distcc or ccache enabled, since those will throw your accuracy way off. 
For example, I have a P166MMX machine running Gentoo on 32MB of RAM.  It
runs fine.  How is it setup?  Simple, I have it setup for distcc with
MAKEOPTS=-j4 and DISTCC_HOSTS="smpbox1/2 smpbox2/2 othermachine".  It
pretty much never does any compiling locally.  It can compile
applications almost as fast as working with one of my SMP machines.  The
data would be completely off on this machine if it were to be submitted.

-- 
Chris Gianelloni
Developer, Gentoo Linux


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-07-26 13:51 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 [this message]
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=1059227442.24877.25.camel@vertigo \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=haavardw@ifi.uio.no \
    --cc=werner.van.belle@vub.ac.be \
    /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