From: "Jose R. Santos" <jrsantos@austin.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Jose R. Santos" <jrsantos@austin.ibm.com>,
linux-kernel@vger.kernel.org, anton@samba.org, dheger@us.ibm.com,
slpratt@us.ibm.com
Subject: Re: [PATCH] dentry and inode cache hash algorithm performance changes.
Date: Fri, 7 May 2004 08:04:15 -0500 [thread overview]
Message-ID: <20040507130415.GA1537@rx8.ibm.com> (raw)
In-Reply-To: <20040504115510.696184dc.akpm@osdl.org> (from akpm@osdl.org on Tue, May 04, 2004 at 13:55:10 -0500)
On 05/04/04 13:55:10, Andrew Morton wrote:
> > Andrew - Is there any workload you want me to run to show that this hash
> > function is going to be equal or better that the one already provided
> > in Linux?
>
> Not really - it sounds like you've covered it pretty well. Did you try SDET?
>
> It could be that reducing the hash table size will turn pretty much any
> workload into a test of the hash quality.
Sorry for the late reply...
Steve Pratt seem to have a SDET setup already and he did me the favor of
running SDET with a reduce dentry entry hash table size. I belive that
his table suggest that less than 3% change is acceptable variability, but
overall he got a 5% better number using the new hash algorith.
-JRS
=========================================================================
A) x4408way1.sdet.2.6.5100000-8p.04-05-05_12.08.44 vs
B) x4408way1.sdet.2.6.5+hash-100000-8p.04-05-05_11.48.02
<6>Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
<4>Inode-cache hash table entries: 1048576 (order: 10, 4194304 bytes)
Results:Throughput
tolerance = 0.00 + 3.00% of A
A B
Threads Ops/sec Ops/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 4341.9300 4401.9500 1.38 60.02 130.26
2 8242.2000 8165.1200 -0.94 -77.08 247.27
4 15274.4900 15257.1000 -0.11 -17.39 458.23
8 21326.9200 21320.7000 -0.03 -6.22 639.81
16 23056.2100 24282.8000 5.32 1226.59 691.69 *
32 23397.2500 24684.6100 5.50 1287.36 701.92 *
64 23372.7600 23632.6500 1.11 259.89 701.18
128 17009.3900 16651.9600 -2.10 -357.43 510.28
=========================================================================
next prev parent reply other threads:[~2004-05-07 20:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040430191539.GC14271@rx8.ibm.com>
[not found] ` <20040430131832.45be6956.akpm@osdl.org>
2004-04-30 20:57 ` [PATCH] dentry and inode cache hash algorithm performance changes Jose R. Santos
2004-04-30 21:33 ` Jose R. Santos
2004-04-30 22:02 ` Andrew Morton
2004-04-30 23:42 ` Jose R. Santos
2004-05-04 13:12 ` Jose R. Santos
2004-05-04 18:55 ` Andrew Morton
2004-05-07 13:04 ` Jose R. Santos [this message]
2004-05-08 1:03 ` Dave Hansen
2004-04-30 19:55 Jose R. Santos
2004-05-01 12:08 ` Olaf Dietsche
2004-05-01 15:08 ` Jose R. Santos
2004-05-20 13:34 ` Raghavan
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=20040507130415.GA1537@rx8.ibm.com \
--to=jrsantos@austin.ibm.com \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=dheger@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=slpratt@us.ibm.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