That really helped (boosted TPS from 38 to 83 :). Is this option documented or not? I can't find it in the manual...
That option has been around for some time, although it has never seemed to find its way onto the na_options(1) man page, for reasons I'm afraid I don't know. It was just bumped to having a 32K default in the latest 5.3.5 releases. I *think* we really should be documenting that option though. Sorry. It's one of the most celebrated "secret" options we have! :-)
P.S. Still a big problem with NFS2 performance. We have (besides of Solaris) lots of IRIX boxes, and (surprise) if you use automount on IRIX all mounts are NFS2 only...
Really. So IRIX doesn't let you put mount options in its /etc/auto_master entries? That's a little unhip.
The usual drill for NFS mounting when no options are specified, as defined by Sun/Solaris (if you accept Sun/Solaris as a definer here?), is to mount using the highest revision of the NFS protocol available on both the client and the server, and the first connection oriented protocol available (usually TCP), falling back to the first connectionless protocol (usually UDP). So if the IRIX folk were paying any attention to the Solaris folk when they put their implementation together, as long as you have:
filer> options nfs.v3.enable on filer> options nfs.tcp.enable off
set on the filer, you would be in with a fighting chance of getting your 32K/NFSv3/UDP aspirations satisfied, even without specifying any mount options (32K xfer sizes are the default for NFSv3).
Keith