linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Ray Lee" <ray-lk@madrabbit.org>
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: Mon, 28 Jul 2008 08:30:34 -0700	[thread overview]
Message-ID: <2c0942db0807280830n621922vdb5e9fdb6c66d48f@mail.gmail.com> (raw)
In-Reply-To: <20080728105742.50d6514e@cuia.bos.redhat.com>

On Mon, Jul 28, 2008 at 7:57 AM, Rik van Riel <riel@redhat.com> wrote:
> On Thu, 24 Jul 2008 22:25:10 -0400
> Rik van Riel <riel@redhat.com> wrote:
>
>>   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.
>
> OK, the throughput number with this test turns out not to mean
> nearly as much as I thought.
>
> Switching off CPU frequency scaling, pinning the CPUs at the
> highest speed, resulted in a throughput of only 102MB/s.
>
> My suspicion is that faster running code on the CPU results
> in IOs being sent down to the device faster, resulting in
> smaller IOs and lower throughput.

Or the IOs are getting sent in a different order, and so
coalescing/merging isn't occurring as often. Getting some
instrumentation (something as simple as a histogram) on the IO sizes
could be useful.

--
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>

  reply	other threads:[~2008-07-28 15:30 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 [this message]
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

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=2c0942db0807280830n621922vdb5e9fdb6c66d48f@mail.gmail.com \
    --to=ray-lk@madrabbit.org \
    --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