Unsolved
This post is more than 5 years old
17 Posts
0
1605
NFSv4 Poor Performance
Hi ALL,
We have enabled nfsv4 and advisory locking in VG8.
Below are the steps we have exported a file system.
a)create the interface and route.
b)create a vdm.
c)create a file system and mount the fs on vdm with Mixed policy.
d)export the fs via PDM (server_2) with nfsv4 option.
Now the issue is with performance of this export is very poor. Export is mounted on the host end and it is giving very poor performance.
Note: In the same existing environment nfsv3 share is there and the performance is good for this.
we have tried with nfsv4 delegation option with None and RW.
Please suggest us any other steps to follow to increase the performance for this nfsv4 export.
Thanks,
Praveen
Rainer_EMC
8.6K Posts
0
February 18th, 2013 06:00
Hi,
does mandatory vs. advisory locking make a difference in performance in your NFSv4 tests ?
I would suggest to open a service request
Praveen_td
17 Posts
0
February 18th, 2013 22:00
Hi,
It's some kind of application program is running on the linux host as the MQSeries user....
So this will impact the performance?
Thanks,
Praveen
Rainer_EMC
8.6K Posts
0
February 19th, 2013 04:00
I dont know – never tried it
mcxian
1 Message
0
April 3rd, 2015 05:00
We are also seeing awful nfsv4 performance out of our new Isilon. We have multiple calls into EMC about the issue, so hopefully it get's resolved but I'm not holding my breath.
Here's a quick apache benchmark result from our current environment of a Dell server running linux as an nfsv4 server
###NFSv4 mount to Dell server running linux with nfsv4 server
# mount
HOSTNAME:/www on /export/web type nfs4
(rw,addr=IPADDRESS,clientaddr=IPADDRESS)
Time taken for tests: 6.491 seconds
Requests per second: 154.07 [#/sec] (mean)
Time per request: 162.268 [ms] (mean)
Time per request: 6.491 [ms] (mean, across all concurrent requests)
Percentage of the requests served within a certain time (ms)
50% 155
66% 163
75% 169
80% 173
90% 186
95% 234
98% 268
99% 280
100% 305 (longest request)
Here is the result from Isilon on NFS4
###NFSv4 mount
# mount
HOSTNAME:/ifs/shares/services/cws on /export/web type nfs4
(rw,addr=IPADDRESS,clientaddr=IPADDRESS)
# ab -n 1000 -c 25 -H 'Host: HOSTNAME' http://localhost/
Time taken for tests: 31.813 seconds
Requests per second: 31.43 [#/sec] (mean)
Time per request: 795.331 [ms] (mean)
Time per request: 31.813 [ms] (mean, across all concurrent requests)
Percentage of the requests served within a certain time (ms)
50% 777
66% 809
75% 847
80% 866
90% 910
95% 940
98% 963
99% 991
100% 1079 (longest request)
Isilon nfs3 is a similar result to our current hosting, but we don't wish to give up our existing firewall rules, NFS delegations, server-side-copy support, or have to redo our filesystem to get UID sync.