config/index.php wasn't detecting eAccelerator (svn,ea svn,5.2.3) until I changed
$conf->eaccel = function_exists( 'eaccelerator_get' );
to
$conf->eaccel = function_exists( 'eaccelerator_info' );
Is it possible to change it on svn as well?
--alnokta
On 19/09/2007, Mohamed Magdy mohamed.m.k@gmail.com wrote:
config/index.php wasn't detecting eAccelerator (svn,ea svn,5.2.3) until I changed
$conf->eaccel = function_exists( 'eaccelerator_get' );
to
$conf->eaccel = function_exists( 'eaccelerator_info' );
Is it possible to change it on svn as well?
Probably not, no; MediaWiki isn't looking for eAccelerator in its own right (the bytecode caching functionality of such modules operates at a lower level, and scripts don't need to worry about it), but the capability for eAccelerator to be used to store data in an object cache, similar to memcached, but on a smaller (i.e. single application server) scale.
If eaccelerator_get() isn't available, then things are going to break or otherwise not function if MediaWiki starts attempting to use it to read the object cache, hence the check here is accurate.
Rob Church
Rob Church wrote:
On 19/09/2007, Mohamed Magdy mohamed.m.k@gmail.com wrote:
config/index.php wasn't detecting eAccelerator (svn,ea svn,5.2.3) until I changed
$conf->eaccel = function_exists( 'eaccelerator_get' );
to
$conf->eaccel = function_exists( 'eaccelerator_info' );
Is it possible to change it on svn as well?
Probably not, no; MediaWiki isn't looking for eAccelerator in its own right (the bytecode caching functionality of such modules operates at a lower level, and scripts don't need to worry about it), but the capability for eAccelerator to be used to store data in an object cache, similar to memcached, but on a smaller (i.e. single application server) scale.
If eaccelerator_get() isn't available, then things are going to break or otherwise not function if MediaWiki starts attempting to use it to read the object cache, hence the check here is accurate.
Rob Church
Okay, Thanks..
But it works without being enabled (get function) .. What is the things we make that can break it?
Which is better, running it as Zend extension or PHP extension?
Does mw need eAccelerator session handler or not?
I added a note: http://www.mediawiki.org/wiki/Manual:$wgUseEAccelShm
--alnokta
wikitech-l@lists.wikimedia.org