To use redis as a cache you can have something like:
// requires phpredis extension for PHP
$wgObjectCaches['pecl-redis'] = array(
'class' = 'RedisBagOStuff',
'servers' = array( '127.0.0.1:6379' ),
);
$wgMainCacheType = 'pecl-redis';
This would also require that the redis
Awesome! Thank you!
Do you know the version required for these? Thinking maybe I could writeup a
page on mw.o documenting the process of putting redis in place for these.
Jamie Thingelstad
ja...@thingelstad.com
mobile: 612-810-3699
find me on AIM Twitter Facebook LinkedIn
On May 24, 2013, at
If you implement this, is there any use for memcached still? I assume PHP also
needs to be told that sessions are in redis?
Jamie Thingelstad
ja...@thingelstad.com
mobile: 612-810-3699
find me on AIM Twitter Facebook LinkedIn
On May 24, 2013, at 2:44 PM, Aaron Schulz aschulz4...@gmail.com wrote:
2.2.2 of the extensions works for me. I downloaded it from source and
compiled it.
The redis server itself will need to be 2.6 or higher for the job queue.
Looking around, I forgot to mention that JobQueueRedis was actually removed
from 1.21 (though it's in master and will be in 1.22).
--
Note that if you already use memcached for the main cache, there isn't really
any reason to switch to redis unless you need replication or persistence.
Anyway, to use it for sessions, if you had $wgSessionCacheType explicitly
set to something, then you'd need to change that too (like to
I can see how memcached and redis would have similar performance for sessions.
Is that also true for job queue? I was assuming that job queue could move from
database to redis, but not to memcached. Is that a correct assumption?
The main reason I could see moving sessions into redis would be to
Indeed, the queue cannot use memcached. Redis will trivialize the time spent
on actually queue operations, which could help if that is a bottleneck for
job runners. If the actual jobs themselves are slow, of course it won't help
too much.
Have you already tried setting the job run rate to 0 and
