[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0705031740470.15240@schroedinger.engr.sgi.com>
Date: Thu, 3 May 2007 17:44:19 -0700 (PDT)
From: Christoph Lameter <clameter@....com>
To: "Chen, Tim C" <tim.c.chen@...el.com>
cc: Tim Chen <tim.c.chen@...ux.intel.com>,
"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
"Zhang, Yanmin" <yanmin.zhang@...el.com>,
"Wang, Peter Xihong" <peter.xihong.wang@...el.com>,
Arjan van de Ven <arjan@...radead.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: RE: Regression with SLUB on Netperf and Volanomark
On Thu, 3 May 2007, Chen, Tim C wrote:
> We are still seeing a 5% regression on TCP streaming with
> slub_min_objects set at 16 and a 10% regression for Volanomark, after
> increasing slub_min_objects to 16 and setting slub_max_order=4 and using
> the 2.6.21-rc7-mm2 kernel. The performance between slub_min_objects=8
> and 16 are similar.
Ok. We then need to look at partial list management. It could be that the
sequence of partials is reversed. The problem is that I do not really
have time to concentrate on performance right now. Stability comes
first. We will likely end up putting some probes in there to find out
where the overhead comes from.
> > Check slabinfo output for the network slabs and see what order is
> > used. The number of objects per slab is important for performance.
>
> The order used is 0 for the buffer_head, which is the most used object.
>
> I think they are 104 bytes per object.
Hmmm.... Then it was not affected by slab_max_order? Try
slab_min_order=1 or 2 to increase that?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists