home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!rutgers!rochester!rocksanne!news
- From: weltman@adoc.xerox.com (Rob Weltman)
- Newsgroups: comp.client-server
- Subject: NFS and RPC
- Keywords: NFS,RPC
- Message-ID: <1992Dec30.155939.13344@spectrum.xerox.com>
- Date: 30 Dec 92 15:59:39 GMT
- Sender: news@spectrum.xerox.com
- Reply-To: weltman@adoc.xerox.com
- Organization: Xerox PARC, Palo Alto, CA
- Lines: 43
-
-
- Why is NFS so slow?
- -------------------
-
- I followed the initial discussion in this group about RPC, TCP, and
- UDP with great interest. At about the same time, a friend did a series
- of benchmarks in a network of Sparcstation 2's, to compare the file
- transfer performance using TCP sockets, NFS (write to remote-mounted
- disk), and RPC using TCP. The files were large (around 2 MB or larger).
- RPC using TCP was slightly slower than straight sockets using TCP, as
- expected. What was surprising was that it was so slow to just do a
- large write to the open file descriptor of a remote mounted file.
-
- It turned out to be much faster to:
-
- - have a small server process on the remote machine open a file there
- - transfer the file to the remote process with RPC or socket
- - have the remote process write to the file
-
- Some improvement over the open/write to the remote file was obtained
- by mmapping the remote file instead, but this is still slower than using
- the remote process.
-
- Can NFS be tweaked for better performance? Are there other settings
- that affect NFS performance this drastically?
-
- Thanks for any clues!
-
- Rob
-
-
-
- ---
-
- ---------------------------------------------
- | Rob Weltman |
- | Xerox |
- | 3400 Hillview Ave, building 5 |
- | Palo Alto, CA 94303 |
- | |
- | weltman@adoc.xerox.com |
- | phone (415)-813-7477 fax (415)-813-6792 |
- ---------------------------------------------
-