From: Wendy Cheng <s.wendy.cheng@gmail.com>
To: Benny Halevy <bhalevy@panasas.com>
Cc: Frank Steiner
<fsteiner-mail1-G0GEQqhI7DhYiKXMg8wJIg@public.gmane.org>,
nfs@lists.sourceforge.net
Subject: Re: [NFS] Does "sync" cause the FUA bit to be set?
Date: Tue, 10 Jun 2008 13:52:08 -0500 [thread overview]
Message-ID: <484ECD58.8040100@gmail.com> (raw)
In-Reply-To: <484EA215.5090000@panasas.com>
Benny Halevy wrote:
> On Jun. 10, 2008, 18:44 +0300, Wendy Cheng <s.wendy.cheng@gmail.com> wrote:
>
>> Frank Steiner wrote:
>>
>>> With the profile ignoring the FUA bit, copying or deleting directories
>>> of e.g. 10M with a about 1000 files is factor 5 faster than with the
>>> profile honoring the FUA bit.
>>>
>>>
>> FUA bit is normally combined with write-thru scsi command that bypasses
>> storage write cache. I would imagine it needs to well synchronize
>> various pieces before issuing this command. It could hurt the
>> performance if not done well, particularly for meta data. So your result
>> is not surprising.
>>
>>> We export with the "sync" option. Does that option maybe set the FUA bit
>>> for all write operations on the NFS server?
>>>
>>>
>> It depends on how the filesystem (and its associated disk subsystem) is
>> implemented. The "sync" export option itself has a heavy performance
>> impact, regardless how FUA bit is handled. Some vendors uses specialized
>> HW (e.g. NVRAM) to alleviate this performance hit. If your filesystem
>> doesn't have this type of support, you should expect "sync" option runs
>> much much slower than "async". It is a choice (or balance) between cost,
>> performance, and data reliability.
>>
>
> Wendy, I *think* what you have in mind is the sync mount option
> rather than the sync export flag. The latter just tells the server
> not to cheat and do everything asynchronously. It should *not*
> have a heavy performance penalty for I/O intensive writes if the
> client is using async writes and commits.
>
>
No, I didn't get confused ... We can use Linux as an example :) .. check
out:
http://marc.info/?l=linux-nfs&m=119618886105337&w=2
-- quote
The default export might have been "async", but unless the option "sync"
in /etc/exports was being ignored I was already using "sync". Nevertheless
I will try to change to async and test if it makes a difference.
(one day later: )
I have now tried it and the load on the NFS server is much lower and KDE
logins seem to be reasonably fast now.
-- un-quote
-- Wendy
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2008-06-10 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 10:43 [NFS] Does "sync" cause the FUA bit to be set? Frank Steiner
[not found] ` <484E5AC1.3020200-G0GEQqhI7DhYiKXMg8wJIg@public.gmane.org>
2008-06-10 11:53 ` Benny Halevy
2008-06-10 15:44 ` Wendy Cheng
[not found] ` <484EA215.5090000@panasas.com>
2008-06-10 18:52 ` Wendy Cheng [this message]
2008-06-10 19:47 ` J. Bruce Fields
[not found] ` <484EC317.8090801@panasas.com>
2008-06-10 22:58 ` Wendy Cheng
2008-06-16 13:06 ` Frank Steiner
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=484ECD58.8040100@gmail.com \
--to=s.wendy.cheng@gmail.com \
--cc=bhalevy@panasas.com \
--cc=fsteiner-mail1-G0GEQqhI7DhYiKXMg8wJIg@public.gmane.org \
--cc=nfs@lists.sourceforge.net \
/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.