From: NeilBrown <neilb@suse.de>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
Chuck Lever <chuck.lever@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Use of READDIRPLUS on large directories
Date: Tue, 5 Apr 2011 22:20:19 +1000 [thread overview]
Message-ID: <20110405222019.6c4d2997@notabene.brown> (raw)
In-Reply-To: <4D9A26B8.6080504@netapp.com>
On Mon, 04 Apr 2011 16:14:48 -0400 Bryan Schumaker <bjschuma@netapp.com>
wrote:
> I've done some more testing and posted my initial results here: https://wiki.linux-nfs.org/wiki/index.php/Readdir_performance_results. If anybody has suggestions for better ways to organize the data, please let me know. I'll also try to post some graphs in the next couple of days.
I think graphs would certainly help.
Also it might be good to be explicit about the server hardware/config as that
can make a real performance difference.
No bright ideas about how to organise the graphs...
I'd probably try just graphing the 'real' time against kernel version
with one line for each different directory size.
Then you get 16 graphs, 4 different configs (v3/v4 x rddirplus/norddirplus)
and 4 different tests (ls -f, ls -lU, ls -U, rm -r... though I can't see how
"ls -U" is different from "ls -f").
NeilBrown
next prev parent reply other threads:[~2011-04-05 12:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 4:55 Use of READDIRPLUS on large directories NeilBrown
2011-03-16 12:30 ` peter.staubach
2011-03-16 13:50 ` Trond Myklebust
2011-03-16 21:40 ` NeilBrown
2011-03-17 0:55 ` NeilBrown
2011-03-17 17:44 ` J. Bruce Fields
2011-03-18 4:27 ` NeilBrown
2011-03-16 13:43 ` Chuck Lever
2011-03-16 14:14 ` Bryan Schumaker
2011-03-16 14:20 ` Trond Myklebust
2011-03-16 21:30 ` NeilBrown
2011-03-16 21:42 ` Trond Myklebust
2011-03-16 22:40 ` NeilBrown
2011-03-17 17:18 ` J. Bruce Fields
2011-04-04 20:14 ` Bryan Schumaker
2011-04-05 12:20 ` NeilBrown [this message]
2011-04-07 14:28 ` Bryan Schumaker
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=20110405222019.6c4d2997@notabene.brown \
--to=neilb@suse.de \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=bjschuma@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).