Re: reply cache

[Jordi Prats <jprats@cesca.es>]

Thank you!

I miss understood the reply cache, I was thinking it as a way it caches 
the answer to a question like "which are the attributes of that file?"

Now I'm happy with my zero hits ;)

Jordi

Chuck Lever wrote:
> 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.

-------------------------------------------------------------------------
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/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs