[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081007231851.3B88.KOSAKI.MOTOHIRO@jp.fujitsu.com>
Date: Tue, 7 Oct 2008 23:26:54 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: Rik van Riel <riel@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Lee Schermerhorn <Lee.Schermerhorn@...com>
Cc: kosaki.motohiro@...fujitsu.com,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
netdev@...r.kernel.org, trond.myklebust@....uio.no,
Daniel Lezcano <dlezcano@...ibm.com>,
Pekka Enberg <penberg@...helsinki.fi>,
Neil Brown <neilb@...e.de>, David Miller <davem@...emloft.net>
Subject: split-lru performance mesurement part2
Hi
> yup,
> I know many people want to other benchmark result too.
> I'll try to mesure other bench at next week.
I ran another benchmark today.
I choice dbench because dbench is one of most famous and real workload like i/o benchmark.
% dbench client.txt 4000
mainline: Throughput 13.4231 MB/sec 4000 clients 4000 procs max_latency=1421988.159 ms
mmotm(*): Throughput 7.0354 MB/sec 4000 clients 4000 procs max_latency=2369213.380 ms
(*) mmotm 2/Oct + Hugh's recently slub fix
Wow!
mmotm is slower than mainline largely (about half performance).
Therefore, I mesured it on "mainline + split-lru(only)" build.
mainline + split-lru(only): Throughput 14.4062 MB/sec 4000 clients 4000 procs max_latency=1152231.896 ms
OK!
split-lru outperform mainline from viewpoint of both throughput and latency :)
However, I don't understand why this regression happend.
Do you have any suggestion?
--
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