From: Fabio Riccardi <fabio@chromium.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: mingo@elte.hu, Zach Brown <zab@zabbo.net>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@redhat.com>
Subject: Re: numbers?
Date: Fri, 20 Apr 2001 14:12:38 -0700 [thread overview]
Message-ID: <3AE0A646.74079E95@chromium.com> (raw)
In-Reply-To: <E14qhu5-0002B8-00@the-village.bc.nu>
Alan,
SPEC connections are cumulative of static (70%) and dynamic (30%) pages, with the
dynamic using quite a bit of CPU (25%-30%) and the static pages dataset of several
(6-8) gigabytes.
The chromium server is actually much faster than thttpd and it is a complete web
server.
- Fabio
Alan Cox wrote:
> > Incidentally the same server running on a kernel with a multiqueue scheduler
> > achieves 1600 connections per second on the same machine, that was the original
> > reason for my message for a better scheduler.
>
> I get 2000 connections a second with a single threaded server called thttpd
> on my setup. Thats out of the box on 2.4.2ac with zero copy/sendfile.
>
> I've never had occasion to frob with tux or specweb
prev parent reply other threads:[~2001-04-20 21:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-20 3:38 user space web server accelerator support Fabio Riccardi
2001-03-20 3:51 ` David S. Miller
2001-03-20 3:58 ` Fabio Riccardi
2001-03-20 3:59 ` David S. Miller
2001-03-20 4:07 ` Fabio Riccardi
2001-03-20 13:08 ` Erik Mouw
2001-03-20 16:01 ` Zach Brown
2001-03-23 3:53 ` Fabio Riccardi
2001-03-23 19:14 ` Zach Brown
2001-03-23 20:24 ` kernel support for _user space_ web server accelerator Fabio Riccardi
2001-04-18 16:19 ` numbers? Ingo Molnar
2001-04-20 19:35 ` numbers? Fabio Riccardi
2001-04-20 18:42 ` numbers? Ingo Molnar
2001-04-20 21:23 ` numbers? Fabio Riccardi
2001-04-21 3:42 ` numbers? Ingo Molnar
2001-04-20 20:53 ` numbers? Alan Cox
2001-04-20 21:12 ` Fabio Riccardi [this message]
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=3AE0A646.74079E95@chromium.com \
--to=fabio@chromium.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zab@zabbo.net \
/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.