Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!mcvax!ukc!stc!ist!neil
From: neil@ist.UUCP (Neil Todd)
Newsgroups: comp.unix.wizards,comp.unix.questions
Subject: Tuning NFS links
Message-ID: <1482@ist.UUCP>
Date: Fri, 9-Oct-87 04:46:33 EDT
Article-I.D.: ist.1482
Posted: Fri Oct  9 04:46:33 1987
Date-Received: Mon, 12-Oct-87 22:34:45 EDT
Organization: Imperial Software Technology, London
Lines: 30
Keywords: NFS performance admin
Xref: mnetor comp.unix.wizards:4833 comp.unix.questions:4493

I want to tune up my NFS. Specifically - the read/write size, retry
and timeout counts.

The standard advice seems to be ``suck it and see'' (I assume that
translates into U.S. English). This seems most unsatisfactory, there
surely must be a more scientific approach.

Obviously the environment is a major factor, if for example the
principle use of a nfs mounted filesytem is for a database system to
access it data, and it always does read and writes of a standard size
then clearly there is a good starting point. But what about a more mixed
environment ? How could I monitor things, so that as the nature of the
use of the link changes with time I can see, reasonably quickly, whether
I should reconsider the values of [rw]size etc.

Words of wisdom will be much appreciated here. Hopefully the answers
won't include making kernel hacks as the majority of sites don't have
source, but if this is the only way - please say so, at least source
sites can do something then.


Neil Todd

[neil@ist.co.uk		<- preferred
[neil@ist.uucp 
[{backbone}!ukc!ist.co.uk!neil



Disclaimer: Own opinions, not necessarily those of employer etc, etc.