[SPT/CWIS] content caching w/ smarty

[Kucera, Rich]

>   I'd expect this type of accelerator to provide
>    increasing performance gains in the future.
>
>    Ed
>    P.S.  (If you do give Smarty or an accelerator a try,
>    please don't hesitate to share your experiences with the
>    rest of us. :-))

Ed,
Installed and tried out eaccelerator with CWIS earlier this week (suse 10,
rpm-based install,  was easy,  have suse9.3 RPMs for same exercise later).

It seemed to have a good effect on performance,  but haven't measured
anything.   Conceptually it would complement Pear::Cache_Lite nicely,  they
cache at different levels (eaccelerator would cache the code that executed
the I/O to return the cached HTML response that had been cached by
Cache_Lite).  Probably the filesystem would implement it's own cache
underneath that so it's unlikely the file I/O would result in a disk access.

For both of these cache systems,  you can see the directories of cached files
growing as you test the system.

Also ran across FastCGI,   however it's not clear where it fits or if it
complements either of these.  Doesn't seem likely at this point.  Also
installation seems more involved (replacing the existing apache
integration(mod_php) and forces you to look at low-level architectural
issues).  FastCGI is, however, language-independent.

-Rich