Jeremy Dunck wrote:
I see that MW 1.5 supports 2 object caching methods.
Is one preferred, or are they considered interchangable?
One is not prefered as far as MW goes, but you should know the
background behind them.
eAccelerator is the "successor" of Turck MMCache. The primary developer
for Turck was hired by Zend and so Turck was fairly considered "abandoned".
eAccelerator branches off of Turck. However, due to
copyright/patent/etc. issues with Zend, they have been forced to develop
a new architecture.
eAccelerator, in our enviroment, has caused much grief, especially in
combination with WordPress (go figure). (
endeavour.zapto.org and its
hosted sites are what I am talking about.) The reason we keep it
installed is so that BrickWiki has some scrap of performance.
MediaWiki only uses Turck/eAccel for shared memory management (faster
caching that SQL). Both of these apps also cache parsed scripts
(speeding startup time) and may even optimize them (speeding execution
time, hopefully).
The bottom line is to do your own testing before making a decision.
-- Jamie
-------------------------------------------------------------------
http://endeavour.zapto.org/astro73/
Thank you to JosephM for inviting me to Gmail!
Have lots of invites. Gmail now has 2GB.