All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Jason Legate <linux-nfs@proxime.net>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS for millions of files
Date: Wed, 02 Sep 2009 14:37:31 -0400	[thread overview]
Message-ID: <4A9EBB6B.4040009@redhat.com> (raw)
In-Reply-To: <20090902180841.GF946@proxime.net>

Jason Legate 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.
> 

Hi.

Please keep in mind that the NFS stable storage requirements are
probably causing a significant slowdown in activities such as this.
All of the files being created over NFS are being flushed to stable
storage, including modified directory contents and inode information,
before the server responds to the client.  All of those local file
creates are simply manipulating in-memory buffers and are not being
flushed to stable storage until some later time.

There really aren't any good solutions, except perhaps, for
utilizing write caching on the server, and I would only recommend
doing that if you have a good solution, from top to bottom in
the file system and storage stack on the server.  Most aren't.

		ps

  parent reply	other threads:[~2009-09-02 18:37 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
2009-09-02 18:37 ` Peter Staubach [this message]
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=4A9EBB6B.4040009@redhat.com \
    --to=staubach@redhat.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.