public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Mieland <dma147@mieland-programming.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Some important questions to the officals of www.gentoo.org
Date: Sun, 11 Jul 2004 01:08:20 +0200	[thread overview]
Message-ID: <200407110108.21021.dma147@mieland-programming.de> (raw)
In-Reply-To: <20040710234423.326fcefe@snowdrop.home>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Sonntag, 11. Juli 2004 00:44 schrieb Ciaran McCreesh:
> On Sun, 11 Jul 2004 00:39:03 +0200 Alexander Mieland
> <dma147@mieland-programming.de> wrote:
> | Daniel and me, Alex, got the idea of a database which contains merge
> | times   of all currently available (unmasked) gentoo packages for x86
> | architecture.
>
> ...pretty useless, really, unless you plan to provide times for both
> SMP and non-SMP kit. Otherwise you'll get *horridly* skewed results for
> packages which can't handle -j>1.
>
> Heck, even distcc is enough to upset this beyond the point of
> usability.

ACK.
it's surely in our mind to provide as much information as we can. I'm also 
planning on a second dedicated machine, which has a Pentium 4 with 
HT-technology to provide the SMP-part of the merge-times. In the future, 
if all is running and the response of the users is good enough, we hope 
that we can also provide the merge-times for other architectures than 
x86.

By the way, as long as we dont have a second machine with smp-support, it 
should be possibly to get reasonably accurate results if we multiply the 
number of cpus and then divide through a factor like 1.2. You can test 
it, it should be reasonably accurate.

But as I said, we are planning on a second machine with smp and also on 
merge-time information for other architectures.

(please overlook my horrible grammars)

Yours sincerely,

- -- 
Alexander Mieland                      System: Gentoo 2004.1, 2.6.7 SMP
APP - Another PHP Program                 Registered Linux-User #249600
http://www.php-programs.de                        http://counter.li.org
http://www.mieland-programming.de            s/Alexander Mieland/dma147
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA8HblkxKnzj3lcIERAr0QAJ0TMsiXzDYp6TdZjDP9UaxDbUmp9gCePRH3
xNvjEIhIbfXQeJwkVtfdWw4=
=eN25
-----END PGP SIGNATURE-----

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-07-10 23:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-10 19:38 [gentoo-dev] Some important questions to the officals of www.gentoo.org Alexander Mieland
2004-07-10 20:29 ` Mike Frysinger
2004-07-10 22:05 ` Grant Goodyear
2004-07-10 22:39   ` Alexander Mieland
2004-07-10 22:44     ` Ciaran McCreesh
2004-07-10 23:08       ` Alexander Mieland [this message]
2004-07-10 23:29         ` Chris Gianelloni
2004-07-10 23:41           ` Alexander Mieland
2004-07-10 23:32         ` Ciaran McCreesh
2004-07-10 23:45     ` marduk
2004-07-11  0:37     ` Mike Frysinger
2004-07-11  0:54       ` Joseph Booker
2004-07-11  1:32         ` Marius Mauch
2004-07-12 20:25 ` Aron Griffis
2004-07-12 20:45   ` Don Seiler

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=200407110108.21021.dma147@mieland-programming.de \
    --to=dma147@mieland-programming.de \
    --cc=gentoo-dev@lists.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