1 |
On Sat, 2008-01-26 at 10:29 +0000, Stroller wrote: |
2 |
> On 25 Jan 2008, at 22:40, Florian Philipp wrote: |
3 |
> > On Thu, 2008-01-24 at 19:19 -0600, Dan Farrell wrote: |
4 |
> > |
5 |
> > [...] |
6 |
> >> and as the client (from `mount`): |
7 |
> >> |
8 |
> >> nfs:/mnt/storage on /home/media/storage type |
9 |
> >> nfs(rw,rsize=65536,wsize=65536,soft,timeo=300,addr=192.168.1.88) |
10 |
> >> |
11 |
> >> /etc/fstab on the client looks like: |
12 |
> >> |
13 |
> >> nfs:/mnt/storage /home/media/storage nfs |
14 |
> >> rsize=65536,wsize=65536,rw,async,soft,timeo=300 0 0 |
15 |
> >> |
16 |
> >> |
17 |
> >> Of these options, rsize,wsize,and async are reputed to effect |
18 |
> >> performance. ... |
19 |
> > [...] |
20 |
> > |
21 |
> > As far as I remember, rsize and wsize are negotiated between client |
22 |
> > and |
23 |
> > server. Those mount options just set an upper limit which is certainly |
24 |
> > not what you want. I'm even wondering that those settings are accepted |
25 |
> > at all! Normally, unsigned 16bit integer has a range from 0 to |
26 |
> > 65535. If |
27 |
> > you ask me, that's an off-by-one error just waiting to happen... |
28 |
> |
29 |
> This seems to suggest that 32768 is the largest figure that can be |
30 |
> specified for rsize,wsize: |
31 |
> http://www.mythtv.org/wiki/index.php/ |
32 |
> Optimizing_Performance#NFS_servers |
33 |
> |
34 |
> Stroller. |
35 |
> |
36 |
> |
37 |
|
38 |
Ehmm, yes. NFS-docs approve this. |
39 |
|
40 |
From a programmer's perspective this number is still odd because it's |
41 |
one more than can fit into signed 16bit int and and 32767 less than |
42 |
unsigned 16bit int... maybe they had other reasons. |
43 |
|
44 |
Well, although neither info- nor man-pages mention it, I've found an old |
45 |
man-page [1] which states that these values default to 1024, therefore |
46 |
setting it to 32768 seems the best choice. |
47 |
|
48 |
[1] http://www.trinler.de/de/linux/man.html?command=nfs |