We've just finished uploading the latest versions of our XCache and eAccelerator plugins, now at version 0.6.
For those of you that missed the initial announcement, we've written two plugins that let WordPress communicate directly with memory-resident opcode PHP variable caches that are used in XCache and eAccelerator to boost performance and decrease I/O activity.
eAccelerator and XCache are the two most-popular open-source opcode caching engines for PHP, and we highly recommend that any and all hosts use them to improve PHP performance by several folds. In particular, we recommend XCache for best performance. The update to the WordPress opcode caching plugins brings a very important stability/reliability update to the table, especially for those of you running PHP as a multi-threaded (worker_mpm, PHP as ISAPI, PHP as NSAPI, etc.) extension to your application server (which isn't recommended with PHP!).
Aside from preventing future memory-access violation errors and heap corruption, version 0.6 fixes a minor bug that would incorrectly report that eAccelerator is installed and ready for opcode caching when it actually wasn't.
Download XCache for WordPress v0.6
Download eAccelerator for WordPress v0.6
[bug tracker] [support forums] [XCache] [eAccelerator]
NeoSmart Technologies uses and recommends XCache as the PHP opcode caching engine of choice for best performance, uptime, and stability.
Thanks for this - I'm on Apache w/ mod_apache (yes, I know, I'll be leaving it soon! and wtf is the point of mod_apache being so damn easy if it doesn't work (in mpm_worker mode)!!?!?!) and I was getting some heap corruption with XCache php extension when using this plugin.
Now it's gone!! :)
An excellent bit of code! I was actually getting ready to write my own script to utilize the var cache in XCache and this just saved me some time.
sweet, two plugins release for caching, good jobs. tho would be better with APC
The APC one is already there. See the download page.
But I don't know why you'd want to use APC - like everything else produced/maintained by PHP themselves, its performance isn't anything to write home about, especially compared to XCache and eAccelerator.
Great work! I have been using XCache for a number of months now and it works wonders with wordpress, and of course other PHP sites.
I can't wait to use your plugin to help even more. One one, make sure people have their Variable Cache enabled :) I have 2x 128mb of Opcode Cache, but 0mb of Variable (as I never needed it before).
Cheers!
Trying it out on WordPress MU, and apart from the fact that Apache2 segfaults after a few hours of running it, I can no longer access the Site Admin part of my WP Admin panel. It seems to have cached the privileges of a normal user, and not my own. Deleting
object-cache.phpmagically makes the Site Admin button appear again.Does it work if you access that URI directly?
Nope, I get a "You do not have permission to do that" message.
Well, I haven't tested it with WPMU, perhaps I'll get a chance sometime in the near future, but no guarantees. Pretty sad I guess, seeing as the highest concentration of heavy-load servers is most likely WPMU users in the first place :)
Well thanks for the interest, and if you ever want to get on my WPMU server to test anything out, I'll be happy to give you an account.
How about a version that works with the Zend optimizing and caching products? (That what my hosting company has installed.)
Actually, I just confirmed that this is not a problem with your plugin. Even with your plugin disabled, but XCache enabled, Apache still segfaults after a few hours. I suspect a memory leak somewhere.
That's just PHP being a bitch.
I assume you're using worker_mpm? PHP doesn't work properly in multi-threaded environments, despite what they say. Honestly, PHP was never made for anything other than CGI deployment, and FastCGI throws PHP a lifeline.
PHP doesn't thread right, no matter what you do or what extensions you use, though PHP will tell you otherwise. In 3 years of self-hosting PHP, we found the only reliable high-uptime method to be either CGI or FastCGI - *sapi, mpm_worker/mpm_threaded are no go.
Most likely you're running mpm_worker, you'll need to switch to mpm_prefork and sacrifice the huge performance difference in order to have stable PHP uptime.
PHP may be a great language, but it's implentation sucks... on both Windows and Linux.
We dealt with the last of the memory corruption (segfault) bugs in the XCache/eAccelerator plugins with this version, under heavy load-testing for extended periods of time (24 hours+ of non-stop load) without a problem.
Nope, it's prefork.
jeremy@ubuntu-www-2:~$ dpkg -s apache2-mpm-worker Package `apache2-mpm-worker' is not installed and no info is available.jeremy@ubuntu-www-2:~$ dpkg -s apache2-mpm-prefork Package: apache2-mpm-prefork Status: install ok installed
Like I said, it happens even without your plugin (XCache running, but no WP integration). I think I'll have to pursue this with the XCache community (if there is one).
hi, im using wordpress mu in blogmas.com. I have using eaccelerator for 3 day and i happy with it because i help me reduce server load by more than 100%.
Today i install your eaccelerator plugin and everything is okay. So how i can confirm that your plugins doing the work?
thanks for the great plugins.
adar, what I did was I edited the plugin near the top, where it has the following:
include_once(ABSPATH . WPINC . '/cache.php');Change it to:
{ error_log('Oh no! If you see this, the cache plugin isn\'t working!'); include_once(ABSPATH . WPINC . '/cache.php'); }After that, load a few pages, and look in your PHP error logs. If you see the message "Oh no! If you see this, the cache plugin isn't working!" anywhere, you'll know it's not working.
I think I'll add that to the next version, or perhaps have it echo it as an HTML comment, maybe.
Jeremy, you can stop Apache from having a segfault if you run PHP in an "isolation" layer, like using the FastCGI or FastCGId modules.
That way, if a PHP process dies out, it'll be silently replaced and Apache won't even know anything happened.
The Apache FastCGI plugin is great, but more or less dead. Here's the fcgid module: http://fastcgi.coremail.cn/
I've installed the xcache for wordpress v0.6 version in my WP 2.3.1's wp-content\plugins directory and it doesn't show up in the plugins screen in admin to enable this. Any idea why? (This is on Win2003 - Apache - XCache 1.2.1)
XCache is working on a vbulletin forums that I have installed on the same machine.
Thanks!
Ron
It's not a real plugin in that it doesn't show in the plugins administration interface.
This is because it's stored in /wp-content/ and not /wp-content/plugins/
Is anyone using eAccelerator with this plugin? XChache sounds good but my host supports installing eAccelerator for free and at this point, installing Xcache is probably a bit beyond my experience.
Hi,
Firstly, thanks for the excellent work with this plugin. I've been trying to get my dedicated server to run faster with multiple WordPress installs. Given that I didn't know what apache meant until a few weeks ago, I'm doing OK - I got Xcache working after a couple of hours pissing about. I have one question about this plugin for wordpress though:
How do I tell wordpress to use the plugin? - That is, does simply dropping the object-cache.php file (with my auth details therein) into wp-content do this on its own? If so, how? If not, as I suspect, I'll have to tell it using WP-Config where this cache info resides - how do I do that?
Correct me if I'm wrong, its just that, after today's not uncommon trials and tribulations, it seems a little easy just to add this file et voila, it works - how does WordPress know to use it without me going in and defining this file??
Thanks for your help.
Rob
Rob, WordPress 2.1+ will automatically search for object-cache.php, and if it's found WP will take care of the rest. It really is as simple as dragging-and-dropping the file and then you're set :)
In Wordpress 2.5 it seems that the object-cache changed a little bit.. or?
More than just a little :-)
To the best of my knowledge, caching has been ATM removed completely from WP 2.5. But once you install these plugins, it'll be back like before.
Indeed. The object cache is no longer file-based. (See ticket #5570.)
right.. memory based now and it seems (i
ve tested some hours ago..) that its the same speed as using xcache object-cache.. can someone agree? i`m not sure about my tests this morning (too less coffee..) and there are guys out there who have really skillz about that.. after all, 2.5 is really running great and the final should convince a lot people in my mind.. ;)Well, no. Not exactly. I'm planning a lengthy post on the matter today or tomorrow that should clear things up.
thank you, Mahmoud Al-Qudsi. I´m looking forward to it, really.
have a nice day!
greetings,
Chris
I finally got around to making that post... it's a bit longer than I'd originally intended, but hopefully it gets the message across loud and clear:
http://neosmart.net/blog/2008/wordpress-25-and-the-object-cache/
wow! excellent job and hope it will work for me..
thanks