From: Bernd Schubert <bernd-schubert@gmx.de>
To: Undisclosed.Recipients: ;
Cc: Johan Dahlin <jdahlin@async.com.br>, nfs@lists.sourceforge.net
Subject: Re: Performance expectations of NFS
Date: Thu, 25 Jan 2007 23:50:21 +0100 [thread overview]
Message-ID: <200701252350.22255.bernd-schubert@gmx.de> (raw)
In-Reply-To: <20070125193121.GA7267@anthem.async.com.br>
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 syn=
c =
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. =
>
> Now I know that file creation is synchronous, and that because of this,
> the NFS copy will /always/ run significantly slower. But I was amazed at
> just how much faster reading was than writing, and at how fast reading
> actually is -- it's much faster than I expected NFS could be.
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 loo=
k =
at the commit calls, once with sync and once with async option.
> But what I'd really like to know if there is a way of making the
> above operation run in significantly less time than it is today, or if
I guess if one could convince the nfs clients to reduce the number of commi=
t =
calls, write operations would be much much faster. Don't know if that is =
possible at all, though.
Cheers,
Bernd
-- =
Bernd Schubert
PCI / Theoretische Chemie
Universit=E4t Heidelberg
INF 229
69120 Heidelberg
-------------------------------------------------------------------------
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=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-01-25 22:50 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 [this message]
2007-01-26 0:54 ` Christian Robottom Reis
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=200701252350.22255.bernd-schubert@gmx.de \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox