All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Eric Cuendet <jean-eric.cuendet@linkvest.com>
To: Mark Mielke <mark@mark.mielke.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: UNIX bench better on 2.2 than 2.4?
Date: Fri, 15 Mar 2002 11:44:51 +0100	[thread overview]
Message-ID: <3C91D0A3.4050500@linkvest.com> (raw)
In-Reply-To: <3C91A822.7030304@linkvest.com> <20020315053211.A5619@mark.mielke.cc>

>
>
>>Results:
>>Host1: 2xPIII 550MHz / 1Gb RAM / RAID5 SCSI / 2.4.6smp + LVM
>>       Result: 164.7
>>Host2: 2xPIII 866MHz / 1Gb RAM / RAID1 soft IDE / 2.4.16smp + LVM
>>       Result: 195.7
>>Host3: 1xPIII 800MHz / 512Mb RAM / IDE / 2.2.19 RedHat 6.2
>>       Result: 208.6
>>Host4: 1xPIII 600MHz / 256Mb RAM / IDE / 2.4.19-pre2-ac4-preempt
>>       Result: 153.6
>>
>
>I dunno what Unix bench is... but isn't 153.6/208.6 close to 600/800
>in terms of a fraction?
>
Yes, you are right for this one.
But what impressed me is between Host2/Host3. One is a dual-866 with 
2.4.16 and the other is mono-800 with 2.2.19. And the host3 with 2.2.19 
is ~7% better than Host2 (Not counting that Host3 has ~8% more CPU 
clock, which should have be ~15% better for Host2 vs Host3...)

>Make Host3 or Host4 have both versions of the linux kernel in /boot
>and try each on the same machine.
>
But that's just what I'd like to see. How 2.4 compares vs 2.2
-jec



  reply	other threads:[~2002-03-15 10:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15  7:52 UNIX bench better on 2.2 than 2.4? Jean-Eric Cuendet
2002-03-15 10:32 ` Mark Mielke
2002-03-15 10:44   ` Jean-Eric Cuendet [this message]
2002-03-15 10:56     ` Mark Mielke
  -- strict thread matches above, loose matches on Subject: below --
2002-03-15  7:36 Jean-Eric Cuendet

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=3C91D0A3.4050500@linkvest.com \
    --to=jean-eric.cuendet@linkvest.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@mark.mielke.cc \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.