From: bpm@sgi.com
To: Tristan Ball <tristanb@pronto.com.au>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFS Sync with External Journal
Date: Wed, 8 Jun 2011 13:08:49 -0500 [thread overview]
Message-ID: <20110608180849.GI26107@sgi.com> (raw)
In-Reply-To: <3FA034197108F04082D2AE1401CE0F3832A9B34E@VICMAILBOX.pronto.com.au>
Hey Tristan,
On Mon, Jun 06, 2011 at 01:42:39PM +0000, Tristan Ball wrote:
> I've been experimenting with using an external ext3 journal as a way
> to bring the write performance of an NFS share exported with the the
> 'sync' option closer to that of one exported with 'async'.
>
> I've mounted the ext3 filesystem with data=journal, and the journal
> itself is on SSD. I've seen various references on the net saying that
> this should improve performance, as the nfs process can respond to
> write requests as soon as the data is in journal, rather than flushed
> all the way to the filesystem
There was some work done for xfs awhile back with a similar issue in
mind. Once metadata are in the xfs journal the nfs server can respond
to requests without waiting for it to be flushed to its final place on
disk. We're using the commit_metadata export_operation to do that.
But XFS won't do that for the data itself. We rely on multiple spindles
to improve performance there.
Regards,
Ben
prev parent reply other threads:[~2011-06-08 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 13:42 NFS Sync with External Journal Tristan Ball
2011-06-06 20:12 ` Wendy Cheng
2011-06-07 23:23 ` J. Bruce Fields
2011-06-08 3:57 ` Tristan Ball
2011-06-08 17:33 ` Wendy Cheng
2011-06-08 18:08 ` bpm [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=20110608180849.GI26107@sgi.com \
--to=bpm@sgi.com \
--cc=linux-nfs@vger.kernel.org \
--cc=tristanb@pronto.com.au \
/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;
as well as URLs for NNTP newsgroup(s).