🚀 go-pugleaf

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.