Re: [PATCH 0/2] RFC: nfs client: lower number of NFS ops in some circumstances

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

 



On 10/04/13 17:18, Peter Staubach wrote:
> Miquel van Smoorenburg wrote:
>>
>> These NFS client patches are posted as an RFC - request for comment.
>>
>> The idea behind these patches is to make it possible to cut down on
>> the number of NFS operations used when opening a file in certain
>> circumstances and environments (esp. mostly-readonly environments).
>
> Outside of possibly reducing the overall RPC count between the NFS
> client and the NFS server, was a difference measured in the overall
> performance of the website, from the customer's viewpoint?

(Sorry, it took a while before I could run these tests)

Yes- mostly tests with a webbrowser, as in "does it 'feel' faster",
which is hard to quantify objectively.

We also ran some more objective tests, which I re-ran just now.

I took one of our servers out of the cluster, and did some tests on it.
I ran a "wget http://customer-site.nl/"; on it repeatedly with different
mount options. The customer testsite is a joomla site (one of the
'modular' CMSes that stats/opens a lot of files for each page-request).

2 sessions below, each session was started with an empty cache.


1. Mountoptions: rw,nosuid,tcp,noatime,vers=3

   request    request time (wget)
   1          0m1.287s
   2          0m0.550s
   3          0m0.453s
   4          0m0.343s
   5          0m0.379s

   nfsstat:

   Client rpc stats:
   calls      retrans    authrefrsh
   2612       0          2612    

   Client nfs v3:
   null         getattr      setattr      lookup       access       readlink     
   0         0% 1308     50% 0         0% 416      15% 667      25% 3         0% 
   read         write        create       mkdir        symlink      mknod        
   216       8% 0         0% 0         0% 0         0% 0         0% 0         0% 
   remove       rmdir        rename       link         readdir      readdirplus  
   0         0% 0         0% 0         0% 0         0% 0         0% 2         0% 
   fsstat       fsinfo       pathconf     commit       
   0         0% 0         0% 0         0% 0         0% 

2. Mountoptions: rw,nosuid,tcp,noatime,noaccesscheck,sloppycto=3,vers=3

   request    request time (wget)
   1          0m0.787s
   2          0m0.376s
   3          0m0.385s
   4          0m0.324s
   5          0m0.338s

   nfsstat:

   Client rpc stats:
   calls      retrans    authrefrsh
   1539       0          1539    

   Client nfs v3:
   null         getattr      setattr      lookup       access       readlink     
   0         0% 902      58% 0         0% 416      27% 0         0% 3         0% 
   read         write        create       mkdir        symlink      mknod        
   216      14% 0         0% 0         0% 0         0% 0         0% 0         0% 
   remove       rmdir        rename       link         readdir      readdirplus  
   0         0% 0         0% 0         0% 0         0% 0         0% 2         0% 
   fsstat       fsinfo       pathconf     commit       
   0         0% 0         0% 0         0% 0         0% 


You can clearly see that with the new mount options the number of NFS requests
is way lower, and page loading time (esp. for the first request) has gone down.
The number of lookups and reads is exactly the same, but the second nfsstat has
zero 'access' calls and 45% less 'getattr' calls.

Mike.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux