All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Edmunds <kae@midnighthax.com>
To: linux-nfs@vger.kernel.org
Subject: NFS access slow
Date: Tue, 18 Dec 2012 15:52:48 +0000	[thread overview]
Message-ID: <20121218155248.49dfa1fd@kae.tiger-computing.wbp> (raw)

Accessing disks locally on a server gives read speeds around 100MB/s,
write speeds around 267MB/s.

Mounting the same disks on the same server via NFS (ie, not using the
network at all) gives read speeds around 30MB/s, write speeds around
80MB/s.

That's about 30% of the local access speed.

Is that to be expected? I'd expect a 10-15% slowdown, but not this much.

This is using NFSv4; using NFSv3 improves the speeds slightly (36MB/s
read, 95MB/s write).

Other parameters we've changed, none of which have a significant impact:

 - UDP/TCP
 - rsize and wsize
 - noatime
 - noacl
 - nocto

If that's an unexpected slow down, where should we be looking?

Thanks.

             reply	other threads:[~2012-12-18 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18 15:52 Keith Edmunds [this message]
2012-12-18 18:50 ` NFS access slow J. Bruce Fields
2012-12-18 19:42   ` Keith Edmunds
2012-12-18 20:34     ` Jim Rees
2012-12-18 20:37     ` 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=20121218155248.49dfa1fd@kae.tiger-computing.wbp \
    --to=kae@midnighthax.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 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.