On Thu, 2008-01-24 at 19:19 -0600, Dan Farrell wrote: [...] > and as the client (from `mount`): > > nfs:/mnt/storage on /home/media/storage type > nfs(rw,rsize=65536,wsize=65536,soft,timeo=300,addr=192.168.1.88) > > /etc/fstab on the client looks like: > > nfs:/mnt/storage /home/media/storage nfs > rsize=65536,wsize=65536,rw,async,soft,timeo=300 0 0 > > > Of these options, rsize,wsize,and async are reputed to effect > performance. However, I do not see much of an effect between different > rsize and wsize settings. I believe that over an uncongested 100T > network it probably doesn't matter too much what rsize and wsize are. > On a different share (same server) mounted async without [r|w]size set, > performance (write, this time) was 11.2mb/s, roughly the same. > Furthermore, I'm not sure these values are even valid. > http://www.linuxdocs.org/HOWTOs/NFS-HOWTO/performance.html said that > nfs3 goes only to 32768. [...]
As far as I remember, rsize and wsize are negotiated between client and server. Those mount options just set an upper limit which is certainly not what you want. I'm even wondering that those settings are accepted at all! Normally, unsigned 16bit integer has a range from 0 to 65535. If you ask me, that's an off-by-one error just waiting to happen...
signature.asc
Description: This is a digitally signed message part
