From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Rik van Riel <riel@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ulrich Drepper <drepper@redhat.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory
Date: Sat, 05 May 2007 09:49:26 +1000 [thread overview]
Message-ID: <463BC686.70901@yahoo.com.au> (raw)
In-Reply-To: <463B1FF6.1030904@redhat.com>
Rik van Riel wrote:
> Nick Piggin wrote:
>
>> Rik van Riel wrote:
>>
>>> With lazy freeing of anonymous pages through MADV_FREE, performance of
>>> the MySQL sysbench workload more than doubles on my quad-core system.
>>
>>
>> OK, I've run some tests on a 16 core Opteron system, both sysbench with
>> MySQL 5.33 (set up as described in the freebsd vs linux page), and with
>> ebizzy.
>>
>> What I found is that, on this system, MADV_FREE performance improvement
>> was in the noise when you look at it on top of the MADV_DONTNEED glibc
>> and down_read(mmap_sem) patch in sysbench.
>
>
> Interesting, very different results from my system.
>
> First, did you run with the properly TLB batched version of
> the MADV_FREE patch? And did you make sure that MADV_FREE
> takes the mmap_sem for reading? Without that, I did see
> a similar thing to what you saw...
Yes and yes (I initially forgot to add MADV_FREE to the down_read
case and saw horrible performance!)
> Secondly, I'll have to try some test runs one of the larger
> systems in the lab.
>
> Maybe the results from my quad core Intel system are not
> typical; maybe the results from your 16 core Opteron are
> not typical. Either way, I want to find out :)
Yep. We might have something like that here, and I'll try with
some other architectures as well next week, if I can get glibc
built.
--
SUSE Labs, Novell Inc.
--
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>
next prev parent reply other threads:[~2007-05-04 23:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 4:43 Rik van Riel
2007-05-04 10:53 ` Nick Piggin
2007-05-04 11:58 ` Rik van Riel
2007-05-04 23:49 ` Nick Piggin [this message]
2007-05-04 16:04 ` Ulrich Drepper
2007-05-04 23:47 ` Nick Piggin
2007-05-05 0:10 ` Ulrich Drepper
2007-05-06 22:43 ` Rik van Riel
2007-05-07 2:42 ` Ulrich Drepper
2007-05-07 4:56 ` Rik van Riel
2007-05-07 4:53 ` Ulrich Drepper
2007-05-07 16:51 ` Rik van Riel
2007-05-08 6:12 ` Nick Piggin
2007-05-08 14:59 ` Rik van Riel
2007-05-08 23:23 ` Nick Piggin
2007-05-08 18:35 ` Jakub Jelinek
2007-05-08 23:43 ` Nick Piggin
2007-05-08 3:51 ` [PATCH] stub MADV_FREE implementation Rik van Riel
2007-05-08 23:05 ` Andrew Morton
2007-05-09 17:15 ` Ulrich Drepper
2007-05-09 16:38 ` [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory Hugh Dickins
2007-05-29 16:59 ` Rik van Riel
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=463BC686.70901@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.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