From: Andi Kleen <ak@muc.de>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andi Kleen <ak@muc.de>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Dcache hash distrubition patches
Date: Tue, 11 Mar 2003 16:23:22 +0100 [thread overview]
Message-ID: <20030311152322.GA2358@averell> (raw)
In-Reply-To: <26350000.1047368465@[10.10.2.4]>
On Tue, Mar 11, 2003 at 08:41:07AM +0100, Martin J. Bligh wrote:
> some numbers. They still look pretty good to me. I shrunk us from
> 1,048,576 buckets to 65536, and loaded 1,150,000 entries in there.
Interesting would be to find the sweet spot with the smallest hash table
size that still performs well. Not sure if find / is a good workload
for that though.
Also same for inode hash (but I don't have statistics for that right now)
-Andi
next prev parent reply other threads:[~2003-03-11 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 17:45 Dcache hash distrubition patches Martin J. Bligh
2003-03-10 17:52 ` Andi Kleen
2003-03-11 7:41 ` Martin J. Bligh
2003-03-11 7:47 ` William Lee Irwin III
2003-03-11 15:23 ` Andi Kleen [this message]
2003-03-11 15:31 ` Martin J. Bligh
2003-03-11 16:27 ` Andi Kleen
2003-03-11 17:29 ` Anton Blanchard
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=20030311152322.GA2358@averell \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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