: I've had a few users who are running/testing Solaris 2.5 with caching.
: They seem to feel that it runs "slow". Not very precise in what is slow,
: but when I turned off caching they reported that it was "faster" or at
: least more consistent. Has anyone else heard these types of complaints?
: I am caching only application directories (framemaker, etc.) and they
: are running on a Sparc 5/75 and IPXes. Surely accessing from local disk
: should be faster than going over the network to our server even if I
: have it consistency checking every 30 seconds?
not in every case.
cacheos, in my experience, isn't something that's always useful,
or to be blindly used. it's just like any other tool or component
of an overall system design.
for example, I had several machines here set up with a cache for
their software directories. everyone noticed that those machines
were significantly slower than all the others. didn't make anyone
happy, that. why? because the machine had only one disk. as a result,
when it started paging, it'd flush out both anon memory and software
text... which it'd then have to reload - from the cache.. and in this
case, all the extra overhead of moving the disk heads back and forth
from swap partition to cache partition and back again and again was
overall slower than reloading the software from the relatively faster
server and just swapping to the local disk.
: One other aspect is that with caching on (30 second timeout to test it),
: when they type a command that doesn't exist in their PATH, it takes 10
: or 15 seconds to return for the first mistyped command. Then its
: instantaneous for a few hours, then it takes 10 or 15 seconds, etc.
turn off consistency checking. :)
= Jeff Bacon General Systems Hack, Michigan Technological University =