All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Legate <jlegate@proxime.net>
To: Aaron Wiebe <epiphani@gmail.com>
Cc: Jason Legate <linux-nfs@proxime.net>, linux-nfs@vger.kernel.org
Subject: Re: NFS for millions of files
Date: Wed, 2 Sep 2009 15:00:31 -0400	[thread overview]
Message-ID: <20090902190031.GG946@proxime.net> (raw)
In-Reply-To: <e7ca40f70909021119r2f49724dj705e334cf1ae9b3a@mail.gmail.com>

It is said that Aaron Wiebe, at Wed, 02 Sep 2009, wrote:

> Have a look at these two kernel params - I'd recommend bumping them up
> to 128 (they're 16 by default).
> 
> sunrpc.tcp_slot_table_entries
> sunrpc.udp_slot_table_entries

They were indeed 16.  I've bumped them up to 128, and am trying again.

> Keep in mind that this could also be a serialization issue.  If you've
> got a 3ms latency, and you're performing all of your opens serially,
> you aren't going to get much faster.  If you do the work in parallel
> you'll likely get substantially better numbers.

It appears it might just be serialization.  When I run more than 1 thread,
I can consistently get between 200 and 250 files/thread/second (up to about
10 threads, at which point I get diminishing returns per thread).

I seem to be doing a lot of GETATTR's, and it appears to be driven by perl.
We are open()'ing files with +>filename and apparently perl will do an fstat
for us after opening.  Thanks for the tip, Aaron!

-j

> -Aaron
> 
> 
> On Wed, Sep 2, 2009 at 2:08 PM, Jason Legate<linux-nfs@proxime.net> wrote:
> > Hi, I'm trying to setup a server that we can create millions of files on over
> > NFS. ?When I run our creation benchmark locally ?I can get around 3000 files/
> > second in the configuration we're using now, but only around 300/second over
> > NFS. ?It's mounted as this:
> >
> > rw,nosuid,nodev,noatime,nodiratime,hard,bg,nointr,rsize=32768,wsize=32768,tcp,
> > nfsvers=3,timeo=600,actimeo=600,nocto
> >
> > When I mount the same FS over localhost instead of across the lan, it performs
> > about full speed (the 3000/sec). ?Anyone have any ideas what I might tweak or
> > look at?
> >
> > We're going to be testing various XFS/LVM configs to get the best performance,
> > but right out the gate, NFS having a 10:1 penalty of performance doesn't bode
> > well.
> >
> > Thanks in advance,
> > Jason
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at ?http://vger.kernel.org/majordomo-info.html
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-09-02 18:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 18:08 NFS for millions of files Jason Legate
2009-09-02 18:19 ` Aaron Wiebe
2009-09-02 18:35   ` Peter Chacko
2009-09-02 19:06     ` Jason Legate
2009-09-02 19:10     ` Aaron Wiebe
2009-09-02 19:27       ` Peter Chacko
2009-09-02 19:00   ` Jason Legate [this message]
2009-09-02 18:37 ` Peter Staubach
2009-09-03 18:15   ` J. Bruce Fields
2009-09-03 18:37     ` Ric Wheeler
2009-09-03 18:54       ` Trond Myklebust
2009-09-03 19:05       ` J. Bruce Fields
2009-09-02 18:38 ` Chuck Lever

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=20090902190031.GG946@proxime.net \
    --to=jlegate@proxime.net \
    --cc=epiphani@gmail.com \
    --cc=linux-nfs@proxime.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.