public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Ted Carpenter <ted@qumulo.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Collapsing I/O size with unstable writes with NFSv3 on 4.15
Date: Mon, 25 Mar 2019 19:13:51 -0400	[thread overview]
Message-ID: <20190325231351.GA23190@fieldses.org> (raw)
In-Reply-To: <CABu8kFdbzgEnoWh595+ODPt4cTaWryO9OR9fKVB68z+tfbNaCA@mail.gmail.com>

On Wed, Mar 20, 2019 at 08:47:32AM -0700, Ted Carpenter wrote:
> I'm testing performance of a clustered NFS server using a 4.15 client.
> My test setup involves running IOZone to write a 30GB file to the
> server over NFSv3. The issue is that we occasionally see bad
> performance, especially when unstable writes are enabled on the
> server.

Which server, and how do you enable unstable writes?

> Based on observing the network traffic, we've seen the write I/O size
> during good runs stay around 1MB (which is how we've mounted) but in
> the bad runs we see often see dips in write size (down to even 4KB or
> 8KB) towards the end of the test.
> 
> I'm trying to understand why we see the dip in I/O size from the NFS
> client as it seems to be related to the decrease in performance. Any
> ideas what could cause it? Also, any suggestions on where I should
> look to start learning about the way the Linux NFS client and page
> cache handle unstable writes internally?

I'm not sure what to recommend.  We might also need some more details
about the performance results you're seeing.

--b.

      reply	other threads:[~2019-03-25 23:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 15:47 Collapsing I/O size with unstable writes with NFSv3 on 4.15 Ted Carpenter
2019-03-25 23:13 ` J. Bruce Fields [this message]

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=20190325231351.GA23190@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=ted@qumulo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox