Article View: comp.client-server
Article #192Re: NFS and RPC
From: Tad Marshall
Date: Thu, 07 Jan 1993 03:05
Date: Thu, 07 Jan 1993 03:05
18 lines
1347 bytes
1347 bytes
In article <1992Dec30.155939.13344@spectrum.xerox.com> weltman@adoc.xerox.com writes: > > 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. > >Why is NFS so slow? NFS is "stateless", which means that each "write" from the client side will result in an open/write/close on the server. The opens/closes slow it down quite a bit over the file-transfers you were comparing it to. -- Tad
Technical Details
Message-ID:
<1ig6ltINNe2d@shelley.u.washington.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!olivea!spool.mu.edu!uwm.edu!ogicse!news.u.washington.edu!tadReferences:
<1992Dec30.155939.13344@spectrum.xerox.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!spool.mu.edu!uwm.edu!ogicse!news.u.washington.edu!tad From: tad@wrq.com (Tad Marshall) Newsgroups: comp.client-server Subject: Re: NFS and RPC Keywords: NFS,RPC Message-ID: <1ig6ltINNe2d@shelley.u.washington.edu> Date: 7 Jan 93 03:05:33 GMT References: <1992Dec30.155939.13344@spectrum.xerox.com> Organization: Walker Richer & Quinn, Inc., Seattle, WA Lines: 18 NNTP-Posting-Host: elmer.wrq.com