On Wednesday, February 7, 2018, John Horne <[email protected]> wrote: > On Tue, 2018-02-06 at 15:33 -0500, Brian Wolff wrote: >> Generally speaking objectcache is used as a last resort form of caching if >> you dont have apcu, memcached, redis, or something else configured. >> > ... >> >> In the long run, I would reccomend installing apcu so that cache stuff is >> stored there instead of the db. >> > Hello, > > Thanks for the reply. > > At the moment we have the main cache type set to CACHE_NONE, but php does have > apc enabled (not sure why we didn't use it). We are running a relatively small > wiki, but I think we may install memcached (and increase the server memory a > bit). We run memcached on some other, non-wiki, servers with no problem. > > I note that with MW 1.27+ there seems to be an issue using apc as the main > cache and with session caching. For that reason using memcache may be easier at > the moment, and not cause problems when we upgrade mediawiki. > >
Fwiw, i dont think theres actually any bugs with session handling at apcu in 1.27 - just that if apcu isnt working properly (e.g. apcu.shm_size too small or any other situation where apcu doesnt actually store values long enough) then sessions wont work (the other caching stuff wont work either but sessions being broken is much more noticable than site being "slow"). But memcached is probably the best caching approach so your plan sounds like a good idea. One side effect of killing objectcache i didnt think of before is it will log everyone out. -- brian > John. > > -- > John Horne | Senior Operations Analyst | Technology and Information Services > University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK > ________________________________ > [http://www.plymouth.ac.uk/images/email_footer.gif]< http://www.plymouth.ac.uk/worldclass> > > This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form. > _______________________________________________ > MediaWiki-l mailing list > To unsubscribe, go to: > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l > _______________________________________________ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
