All of lore.kernel.org
 help / color / mirror / Atom feed
From: Malahal Naineni <malahal@us.ibm.com>
To: Cedric Blancher <cedric.blancher@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Tuning Linux NFSv4 for high latency connections?
Date: Wed, 23 Apr 2014 16:15:18 -0500	[thread overview]
Message-ID: <20140423211518.GA16506@us.ibm.com> (raw)
In-Reply-To: <CALXu0UdbSHfFM+tq2_zssMhiwZ1qMJdieNdvwtxz6k31CMWAUA@mail.gmail.com>

Cedric Blancher [cedric.blancher@gmail.com] wrote:
> On 23 April 2014 22:44, Malahal Naineni <malahal@us.ibm.com> wrote:
> > Cedric Blancher [cedric.blancher@gmail.com] wrote:
> >> On 23 April 2014 22:24, Malahal Naineni <malahal@us.ibm.com> wrote:
> >> > Cedric Blancher [cedric.blancher@gmail.com] wrote:
> >> >> Are there any options to improve the Linux NFSv4 performance over a
> >> >> high latency connection?
> >> >>
> >> >> We currently use Solaris/Illumos as NFSv4 server and client over a
> >> >> cross continental Internet connection. Latency is terrible (~220ms)
> >> >> but the counter this by running work in parallel so the latency is
> >> >> mostly mitigated.
> >> >>
> >> >> We now wish to migrate (short: Away from Oracle because support is
> >> >> basically unbearable) to Linux (tested SuSE 13.1 and current Fedora)
> >> >> and build times are 17 times (!!!) SLOWER than on Solaris/Illumos.
> >> >>
> >> >> Are there any tunables besides actimeo=300?
> >> >
> >> > rsize and wsize may help! You need to figure out if the read is the
> >> > issue or the write before you dig further.
> >>
> >> I already tried to tune rsize/wsize, making them both smaller or the
> >> maximum of 1048576 bytes, with no effect.
> >>
> >> One possible theory is that maybe something in Linux doesn't allow
> >> multiple requests to be issued in parallel and waits for each request
> >> to be completed before issuing the next one?
> >
> > Linux NFS client can issue I/Os in parallel. Should be limited by number
> > of RPC slots though.
> 
> What controls the number of RPC slots? is there a tunable? Is there
> something to monitor the usage?

sysctl sunrpc.tcp_slot_table_entries (if you are using tcp)

Also, mountstats <mount-point> would be very helpful.

Regards, Malahal.


  reply	other threads:[~2014-04-23 21:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 18:01 Tuning Linux NFSv4 for high latency connections? Cedric Blancher
2014-04-23 20:24 ` Malahal Naineni
2014-04-23 20:30   ` Cedric Blancher
2014-04-23 20:44     ` Malahal Naineni
2014-04-23 21:04       ` Cedric Blancher
2014-04-23 21:15         ` Malahal Naineni [this message]
2014-04-23 22:14           ` Cedric Blancher
2014-04-23 22:57             ` Malahal Naineni
2014-04-24  3:12 ` Jim Rees
2014-04-24 17:22   ` Cedric Blancher
2014-04-28  5:23     ` Dean
2014-04-28 10:35       ` Jim Rees

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=20140423211518.GA16506@us.ibm.com \
    --to=malahal@us.ibm.com \
    --cc=cedric.blancher@gmail.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.