From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Gerrit Huizenga <gh@us.ibm.com>, "David S. Miller" <davem@redhat.com>
Cc: hadi@cyberus.ca, tcw@tempest.prismnet.com,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com, niv@us.ibm.com
Subject: Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000
Date: Fri, 06 Sep 2002 11:26:49 -0700 [thread overview]
Message-ID: <60449712.1031311608@[10.10.2.3]> (raw)
In-Reply-To: <E17nNhM-0003PD-00@w-gerrit2>
>> One of our goals is to actually take the next generation of the most
>> common "large system" web server and get it to scale along the lines
>> of Tux or some of the other servers which are more common on the
>> small machines. For some reasons, big corporate customers want lots
>> of features that are in a web server like apache and would also like
>> the performance on their 8-CPU or 16-CPU machine to not suck at the
>> same time. High ideals, I know, wanting all features *and* performance
>> from the same tool... Next thing you know they'll want reliability
>> or some such thing.
>>
>> Why does Tux keep you from taking advantage of all the
>> feature of Apache? Anything Tux doesn't handle in it's
>> fast path is simple fed up to Apache.
>
> You have to ask the hard questions...
Ultimately, to me at least, the server doesn't really matter, and
neither do the absolute benchmark numbers. Linux should scale under
any reasonable workload. The point of this is to look at the Linux
kernel, not the webserver, or specweb ... they're just hammers to
beat on the kernel with.
The fact that we're doing something different from everyone else
and turning up a different set of kernel issues is a good thing,
to my mind. You're right, we could use Tux if we wanted to ... but
that doesn't stop Apache being interesting ;-)
M.
next prev parent reply other threads:[~2002-09-06 18:24 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 18:30 Troy Wilson
2002-09-05 20:59 ` jamal
2002-09-05 22:11 ` Troy Wilson
2002-09-05 22:39 ` Nivedita Singhvi
2002-09-05 23:01 ` Dave Hansen
2002-09-05 22:48 ` Nivedita Singhvi
2002-09-06 1:47 ` jamal
2002-09-06 3:38 ` Nivedita Singhvi
2002-09-06 3:58 ` David S. Miller
2002-09-06 4:20 ` Nivedita Singhvi
2002-09-06 4:17 ` David S. Miller
2002-09-07 0:05 ` Troy Wilson
2002-09-06 3:56 ` David S. Miller
2002-09-06 3:47 ` David S. Miller
2002-09-06 6:48 ` Martin J. Bligh
2002-09-06 6:51 ` David S. Miller
2002-09-06 7:36 ` Andrew Morton
2002-09-06 7:22 ` David S. Miller
2002-09-06 9:54 ` jamal
2002-09-06 14:29 ` Martin J. Bligh
2002-09-06 15:38 ` Dave Hansen
2002-09-06 16:11 ` Martin J. Bligh
2002-09-06 16:21 ` Nivedita Singhvi
2002-09-06 15:29 ` Dave Hansen
2002-09-06 16:29 ` Martin J. Bligh
2002-09-06 17:36 ` Dave Hansen
2002-09-06 18:26 ` Andi Kleen
2002-09-06 18:31 ` John Levon
2002-09-06 18:33 ` Dave Hansen
2002-09-06 18:36 ` David S. Miller
2002-09-06 18:45 ` Martin J. Bligh
2002-09-06 18:43 ` David S. Miller
2002-09-06 19:19 ` Nivedita Singhvi
2002-09-06 19:21 ` David S. Miller
2002-09-06 19:45 ` Nivedita Singhvi
2002-09-06 19:26 ` Andi Kleen
2002-09-06 19:24 ` David S. Miller
2002-09-06 19:45 ` Martin J. Bligh
2002-09-06 17:26 ` Gerrit Huizenga
2002-09-06 17:37 ` David S. Miller
2002-09-06 18:19 ` Gerrit Huizenga
2002-09-06 18:26 ` Martin J. Bligh [this message]
2002-09-06 18:36 ` David S. Miller
2002-09-06 18:51 ` Martin J. Bligh
2002-09-06 18:48 ` David S. Miller
2002-09-06 19:05 ` Gerrit Huizenga
2002-09-06 19:01 ` David S. Miller
2002-09-06 20:29 ` Alan Cox
2002-09-06 18:34 ` David S. Miller
2002-09-06 18:57 ` Gerrit Huizenga
2002-09-06 18:58 ` David S. Miller
2002-09-06 19:52 ` Gerrit Huizenga
2002-09-06 19:49 ` David S. Miller
2002-09-06 20:03 ` Gerrit Huizenga
2002-09-06 23:48 ` Troy Wilson
2002-09-11 9:11 ` Eric W. Biederman
2002-09-11 14:10 ` Martin J. Bligh
2002-09-11 15:06 ` Eric W. Biederman
2002-09-11 15:15 ` David S. Miller
2002-09-11 15:31 ` Eric W. Biederman
2002-09-11 15:27 ` Martin J. Bligh
2002-09-12 7:28 ` Todd Underwood
2002-09-12 12:30 ` jamal
2002-09-12 13:57 ` Todd Underwood
2002-09-12 14:11 ` Alan Cox
2002-09-12 14:41 ` todd-lkml
2002-09-12 23:12 ` David S. Miller
2002-09-13 21:59 ` todd-lkml
2002-09-13 22:04 ` David S. Miller
2002-09-15 20:16 ` jamal
2002-09-16 4:23 ` David S. Miller
2002-09-16 14:16 ` todd-lkml
2002-09-16 19:52 ` David S. Miller
2002-09-16 21:32 ` todd-lkml
2002-09-16 21:29 ` David S. Miller
2002-09-16 22:53 ` David Woodhouse
2002-09-16 22:46 ` David S. Miller
2002-09-16 23:03 ` David Woodhouse
2002-09-16 23:08 ` Jeff Garzik
2002-09-16 23:02 ` David S. Miller
2002-09-16 23:48 ` Jeff Garzik
2002-09-16 23:43 ` David S. Miller
2002-09-17 0:01 ` Jeff Garzik
2002-09-17 10:31 ` jamal
2002-09-13 22:12 ` Nivedita Singhvi
2002-09-12 17:18 ` Nivedita Singhvi
2002-09-06 23:56 ` Troy Wilson
2002-09-06 23:52 ` David S. Miller
2002-09-07 0:18 ` Nivedita Singhvi
2002-09-07 0:27 ` Troy Wilson
2002-09-05 20:47 Feldman, Scott
2002-09-06 11:44 Robert Olsson
2002-09-06 14:37 ` Martin J. Bligh
2002-09-06 15:38 ` Robert Olsson
2002-09-06 18:35 Manfred Spraul
2002-09-06 18:38 ` David S. Miller
2002-09-06 19:40 ` Manfred Spraul
2002-09-06 19:34 ` David S. Miller
2002-09-10 12:02 ` Robert Olsson
2002-09-10 16:55 ` Manfred Spraul
2002-09-11 7:46 ` Robert Olsson
2002-09-10 14:59 Mala Anand
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='60449712.1031311608@[10.10.2.3]' \
--to=martin.bligh@us.ibm.com \
--cc=davem@redhat.com \
--cc=gh@us.ibm.com \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.com \
--cc=tcw@tempest.prismnet.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®