From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Symlinking /usr/portage/distfiles
Date: Wed, 31 Jan 2007 13:13:42 -0600 [thread overview]
Message-ID: <200701311313.42668.bss03@volumehost.net> (raw)
In-Reply-To: <200701311758.22588.alan@linuxholdings.co.za>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
On Wednesday 31 January 2007 09:58, Alan McKinnon
<alan@linuxholdings.co.za> wrote about 'Re: [gentoo-user]
Symlinking /usr/portage/distfiles':
> On Wednesday 31 January 2007, Bo Ørsted Andresen wrote:
> > Furthermore Pentium 4 is a joke (it performs horribly). A 2 GHz
> > (Dothan I presume) Pentium-M should be faster than a 2,8 GHz Pentium
> > 4. My timing is for an 1,6 GHz (Banias) Pentium-M btw.
>
> This sounds odd, but I'm not a cpu expert so can't really comment. Care
> to elaborate on why the P4 performs so horribly?
The instruction pipeline is very long, the CPU <-> RAM bandwith is quite
small, and the pipeline has to be emptied any time the branch predictor is
wrong. While the pipeline fills, the CPU works but no results are
visible.
Hz has never been a complete trump of other issues affecting CPU
performance, but is always a factor to consider. (Among CPUs that are
otherwise identical, higher Hz wins.)
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss03@volumehost.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.org/ \_/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-31 19:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 13:16 [gentoo-user] Symlinking /usr/portage/distfiles Vlad Dogaru
2007-01-27 13:29 ` Mick
2007-01-27 13:31 ` Dale
2007-01-27 16:40 ` Vlad Dogaru
2007-01-27 18:14 ` Jürgen Geuter
2007-01-27 19:05 ` Jeffrey Rollin
2007-01-27 19:52 ` Vlad Dogaru
2007-01-27 23:48 ` Neil Bothwick
2007-01-29 7:38 ` Alan McKinnon
2007-01-29 13:20 ` Albert Hopkins
[not found] ` <200701292112.22080.alan@linuxholdings.co.za>
2007-01-30 9:29 ` Neil Bothwick
2007-01-30 12:22 ` Bo Ørsted Andresen
2007-01-30 13:09 ` Neil Bothwick
2007-01-30 12:59 ` Albert Hopkins
2007-01-30 7:25 ` Bo Ørsted Andresen
[not found] ` <200701301422.12957.bo.andresen@zlin.dk>
[not found] ` <200701301552.37737.alan@linuxholdings.co.za>
2007-01-30 14:06 ` Uwe Thiem
2007-01-31 11:02 ` Alan McKinnon
2007-01-31 12:22 ` Uwe Thiem
2007-01-31 12:34 ` Bo Ørsted Andresen
2007-01-31 13:23 ` Alan McKinnon
2007-01-31 13:22 ` Alan McKinnon
2007-01-31 13:38 ` Bo Ørsted Andresen
2007-01-31 15:58 ` Alan McKinnon
2007-01-31 19:13 ` Boyd Stephen Smith Jr. [this message]
2007-01-31 23:49 ` Mark Kirkwood
2007-02-01 8:51 ` Nelson, David (ED, PAR&D)
2007-02-01 9:10 ` Alan McKinnon
2007-02-01 18:43 ` Ralf Stephan
2007-02-01 20:41 ` Dan Farrell
2007-01-30 14:35 ` Neil Bothwick
2007-01-30 16:26 ` Anthony E. Caudel
2007-01-31 11:16 ` Alan McKinnon
2007-01-31 12:25 ` Dan Farrell
2007-02-01 10:30 ` Neil Bothwick
2007-01-31 15:22 ` Anthony E. Caudel
2007-01-30 19:10 ` Mick
2007-01-30 19:31 ` Neil Bothwick
2007-01-30 20:18 ` Albert Hopkins
2007-01-30 22:39 ` Neil Bothwick
2007-01-31 0:45 ` Steve Dibb
2007-01-31 1:22 ` Neil Bothwick
2007-01-31 10:37 ` Boyd Stephen Smith Jr.
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=200701311313.42668.bss03@volumehost.net \
--to=bss03@volumehost.net \
--cc=gentoo-user@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