From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: "Justin Piszcz" <jpiszcz@hotmail.com>,
baldrick@free.fr, gene.heskett@verizon.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.6 appears to be 3 to 4 times slower than 2.6.5.
Date: Tue, 18 May 2004 15:23:20 +0200 [thread overview]
Message-ID: <200405181519.17233.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <BAY18-F106WMUe77sHG0002bb5f@hotmail.com>
On Monday 17 of May 2004 17:06, Justin Piszcz wrote:
> Sorry to all, it turns out (in two separate cases I had two different
> problems that affected the results).
>
> Case 1: No SMP turned on for CPU w/HT after fix (~4.78 seconds compile time
> (2.6GHZ w/HT))
> Case 2: Box had 4GB of NON-ECC memory in it, only recognized 2.56GB, took
> out (2) 1GB DDR DIMM's, and the speed returned what it should be. (~4.3
> seconds compile time (3.0GHZ w/HT))
>
> The control box was a 2.53GHZ (533MHZ BUS w/NO HT) = ~5.3seconds
>
> I have not tested 2.6.6 recently, but in one of my tests I believe it
> worked OK, ever since 2.6.6 removed my /etc/lilo.conf and /etc/mtab and
> several other files, I do not wish to touch that kernel with a 10 foot poll
> :-P due to the IDE disk flush/cache issue.
I told you this already: 2.6.6 IDE changes don't cause data corruption
- but fixes some instead (that's why there were merged so quickly!)
so stop spreading FUD and see http://bugme.osdl.org/show_bug.cgi?id=2672.
next prev parent reply other threads:[~2004-05-19 3:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 15:06 Justin Piszcz
2004-05-18 13:23 ` Bartlomiej Zolnierkiewicz [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-19 12:28 Piszcz, Justin Michael
2004-05-19 13:16 ` Bartlomiej Zolnierkiewicz
2004-05-18 8:32 Daniel Blueman
2004-05-17 14:24 Alastair Stevens
2004-05-17 22:26 ` Andrew Morton
2004-05-18 9:19 ` Alastair Stevens
2004-05-15 12:04 Justin Piszcz
2004-05-15 14:38 ` Gene Heskett
2004-05-17 8:07 ` Duncan Sands
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=200405181519.17233.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=baldrick@free.fr \
--cc=gene.heskett@verizon.net \
--cc=jpiszcz@hotmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®