[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#775014: nfs-common: Degraded performance on nfs4 clients after upgrade to Jessie



El Dissabte, 10 de gener de 2015, a les 19:30:12, Martin Steigerwald va 
escriure:
[...]

> 
> I suggest you upgrade to 3.16 bpo kernel. Maybe that already makes a
> difference. And additionally there is greater chance you get security
> updates on that one, cause AFAIK older bpo kernels are not maintained
> anymore.

It's in one of the main server of my institute and it's not easy. Anyway, I 
have programed it to do it soon. Thanks for the suggestion.

[...]

> > cami:/recursos /home/recursos nfs4
> > rw,sync,nodev,noatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,soft,pro
> > t
> > o=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.8,local_lock
> > =n one,addr=192.168.1.254 0 0
> 
> What is this on the wheezy machine?

all the servers are wheezy. The clients are Jessie.

> Look in grep nfs /proc/mounts or nfsstat -m
> 
> I suggest not to manually tune this. Current kernels use good default
> values. I have seen rsize and wsize of up to 1048576.

> Additionally are they all the same hardware, same network cards? If not,
> what is the fast system using and what is the slow system using?


well, I have worked on this issue and i have found some conclusions:

- now, with modern kernels (and nfs4) it has no sense to set rsize and wsize. 
The negotiation between client and server do the best one. So, all the pages 
in the net are outdated.

- the sync parameter works totally different (client side) in a 3.2 kernel than 
3.16 (also 3.12 or 3.8) . I'm talking for a similar hardware (Gigabyte NIC, 
similar cpu, etc) but on a 100 Mb network) from ~7MB/s (kernel 3.2 vs 63,8 
kB/s >3.8). In another environment with a Giga network the rates are ( ~145 
kB/s vs ~70,3 MB/s)

- no significant differences in with wsize. At least that I had found. But the 
default autonegotiation works very well.

- I still don't understand why, although I have a good hardware in the work, 
when my clients do:
 
$ dd if=/dev/zero of=myrandom bs=4096 count=70000

obtains about ~70MB/s

and if I execute the same in the server I obtain 167 MB/s. About 2.5 time 
slower

I still consider this issue important, I think that a lot of people that 
upgrade to Jessie with nfs mounts will found some problem. but this is just 
MHO.

Leopold

-- 
--
Linux User 152692     GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: