All of lore.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <jjs@pobox.com>
To: mingo@elte.hu
Cc: Tux mailing list <tux-list@redhat.com>,
	Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Thomas Lussnig <tlussnig@bewegungsmelder.de>,
	linux-kernel@vger.kernel.org,
	khttpd mailing list <khttpd-users@zgp.org>
Subject: Re: [khttpd-users] khttpd vs tux
Date: Mon, 05 Nov 2001 20:46:29 -0800	[thread overview]
Message-ID: <3BE76B25.F670E250@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111051013230.2914-100000@localhost.localdomain>

Ingo,

Thanks for commenting on this -

Ingo Molnar wrote:

> On Sat, 3 Nov 2001, J Sloan wrote:
>
> > Nobody scales better 1-4 CPUs, as indicated
> > by specweb99 - at 8 CPUs linux is OK, but not
> > as dominating....
>
> This is a common misinterpretation of the TUX SPECweb99 numbers.
> Performance and scalability are two distinct things.

Absolutely correct, I spoke sloppily.
I should have said, "nobody performs better...".

But the scalability certainly _appears_
to be better than average -

> TUX maxes out 2-way and 4-way systems as well, while IIS does not appear
> to do a good job there. So we can say that it's proven that IIS does not
> scale well. I can still not say whether Linux+TUX scales well, i can only
> say that it's too fast for the given hardware :-)

indeed...

> why does it look like as if TUX scaled well on 1, 2, 4 CPUs? Because
> hardware designers are sizing up systems with more CPUs, so the true
> limits of the hardware show a similar scalability graph as the scalability
> graph would be of a scalable webserver.

Excellent point, thanks for making the distinction.

Thanks as well for the other excellent insights,
it was informative to hear what you had to say.

cu

jjs


  reply	other threads:[~2001-11-06  4:47 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 ` [khttpd-users] khttpd vs tux 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 [this message]
2001-11-03 19:37         ` Alan Cox
2001-11-04  0:07         ` Erik Mouw
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=3BE76B25.F670E250@pobox.com \
    --to=jjs@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=khttpd-users@zgp.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 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.