Sam Tregar wrote:
The best workaround is to just switch to the file_cache. In most cases it's just as fast as shared_cache due to the OS caching file access and it's a heck of a lot easier to work with (no arbitrary limits, no need for special tools to clear the cache, etc).
I would seconds Sam's suggestion here. The shared memory caches are not really worth the trouble, and are actually surprisingly slow. If it is absolutely necesary for the cache to be in memory then setup an in-memory filesystem (not sure how to do that on OSX). However, it is often best to just let the OS handle the file system caching directly. The OS is very efficient at keeping the most often accessed files in memory for quick access.
Cheers,
Cees
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Html-template-users mailing list Html-template-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/html-template-users
