Re: reply cache

[Chuck Lever <chuck.lever@ORACLE.COM>]

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

Jordi Prats wrote:
> According to the file fs/nfsd/nfscache.c (line 30 on 2.6.23), reply 
> cache is fixed size. Why is this a fixed size cache? Shouldn't be 
> relative to the number of nfsd threads? I've a server with this statistics:
> 
> rc 0 959398 336415498
> 
> By what I've been researching this means: 0 hits, 959398 misses (I 
> supose that means something like "recently deleted") and 336415498 not 
> in cache (and never has been). Is that right?

A DRC hit implies the client is retransmitting.  Not having any hits is 
a good thing -- it means your server is able to handle all your clients 
without much sweat.

> Modifying the CACHESIZE to a bigger size do you think it could enhance 
> NFS performance by getting some hits on the reply cache?

The server's DRC is not a performance feature.  It's a way for the 
server to detect replayed requests from the client.  In a perfect world, 
servers wouldn't even have one.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 259 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs