John Perkins wrote: > Some questions that have come up at our site recently after some review > of our OpenAFS client setup. We're running Windows XP with OpenAFS > 1.5.52 or 1.5.30-36 clients. > > 1. Is there a general recommendation for cache size these days? We had > been setting the cache size to 1GB if there was what we thought to be > enough memory on the host. Recently that has caused problems on some > computers, so we've reduced that to 512MB. Still, this is much larger > than the 98MB default.
You should examine the afsd_service.exe process on the two machines to determine what DLLs are being loaded on the one machine vs the other or which is being installed at a conflicting location. The SysInternal's Process Explorer is a good tool for this purpose. > 2. Is there a recommendation toward using or not using the > "NonPersistentCaching" (virtual-memory cache or "normal" file cache)? Do not use it NonPersistentCaching. It doesn't provide you more caching space and limits the ability of your system to page other applications. > 3. Whether or not the NonPersistentCaching option is in use, > the following command: > cmdebug -server <hostname> -cache > returns the following as part of its output: > Cache type: memory In both cases a paging file backed memory cache is being used. > afsd_init.log shows cache type FILE or VIRTUAL as expected; it's just > cmdebug that appears to be confused about this. cmdebug is not confused. It is a cross platform debugging tool. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
