From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.20-rmap15a
Date: Tue, 3 Dec 2002 13:55:26 +0000 (UTC) [thread overview]
Message-ID: <asid4e$ci$1@ncc1701.cistron.net> (raw)
In-Reply-To: Pine.LNX.4.44L.0212011833310.15981-100000@imladris.surriel.com
In article <Pine.LNX.4.44L.0212011833310.15981-100000@imladris.surriel.com>,
Rik van Riel <riel@conectiva.com.br> wrote:
>This is a merge of rmap15a with marcelo's 2.4 bitkeeper tree,
>which is identical to 2.4.20-rc4 (he didn't push the makefile
>update). The only thing left out of the merge for now is
>Andrew Morton's read_latency patch, both because I'm not sure
>how needed it is with the elevator updates and because this
>part of the merge was too tricky to do at merge time; I'll port
>over Andrew Morton's read_latency patch later...
Just FYI:
I've tried this on our peering newsserver, you know, the same one
I tried a couple of 2.5.4X kernels on (Andrew knows ...)
Basically, performance sucks with rmap15a, with or without readlatency2.
See http://stats.cistron.nl/mrtg/html/wormhole.html
Monday 2-dec 16:00 -- Tuesday 3-dec 12:00 rmap15a + rl2
Tuesday 3-dec 12:00 -- Tuesday 3-dec 14:00 rmap15a
Tuesday 3-dec 14:20 -- now 2.4.20 vanilla
As you can see, the server accepted a lot less articles when
running rmap, as a result outgoing bandwidth dropped too.
I have no idea how to find out what the exact cause of this is,
so I didn't (it's still a production server and I can't let
it limp along for a too long period of time) that's why I
started with 'just FYI'. BTW, the server is not into swap - it
just looks like the working set of innd (the main article
accepting process) which includes mmap()s of the history
database is getting pushed out of memory by streaming IO,
which is really bad for performance. 2.4.20 does better on
this, and 2.5 a bit more even (but isn't stable)
Mike.
--
They all laughed when I said I wanted to build a joke-telling machine.
Well, I showed them! Nobody's laughing *now*! -- acesteves@clix.pt
next prev parent reply other threads:[~2002-12-03 13:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-01 20:35 [PATCH] 2.4.20-rmap15a Rik van Riel
2002-12-03 13:55 ` Miquel van Smoorenburg [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-01 20:56 Marc-Christian Petersen
2002-12-01 21:25 ` Rik van Riel
2002-12-01 21:41 ` Marc-Christian Petersen
2002-12-01 21:56 ` Con Kolivas
2002-12-02 0:18 ` Con Kolivas
2002-12-02 8:15 ` Jens Axboe
2002-12-02 8:51 ` Andrew Morton
2002-12-02 8:56 ` Jens Axboe
2002-12-02 12:38 ` Rik van Riel
2002-12-02 20:45 ` Willy Tarreau
2002-12-02 23:10 ` Rik van Riel
2002-12-03 6:21 ` Willy Tarreau
2002-12-02 21:46 ` Bill Davidsen
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='asid4e$ci$1@ncc1701.cistron.net' \
--to=miquels@cistron.nl \
--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