From: Miquel van Smoorenburg <miquels@cistron.nl>
To: linux-mm@kvack.org
Subject: Keeping mmap'ed files in core regression in 2.6.7-rc
Date: Tue, 8 Jun 2004 16:29:18 +0200 [thread overview]
Message-ID: <20040608142918.GA7311@traveler.cistron.net> (raw)
I'm running a Usenet news server with a full feed. Software is
INN 2.4.1.
The list of all articles is called the "history database" and is
indexed by a history.hash and a history.index file, both sized
around 300-400 MB.
These hash and index files are mmap'ed by the main innd process.
A full usenet feed is 800-1000 GB/day, that's ~ 12MB / sec incoming
traffic going to the local spool disk. About the same amount of
traffic is sent out to peers.
With kernels 2.6.0 - 2.6.6, I did a "echo 15 > /proc/sys/vm/swappiness"
and the kernel did a pretty good job of keeping the mmap'ed files
mostly in core, which is needed for performance (100-200 database
queries/sec!).
This is the output with a 2.6.6 kernel:
# ps u -C innd
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
news 276 26.8 60.2 817228 624932 ? D 01:57 232:55 /usr/local/news/b
Now I tried 2.6.7-rc2 and -rc3 (well rc2-bk-latest-before-rc3) and
with those kernels, performance goes to hell because no matter
how much I tune, the kernel will throw out the mmap'ed pages first.
RSS of the innd process hovers around 200-250 MB instead of 600.
Ideas ?
Mike.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next reply other threads:[~2004-06-08 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 14:29 Miquel van Smoorenburg [this message]
2004-06-12 6:56 ` Nick Piggin
2004-06-14 14:06 ` Miquel van Smoorenburg
2004-06-15 3:03 ` Nick Piggin
2004-06-15 14:31 ` Miquel van Smoorenburg
2004-06-16 3:16 ` Nick Piggin
2004-06-16 3:50 ` Andrew Morton
2004-06-16 4:03 ` Nick Piggin
2004-06-16 4:23 ` Andrew Morton
2004-06-16 4:41 ` Nick Piggin
2004-06-17 10:50 ` Miquel van Smoorenburg
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=20040608142918.GA7311@traveler.cistron.net \
--to=miquels@cistron.nl \
--cc=linux-mm@kvack.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