From: Christoph Lameter <cl@linux.com>
To: Glauber Costa <glommer@parallels.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Pekka Enberg <penberg@kernel.org>,
Suleiman Souhlal <suleiman@google.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: object allocation benchmark
Date: Thu, 22 Mar 2012 11:15:07 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1203221113530.25011@router.home> (raw)
In-Reply-To: <4F6B3591.10003@parallels.com>
On Thu, 22 Mar 2012, Glauber Costa wrote:
> On 03/19/2012 07:28 PM, Christoph Lameter wrote:
> > On Mon, 19 Mar 2012, Glauber Costa wrote:
> >
> > > I was wondering: Which benchmark would be considered the canonical one to
> > > demonstrate the speed of the slub/slab after changes? In particular, I
> > > have
> > > the kmem-memcg in mind
> >
> > I have some in kernel benchmarking tools for page allocator and slab
> > allocators. But they are not really clean patches.
> >
> >
> I'd given it a try.
>
> So in general, Suleiman patches perform fine against bare slab, the
> differences being in the order of ~ 1%. There are some spikes a little bit
> above that, that would deserve more analysis.
>
> However, reason I decided to report early, is this test:
> "1 alloc N free test". It is quite erratic. memcg+kmem sometimes performs 15 %
> worse, sometimes 30 % better... Always right after a cold boot.
>
> I was wondering if you usually see such behavior for this test, and has some
> tips on the setup in case I'm doing anything wrong ?
Well some of these tests are sensitive to memory fragmentation in the page
allocator and slab allocator. One approach is to do these tests
immediately after boot with minimal user space bringup.
The other is to run a stress tests for an predefined period to get memory
into a sufficiently fragmented state and then run the test.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-03-22 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 14:33 Glauber Costa
2012-03-19 15:28 ` Christoph Lameter
2012-03-19 20:41 ` David Rientjes
2012-05-09 6:24 ` Pekka Enberg
2012-05-09 22:24 ` David Rientjes
2012-03-22 14:22 ` Glauber Costa
2012-03-22 16:15 ` Christoph Lameter [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=alpine.DEB.2.00.1203221113530.25011@router.home \
--to=cl@linux.com \
--cc=glommer@parallels.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=suleiman@google.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