All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: lyndat3@your-mail.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: file xfer over NFSv4 with 'sync' ~300X slower than with 'async' ?
Date: Wed, 1 Apr 2015 14:51:46 -0400	[thread overview]
Message-ID: <20150401185146.GE3040@fieldses.org> (raw)
In-Reply-To: <1427911337.1794160.248190485.1F161545@webmail.messagingengine.com>

On Wed, Apr 01, 2015 at 11:02:17AM -0700, lyndat3@your-mail.com wrote:
> > There's no maximum sync/async ratio.  You could make that ratio lower or
> > higher by varying dd's block size, for example.
> > 
> > The way I'd look at it, your dd of a 100MB file above is doing 3072
> > writes, and taking about 8*60/3072 =~ .16 seconds per write.
> > 
> > That does sound high.  Things to look at to understand why might include
> > the round-trip ping time to the server, and the time for the server's
> > disk to do a synchronous write.
> > 
> 
> After comments from one of the nfs client maintainers, it turns out the slowness issue is simply one of not-quite-MIS-configuration.
> 
> As helpfully commented here
> 
>   http://serverfault.com/questions/499174/etc-exports-mount-option/500553#500553
> 
> , IIUC there are two *separate* syncs to consider -- at the server, and at the client.
> 
> 'sync' on the EXPORT, and 'async' on the MOUNT is the sane approach; That config also appears to return the performance.
> 
> The many recommendations online to use 'sync' for data integrity are IIUC for sync on the server.

Yes.  This is a common source of confusion.  In retrospect maybe the
export sync/async option should have had a different name from the
client mount option.--b.

> With 'async' set on the moount, and 'sync' on the exports, It appears integrity of writes is properly assured and I've got rsync-over-NFSv4 performance back in the ~30-60 MB/s range.
> 
> LT 

  reply	other threads:[~2015-04-01 18:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 21:44 large data transfer rate slowdows over NFSv4 local lan with kernel 3.19x & 3.16x ? lyndat3
2015-03-31 14:21 ` file xfer over NFSv4 with 'sync' ~300X slower than with 'async' ? lyndat3
2015-04-01 17:54   ` J. Bruce Fields
2015-04-01 18:02     ` lyndat3
2015-04-01 18:51       ` J. Bruce Fields [this message]
2015-04-01 18:59         ` Trond Myklebust
2015-04-01 19:04           ` lyndat3
2015-04-01 19:56             ` J. Bruce Fields
2015-04-01 20:02               ` Trond Myklebust
2015-04-01 20:24               ` lyndat3
2015-04-01 19:50           ` J. Bruce Fields

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=20150401185146.GE3040@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=lyndat3@your-mail.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 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.