From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: Chuck Lever <chuck.lever@oracle.com>, NeilBrown <neilb@suse.de>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Use of READDIRPLUS on large directories
Date: Wed, 16 Mar 2011 10:20:03 -0400 [thread overview]
Message-ID: <1300285203.16266.46.camel@lade.trondhjem.org> (raw)
In-Reply-To: <4D80C5C6.2060003@netapp.com>
On Wed, 2011-03-16 at 10:14 -0400, Bryan Schumaker wrote:
> I guess I misunderstood what to publish test results for? I know I included numbers on one of the patches (commit 82f2e5472e2304e531c2fa85e457f4a71070044e, copied below)... I'll find the numbers you're asking about and post them.
>
> -Bryan
>
> commit 82f2e5472e2304e531c2fa85e457f4a71070044e
> Author: Bryan Schumaker <bjschuma@netapp.com>
> Date: Thu Oct 21 16:33:18 2010 -0400
>
> NFS: Readdir plus in v4
>
> By requsting more attributes during a readdir, we can mimic the readdir plus
> operation that was in NFSv3.
>
> To test, I ran the command `ls -lU --color=none` on directories with various
> numbers of files. Without readdir plus, I see this:
>
> n files | 100 | 1,000 | 10,000 | 100,000 | 1,000,000
> --------+-----------+-----------+-----------+-----------+----------
> real | 0m00.153s | 0m00.589s | 0m05.601s | 0m56.691s | 9m59.128s
> user | 0m00.007s | 0m00.007s | 0m00.077s | 0m00.703s | 0m06.800s
> sys | 0m00.010s | 0m00.070s | 0m00.633s | 0m06.423s | 1m10.005s
> access | 3 | 1 | 1 | 4 | 31
> getattr | 2 | 1 | 1 | 1 | 1
> lookup | 104 | 1,003 | 10,003 | 100,003 | 1,000,003
> readdir | 2 | 16 | 158 | 1,575 | 15,749
> total | 111 | 1,021 | 10,163 | 101,583 | 1,015,784
>
> With readdir plus enabled, I see this:
>
> n files | 100 | 1,000 | 10,000 | 100,000 | 1,000,000
> --------+-----------+-----------+-----------+-----------+----------
> real | 0m00.115s | 0m00.206s | 0m01.079s | 0m12.521s | 2m07.528s
> user | 0m00.003s | 0m00.003s | 0m00.040s | 0m00.290s | 0m03.296s
> sys | 0m00.007s | 0m00.020s | 0m00.120s | 0m01.357s | 0m17.556s
> access | 3 | 1 | 1 | 1 | 7
> getattr | 2 | 1 | 1 | 1 | 1
> lookup | 4 | 3 | 3 | 3 | 3
> readdir | 6 | 62 | 630 | 6,300 | 62,993
> total | 15 | 67 | 635 | 6,305 | 63,004
>
> Readdir plus disabled has about a 16x increase in the number of rpc calls an
> is 4 - 5 times slower on large directories.
Right. Those are the numbers that convinced me...
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-03-16 14: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 [this message]
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
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=1300285203.16266.46.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=bjschuma@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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).