From: Peter Niemayer <niemayer@isg.de>
To: nfs@lists.sourceforge.net
Subject: exported filesystem on loop-device could be much faster if only nfs on the server side...
Date: Thu, 19 Feb 2004 21:33:24 +0100 [thread overview]
Message-ID: <40351D94.8000405@isg.de> (raw)
... would do some more read-ahead. But first: Hi, I'm currently seeing a bizarre
effect with an filesystem on a loop device exported via nfs (v3, kernel 2.6.2):
Another computer, connected via Gigabit-EtherNet, reads a big file. The performance
is not that good, only about 6MB/s, while files that are exported the same way but
are not on a filesystem that resides on a loop device can be read at about 35MB/s.
The server machine has a lot of idle time left in this scenario.
Now comes the funny part: If I start both the copy job on the remote machine reading
the file AND a local "dd if=file_on_loop_fs of=/dev/zero" on the server machine,
the performance increases up to about 30MB/s!
So it seems that a little read-ahead on the server machine can do wonders to the
performance in this case.
Is there any way to configure read-ahead on the server side of NFS?
Any other tip you can give me to get the same performance boost without the
awkward manual start of the bogus "dd" (which certainly spoils some CPU, still) ?
Thanks in advance,
Peter Niemayer
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2004-02-19 20:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40351D94.8000405@isg.de \
--to=niemayer@isg.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 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.