From: Willy Tarreau <willy@w.ods.org>
To: Bernd Eckenfels <be-mail2006@lina.inka.de>
Cc: linux-kernel@vger.kernel.org, gcoady@gmail.com
Subject: Re: Why is 2.4.32 four times faster than 2.6.14.6??
Date: Sun, 8 Jan 2006 12:16:38 +0100 [thread overview]
Message-ID: <20060108111638.GA15093@w.ods.org> (raw)
In-Reply-To: <20060108110919.GA6865@lina.inka.de>
On Sun, Jan 08, 2006 at 12:09:19PM +0100, Bernd Eckenfels wrote:
> On Sun, Jan 08, 2006 at 11:54:01AM +0100, Willy Tarreau wrote:
> > > it eats it in high interrupt load.
> > *high* ? he never goes far beyond 1000/s !
>
> it is 10 times higher on 2.6 than 2.4 (I dont think this can be explained
> by the timer, only.)
>
> > quite possibly, but I'd rather think it's more precisely related
> > to the ping-pong in the scheduler between grep, cut and ssh.
>
> Could be, that would also send smaller buffers to tcp...
that's true, and that could explain the higher interrupt rate.
> Gruss
> Bernd
Cheers,
Willy
next prev parent reply other threads:[~2006-01-08 11:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 6:16 Why is 2.4.32 four times faster than 2.6.14.6?? Grant Coady
2006-01-08 6:58 ` Markus Rechberger
2006-01-08 7:18 ` Bernd Eckenfels
2006-01-08 7:42 ` Grant Coady
2006-01-08 8:00 ` Bernd Eckenfels
2006-01-08 8:11 ` Con Kolivas
2006-01-08 9:12 ` Bernd Eckenfels
2006-01-08 12:04 ` Jan Engelhardt
2006-01-08 19:20 ` Grant Coady
2006-02-22 19:27 ` Enrico Weigelt
2006-02-22 23:17 ` Adrian Bunk
2006-01-08 7:28 ` Grant Coady
2006-01-08 9:57 ` Willy Tarreau
2006-01-08 10:23 ` Bernd Eckenfels
2006-01-08 10:54 ` Willy Tarreau
2006-01-08 11:09 ` Bernd Eckenfels
2006-01-08 11:16 ` Willy Tarreau [this message]
2006-01-08 11:18 ` Grant Coady
2006-01-09 2:37 ` Jesse Brandeburg
2006-01-09 2:46 ` Lee Revell
2006-01-09 2:59 ` Grant Coady
2006-01-09 6:56 ` Grant Coady
2006-01-08 11:05 ` Grant Coady
2006-01-08 18:21 ` Octavio Alvarez Piza
2006-01-08 19:27 ` Grant Coady
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=20060108111638.GA15093@w.ods.org \
--to=willy@w.ods.org \
--cc=be-mail2006@lina.inka.de \
--cc=gcoady@gmail.com \
--cc=linux-kernel@vger.kernel.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