From: Yusuf Goolamabbas <yusufg@outblaze.com>
To: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Cc: nfs@lists.sourceforge.net, akpm@osdl.org
Subject: Re: Should NFS over loopback be over 10x slower compared to local fs
Date: Tue, 30 Mar 2004 11:04:29 +0800 [thread overview]
Message-ID: <20040330030429.GA26484@outblaze.com> (raw)
In-Reply-To: <m3y8pkdoe5.fsf@merlin.emma.line.org>
> > Hi, I did a postmark run on a local ext3 filesystem (data=writeback) and
> > then compared it with the same filesystem mounted over loopback and then
> > over a 100Mbit switch, I see a dramatic slowdown with postmark numbers
> > of loopback NFS compared to local fs.
>
> Depending on drive speed and write clustering, expect a significant
> slowdown I'm not sure 10x is OK, but it's certainly realistic.
I expected a slowdown, it's just that I felt that 10x was inappropiate.
Curious as to what others get with the same test run on different
OS/hardware
On FreeBSD 4.9-RELEASE on similar hardware, the slowdown is only half
compared to postmark over local softupdate enabled fs.
Also on 2.6.x, NFS over loopback wasn't that much faster than NFS over
100Mbit
> There's an important difference between NFS and local file system, in
> semantics: Once the NFS server has acknowledged the _write_ request, the
> data is on disk. You don't get that sort of guarantee with a local file
> system unless you open with O_SYNC (and I wonder how many bugs
> "not-quite-synchronous" need to be shaken out WRT local file systems
> given the recent fsync() discussion).
Hmm, That's plausible. I did a tiobench run over a local ext3 fs
(data=writeback) and the same run over loopback NFS and the slowdown was
in sequential/random writes though sequential writes was much slower
than random writes
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-03-30 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 4:25 Should NFS over loopback be over 10x slower compared to local fs Yusuf Goolamabbas
[not found] ` <m3y8pkdoe5.fsf@merlin.emma.line.org>
2004-03-30 3:04 ` Yusuf Goolamabbas [this message]
2004-04-05 10:13 ` Matthias Andree
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=20040330030429.GA26484@outblaze.com \
--to=yusufg@outblaze.com \
--cc=akpm@osdl.org \
--cc=ma@dt.e-technik.uni-dortmund.de \
--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