From: J Sloan <jjs@pobox.com>
To: Oliver Xymoron <oxymoron@waste.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: heads-up: preempt kernel and tux NO-GO
Date: Tue, 27 Nov 2001 18:23:31 -0800 [thread overview]
Message-ID: <3C044AA3.CDCF7D67@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0111272007070.9338-100000@waste.org>
Oliver Xymoron wrote:
> On Tue, 27 Nov 2001, J Sloan wrote:
>
> > I have been looking into the tux2 webserver -
> > Man, what a thing of beauty. A web benchmark
> > that sends the load on the web server to 150
> > when running apache results in a load average
> > of maybe 2 when running tux, and much faster
> > results to boot - anyway, I digress....
>
> Loadavg isn't much of a measure here, it's a measure of the length of the
> runnable queue. If you've only got two processes because your server has a
> thread per processor, then yes, you'll see lower loadavg, but not lower
> load. A real measure would look at idle percentage and throughput.
That's easily done, and we know that load average
is a measure of tasks waiting to run - but rather
than throw more statistics around, I can say that
a Linux desktop running tux remains responsive
under a http load that would tend to monopolize it's
attention under apache -
Now I'm not knocking apache of course, it's the
standard these days, and there's nothing more
flexible or reliable - but there is indeed a niche
for a small, blindingly fast server like tux - and I
intend to explore that niche in coming months.
cu
jjs
next prev parent reply other threads:[~2001-11-28 2:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 1:17 heads-up: preempt kernel and tux NO-GO J Sloan
2001-11-28 2:12 ` Oliver Xymoron
2001-11-28 2:23 ` J Sloan [this message]
2001-11-28 2:30 ` Andrew Morton
2001-11-28 4:27 ` Robert Love
2001-11-29 4:11 ` data point: tux and low-latency patches OK J Sloan
2001-11-29 1:18 ` interrupt ? McEnroe
2001-11-29 17:07 ` Robert Love
2001-11-29 21:03 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2001-11-28 1:21 heads-up: preempt kernel and tux NO-GO J Sloan
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=3C044AA3.CDCF7D67@pobox.com \
--to=jjs@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.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