[horde] Horde Caching, APC and CSS/JS caching?

[Michael M Slusarz]

Quoting Ralf Lang <lang at b1-systems.de>:

> APC is a nice feature for a production horde setup, but some
> optimizing questions are not clear to me:
>
> * Why is it preferred to store js and css caching in Filesystem rather
> than the generic Horde_Cache?

Because most browsers can't/don't cache data served via the  
Horde_Cache frontend.  The only 100% guaranteed way to ensure browsers  
update their local cache as needed (without messing around with  
webserver configuration) is by serving from files that physically  
exist on the filesystem.

> * Is it generally smarter to use APC in use_memorycache rather than
> the default cache driver?

No.  The APC cache size is way too small (The APC cache was not  
designed to store user data, unlike Horde_Cache).

> * Do the "Filesystem (recommended)" options for css and js something
> different than using the Horde Cache with filesystem backend?

Yes, it is completely different.  See answer to question #1.

> * Is it safe to run APC with apc.stat=0 for a production horde
> environment?

Maybe: only if you manually ensure that APC/PHP is restarted every  
time you update a file that is cached by APC (e.g. upgrading Horde).

michael

___________________________________
Michael Slusarz [slusarz at horde.org]