Re: strange caching behavior

[Peter Staubach <staubach@redhat.com>]

Mark Steele wrote:

>Hi Peter,
>
>The opcode cache is working as expected. It detects the changes
>in the php scripts and recompiles the new files into memory.
>
>Therefore it sees the change in the modification time of the files.
>
>I am using rsync to update the files on the server from a code 
>repository.
>
>I don't see how either of things things affect the behavior of the
>NFS.
>
>Using more caching/less bandwidth when 'freshly' mounted 
>without any file updates 
>
>VS. 
>
>Using lots of bandwidth when files are changed on the NFS server
>(which is done infrequently)
>

My thinking that was the NFS client typically does not do things on its
own, but does so based on application activity.  For a large enough
working set, the more applications request from the file system, the
more traffic that there will be over the wire.

What does the increased traffic look like?  Is it metadata style operations
such as GETATTR or LOOKUP or is it data movement like READ?  What is the
typical working set size, in bytes and numbers of files, of these scripts?

    Thanx...

       ps


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs