home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.client-server
- Path: sparky!uunet!mcsun!sun4nl!dascnl!bambam!gjm
- From: gjm@dasc.nl (Gijs J. Mos)
- Subject: Re: NFS and RPC
- Message-ID: <gjm.726403310@bambam>
- Keywords: NFS,RPC
- Organization: Data Sciences B.V.
- References: <1992Dec30.155939.13344@spectrum.xerox.com> <1ig6ltINNe2d@shelley.u.washington.edu> <16274@auspex-gw.auspex.com>
- Date: Thu, 7 Jan 1993 10:41:50 GMT
- Lines: 24
-
- guy@Auspex.COM (Guy Harris) writes:
-
- >>NFS is "stateless",
-
- >True (modulo debate about the meaning of "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.
-
- >False, at least in the UNIX NFS servers I've seen. In those, there
- >aren't any "open"s or "close"s done by the NFS server. Instead, the NFS
- [stuff describing UNIX implementations deleted]
-
- On Stratus NFS the NFS server regularly opens the file. This is indeed a very
- slow operation that involves directory access. To make things usable the
- NFS server doesn't close files immediately after each write or read. Instead
- the files are kept open for a certain period. The time files are kept open is
- an installation parameter for the NFS server. It is normally 30 seconds
- or so. This means that a write/read benchmark that writes/reads a stream
- of blocks as fast as it can incurs only one open.
-
- Gijs Mos
- gjm@dasc.nl
- #include <stddisclaimer.h> This might not be the view of my employer.
-