mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Thomas Lussnig <tlussnig@bewegungsmelder.de>,
	linux-kernel@vger.kernel.org,
	khttpd mailing list <khttpd-users@zgp.org>,
	Tux mailing list <tux-list@redhat.com>
Subject: Re: [khttpd-users] khttpd vs tux
Date: Sun, 4 Nov 2001 01:07:03 +0100	[thread overview]
Message-ID: <20011104010703.H23391@arthur.ubicom.tudelft.nl> (raw)
In-Reply-To: <E1606Lo-0006ZD-00@the-village.bc.nu> <Pine.LNX.4.30.0111032014580.9446-100000@mustard.heime.net>
In-Reply-To: <Pine.LNX.4.30.0111032014580.9446-100000@mustard.heime.net>; from roy@karlsbakk.net on Sat, Nov 03, 2001 at 08:18:19PM +0100

On Sat, Nov 03, 2001 at 08:18:19PM +0100, Roy Sigurd Karlsbakk wrote:
> > Each GigE card will need its own 66MHz PCI bus. Each PCI bridge will need
> > to be coming off a memory bus that can sustain all of these and the CPU
> > at once.
> >
> > At that point it really doesnt look much like a PC.
> 
> How much raw speed do you think I can manage to get out of a really cool
> n-way server from Compaq? I beleive we'll go for a Compaq server, as
> that's what's been decided some time ago.

Not that much. Alan's point is that you're pushing the limit of the
memory bandwidth, not the number of CPUs. This is the single reason
that high traffic websites either use some serious non-PC hardware (IBM
Z-series, for example) or a large number of PCs in parallel to share
the load.

> I read something by Linus about linux scalability, and I beleive he said
> that 'linux [2.4] scales good up to 4 cpus, but not that good futher on
> [to 8?]'. Can anyone fill in the holes here?

The number of CPUs really doesn't matter in this case. With several
GigE cards memory bandwidth and latency is your main problem.


Erik

-- 
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Faculty
of Information Technology and Systems, Delft University of Technology,
PO BOX 5031, 2600 GA Delft, The Netherlands  Phone: +31-15-2783635
Fax: +31-15-2781843  Email: J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/

  parent reply	other threads:[~2001-11-04  0:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3BE427CD.702@bewegungsmelder.de>
2001-11-03 18:02 ` Roy Sigurd Karlsbakk
2001-11-03 19:08   ` Thomas Lussnig
2001-11-03 19:14     ` Roy Sigurd Karlsbakk
2001-11-03 19:21     ` Alan Cox
2001-11-03 19:18       ` Roy Sigurd Karlsbakk
2001-11-03 19:31         ` J Sloan
2001-11-04  1:19           ` Alan Cox
2001-11-05 10:15           ` Ingo Molnar
2001-11-06  4:46             ` J Sloan
2001-11-03 19:37         ` Alan Cox
2001-11-04  0:07         ` Erik Mouw [this message]
2001-11-04 15:32           ` John Alvord
     [not found] <3BE42379.2050604@bewegungsmelder.de>
2001-11-03 17:08 ` Roy Sigurd Karlsbakk
     [not found] <20011103165129.B26040@fenrus.demon.nl>
2001-11-03 16:56 ` Roy Sigurd Karlsbakk
     [not found] <20011103162642.A25824@fenrus.demon.nl>
2001-11-03 16:43 ` Roy Sigurd Karlsbakk
2001-11-03 18:18   ` Miquel van Smoorenburg
2001-11-03 20:24   ` Dirk Moerenhout
2001-11-03 16:21 Roy Sigurd Karlsbakk
2001-11-04  5:26 ` [khttpd-users] " Chul Lee

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=20011104010703.H23391@arthur.ubicom.tudelft.nl \
    --to=j.a.k.mouw@its.tudelft.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=khttpd-users@zgp.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roy@karlsbakk.net \
    --cc=tlussnig@bewegungsmelder.de \
    --cc=tux-list@redhat.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

all inboxes | Powered by JetHome®