All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christopher Smith <csmith@nighthawkrad.net>
Cc: nfs@lists.sourceforge.net
Subject: Re: (More) NFS Performance woes
Date: Thu, 14 Dec 2006 11:03:59 -0500	[thread overview]
Message-ID: <20061214160359.GA11876@fieldses.org> (raw)
In-Reply-To: <45815427.8070805@nighthawkrad.net>

On Fri, Dec 15, 2006 at 12:39:51AM +1100, Christopher Smith wrote:
> The first test is copying a single large file of about 700M from the 
> (client) local disk to the NFS mount.
> The second test is untarring a 700M tarfile from the (client) local disk 
> to the NFS mount (~5000 files).
> 
> Test #1 consistently finishes in about 17 seconds, delivering about 40 
> MiB/s.
> Test #2 consistently finishes in about 85 seconds, delivering about 8 MiB/s

That's about 17ms per file?  Each of those 5000 file creations is a
synchronous operation--the server doesn't respond until it's actually
committed the operation to disk.  I don't really know what expected
numbers are for your hardware, but given that for each file we have to
wait for both the initial creation and the final flush of the data to
disk on close, 17ms doesn't sound too far off.

> For reference, untarring the same tarfile locally on the server machine 
> takes 7-8 seconds (about 80 MiB/s).

Locally there's not the same requirement that stuff be committed to disk
before certain operations can complete.  For all I know it could be
performing that entire operation without touching the disk.

--b.

-------------------------------------------------------------------------
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

  reply	other threads:[~2006-12-14 16:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14 13:39 (More) NFS Performance woes Christopher Smith
2006-12-14 16:03 ` J. Bruce Fields [this message]
2007-01-25 19:37   ` Christian Robottom Reis
2006-12-14 16:07 ` Trond Myklebust

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=20061214160359.GA11876@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=csmith@nighthawkrad.net \
    --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.