From: Johannes Weiner <hannes@saeurebad.de>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org
Subject: Re: PERF: performance tests with the split LRU VM in -mm
Date: Tue, 29 Jul 2008 15:51:16 +0200 [thread overview]
Message-ID: <87tze84x4b.fsf@saeurebad.de> (raw)
In-Reply-To: <20080724222510.3bbbbedc@bree.surriel.com> (Rik van Riel's message of "Thu, 24 Jul 2008 22:25:10 -0400")
Hi,
Rik van Riel <riel@redhat.com> writes:
> In order to get the performance of the split LRU VM (in -mm) better,
> I have performed several performance tests with the following kernels:
> - 2.6.26 "2.6.26"
> - 2.6.26-rc8-mm1 "-mm"
> - 2.6.26-rc8-mm1 w/ "evict streaming IO cache first" patch "stream"
> Patch at: http://lkml.org/lkml/2008/7/15/465
> - 2.6.26-rc8-mm1 w/ "fix swapout on sequential IO" patch "noforce"
> Patch at: http://marc.info/?l=linux-mm&m=121683855132630&w=2
>
> I have run the performance tests on a Dell pe1950 system
> with 2 quad-core CPUs, 16GB of RAM and a hardware RAID 1
> array of 146GB disks.
>
> The tests are fairly simple, but took a fair amount of time to
> run due to the size of the data set involved (full disk for dd,
> 55GB innodb file for the database tests).
>
>
> TEST 1: dd if=/dev/sda of=/dev/null bs=1M
>
> kernel speed swap used
>
> 2.6.26 111MB/s 500kB
> -mm 110MB/s 59MB (ouch, system noticably slower)
> noforce 111MB/s 128kB
> stream 108MB/s 0 (slight regression, not sure why yet)
>
> This patch shows that the split LRU VM in -mm has a problem
> with large streaming IOs: the working set gets pushed out of
> memory, which makes doing anything else during the big streaming
> IO kind of painful.
>
> However, either of the two patches posted fixes that problem,
> though at a slight performance penalty for the "stream" patch.
Btw, my desktop machine runs -mm (+ the patch I have posted later in
this thread) for over a week now and I have not yet encountered any
notable regressions in normal usage patterns.
I have not collected hard numbers but just tried to work normally with
it.
I also employed a massive memory eater (besides emacs and firefox) that
spawns children that eat, serialized, ~120% of RAM each.
Continuing normal work on both kernels was a bit harder, sure, but not
impossible.
The box never died on me nor did it thrash perceivably harder/longer
near oom than .26. The oom killer was never invoked.
Hannes
--
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:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2008-07-29 13:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 2:25 Rik van Riel
2008-07-28 14:57 ` Rik van Riel
2008-07-28 15:30 ` Ray Lee
2008-07-28 23:41 ` Andrew Morton
2008-07-28 23:57 ` Rik van Riel
2008-07-29 0:03 ` Rik van Riel
2008-07-29 0:17 ` Andrew Morton
2008-07-29 0:31 ` Rik van Riel
2008-07-29 0:46 ` Lee Schermerhorn
2008-07-29 13:21 ` Johannes Weiner
2008-07-29 13:28 ` Rik van Riel
2008-07-29 13:04 ` KOSAKI Motohiro
2008-07-29 13:16 ` Rik van Riel
2008-07-29 13:51 ` Johannes Weiner [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=87tze84x4b.fsf@saeurebad.de \
--to=hannes@saeurebad.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
/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