Writes are also put into read cache. If you have a highly cache dependent file system on a filer with high writes you are also caching those and will roll what is in cache more.

We ended up moving our tools repos to low write filers to alleviate the problems we were experiencing from this. C-

----- Original Message ----- From: owner-toasters@mathworks.com owner-toasters@mathworks.com To: toasters@mathworks.com toasters@mathworks.com Sent: Thu Nov 13 11:09:05 2008 Subject: writes through NVRAM *also* in read cache?

While I'm thinking of it... During a conversation with my sales rep., this question came up... (Haven't had a chance to ask our local SE's yet...)

If a write happens through NVRAM (which it always does), once the write is acknowledged onto disk and the NVRAM flushed, is that data in read cache *as well*? Or, is the path to disk for a write unique, and when you want to read that data, it has to be read from disk and *then* put into read cache?

I'm thinking of our software development environment, where we (of course) do a lot of writing of object files and then linking them into libraries and executables....

Until next time...

The MathWorks, Inc. 508-647-7000 x7792 3 Apple Hill Drive, Natick, MA 01760-2098 508-647-7001 FAX tmerrill@mathworks.com http://www.mathworks.com ---