From: Christian Robottom Reis <kiko@async.com.br>
To: Bernd Schubert <bernd-schubert@gmx.de>
Cc: , Johan Dahlin <jdahlin@async.com.br>, nfs@lists.sourceforge.net
Subject: Re: Performance expectations of NFS
Date: Thu, 25 Jan 2007 22:54:25 -0200 [thread overview]
Message-ID: <20070126005425.GB29218@anthem.async.com.br> (raw)
In-Reply-To: <200701252350.22255.bernd-schubert@gmx.de>
On Thu, Jan 25, 2007 at 11:50:21PM +0100, Bernd Schubert wrote:
> Hi Christian,
>
> > 0:05 - Server: locally on RAID-5
> > 0:06 - Client: copying from NFS mount to tmpfs
> > 2:31 - Client: Copying from NFS mount to NFS mount
> > (i.e., the simple command above)
> > 3:30 - Client: Copying from NFS mount to NFS mount over an existing
> > tree.
> > 5:08 - Client: Copying from tmpfs to NFS mount
> > 0:48 - Client: Deleting copy of tree on NFS mount
>
> I guess your exports has the "sync" option or your didn't set async or sync
> at all (sync is then the default)? Can you repeat the test again using the
> async option? But please, also read carefully the explanations of "man 5
> exports" about this topic.
This /was/ using the async option. Using sync causes the times to worsen
by about 70% (so the NFS to NFS copy takes about 5 minutes).
> Just for fun, take ethereal and capture some data, once with the async and
> once with the sync option. Now have a look how much time each operation of
> the nfs client takes before it gets confirmed by the server. Especially look
> at the commit calls, once with sync and once with async option.
Yeah, that's a great idea; I should do that tomorrow.
> I guess if one could convince the nfs clients to reduce the number of commit
> calls, write operations would be much much faster. Don't know if that is
> possible at all, though.
I get the feeling that the real bottleneck is synchronous file
creation. What I would like to understand is whether this is done for
reliability or to preserve filesystem semantics.
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-01-26 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 19:31 Performance expectations of NFS Christian Robottom Reis
2007-01-25 22:50 ` Bernd Schubert
2007-01-26 0:54 ` Christian Robottom Reis [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=20070126005425.GB29218@anthem.async.com.br \
--to=kiko@async.com.br \
--cc=bernd-schubert@gmx.de \
--cc=jdahlin@async.com.br \
--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.