From: Dan Kegel <dank@kegel.com>
To: sean@dev.sportingbet.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux scalability?
Date: Mon, 21 May 2001 07:25:25 -0700 [thread overview]
Message-ID: <3B092555.DE564871@kegel.com> (raw)
Sean Hunter wrote:
> 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...
>
> 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.
The document tree (21 - 26 GB) is small enough to fit in RAM (32 GB),
so the speed of the disk is not likely to have a noticable impact.
(See http://boudicca.tux.org/hypermail/linux-kernel/2001week20/1276.html )
A lot of people during the Mindcraft discussion made the mistake
of calling the test unfair.
Regardless of whether the initial test was fair, it actually showed
interesting performance weaknesses in Linux, ones the kernel team
has successfully addressed.
> My point was that in the real world having this configuration for a webserver
> is unlikely to be sensible at all.
That's certainly true. On the other hand, worrying about how many
nanoseconds a system call takes isn't really an issue in the
real world, but kernel hackers love to optimize system call overhead
anyway. This is the same sort of intellectual challenge. Plus,
it impresses the beancounters, and they're the ones who buy the
systems and keep us all employed.
- Dan
next reply other threads:[~2001-05-21 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 14:25 Dan Kegel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-18 18:07 Linux scalability? Dan Kegel
2001-05-18 6:14 Linux OS boilerplate 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-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
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=3B092555.DE564871@kegel.com \
--to=dank@kegel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sean@dev.sportingbet.com \
/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