public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Hunter <sean@dev.sportingbet.com>
To: Sasi Peter <sape@iq.rulez.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux scalability?
Date: Mon, 21 May 2001 11:42:21 +0100	[thread overview]
Message-ID: <20010521114221.B24919@dev.sportingbet.com> (raw)
In-Reply-To: <20010518091711.B26232@dev.sportingbet.com> <Pine.LNX.4.33.0105191026260.11903-100000@iq.rulez.org>
In-Reply-To: <Pine.LNX.4.33.0105191026260.11903-100000@iq.rulez.org>; from sape@iq.rulez.org on Sat, May 19, 2001 at 10:31:01AM +0200

Yup.  The problem is that you're trying to measure scalability in performance
of an i/o-bound task by comparing a machine with greater i/o resource but less
processing power with one with greater processing but poorer i/o.  Surprisingly
enough, the one with the best i/o wins.  This isn't really a fair comparison
between the two platforms.

If you put the same disk array on both machines and got the same results, then
you'd have a point.

My point was that in the real world having this configuration for a webserver
is unlikely to be sensible at all.

Sean

On Sat, May 19, 2001 at 10:31:01AM +0200, Sasi Peter wrote:
> On Fri, 18 May 2001, Sean Hunter wrote:
> 
> > Why would you want to run a web server with 8 processors rather than four
> > webservers with 2 each?
> 
> As you might already know, after the interviews to Mingo I assumed, that a
> major portion of the achievements was enabled by the 2.4 scalability
> enhacements. That is why I wrote to LKML, to ask about the 2.4
> scalability, if anybody out there could tell us about the linux kernel's
> scalability possibily compared to W2k scalability...
> 
> -- 
> SaPE - Peter, Sasi - mailto:sape@sch.hu - http://sape.iq.rulez.org/
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

  reply	other threads:[~2001-05-21 10:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-18 20:24 Linux OS boilerplate Scott Long
2001-02-18 20:32 ` Jeremy Jackson
2001-02-18 21:46 ` TeknoDragon
2001-02-19  1:47 ` Alan Cox
2001-02-19 10:07   ` Eric W. Biederman
2001-02-22  1:24     ` Tim Wright
2001-02-19  9:03 ` Paul Gortmaker
2001-02-20  4:29   ` H. Peter Anvin
2001-05-18  6:14   ` H. Peter Anvin
2001-05-18  7:24     ` Linux scalability? Sasi Peter
2001-05-18  8:12       ` reiser.angus
2001-05-18  8:30         ` Ronald Bultje
2001-05-18  8:30           ` reiser.angus
2001-05-18  9:05             ` Ronald Bultje
2001-05-18 19:28           ` [OT] " J Sloan
2001-05-18 19:38             ` David S. Miller
2001-05-18 19:46               ` Peter Rival
2001-05-18 19:57                 ` David S. Miller
2001-05-18 20:06                   ` Peter Rival
2001-05-18 20:13                     ` David S. Miller
2001-05-18 21:36                 ` J Sloan
2001-05-19  8:26         ` Sasi Peter
2001-05-18  8:17       ` Sean Hunter
2001-05-18 21:18         ` Rodger Donaldson
2001-05-19  8:31         ` Sasi Peter
2001-05-21 10:42           ` Sean Hunter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-18 18:07 Dan Kegel
2001-05-21 14:25 Dan Kegel

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=20010521114221.B24919@dev.sportingbet.com \
    --to=sean@dev.sportingbet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sape@iq.rulez.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