{"id":478,"date":"2007-09-16T15:11:17","date_gmt":"2007-09-16T15:11:17","guid":{"rendered":"http:\/\/neosmart.net\/blog\/2007\/xcache-and-eaccelerator-plugins-for-wordpress\/"},"modified":"2013-08-26T18:17:03","modified_gmt":"2013-08-26T23:17:03","slug":"xcache-and-eaccelerator-plugins-for-wordpress","status":"publish","type":"post","link":"https:\/\/neosmart.net\/blog\/xcache-and-eaccelerator-plugins-for-wordpress\/","title":{"rendered":"XCache and eAccelerator Plugins for WordPress"},"content":{"rendered":"

In this episode of “The Never-Ending Quest for Better Server Performance,” we follow our heroes’ journey through the dangerous and murky woods of PHP opcode caching engines, where they aren’t content with just installing an opcode caching engine, but <gasp> becoming one with it too!<\/em>\n<\/p>\n

Yep, you heard that right. We’ve just released two new plugins for the WordPress users out there, that take opcode caching to the next level. If you haven’t already installed an opcode caching engine like XCache<\/a> (our favorite!), eAccelerator<\/a>, Turck MMcache<\/a>, Memcached<\/a>, APC<\/a>, or PHPA<\/a> then you really need to do that right now<\/em> before even continuing this article. Really, what were you waiting for!?\n<\/p>\n

<\/p>\n

Now that you’ve discovered the joy of opcode caching and the benefits it brings to your servers, here comes the next step: integrating the actual code your server runs with your opcode caching engine. By default, when you install the opcode cacher, it’ll sit in the background (in the memory!!!!) and memorize what each compiled PHP script looks like. Sure, it’s a lot of work, but it can be doing even more – like memorizing objects and variables in its uber-fast memory too.\n<\/p>\n

The problem is that this isn’t something “easy” that happens by itself, it requires a conscious and painful effort on behalf of script developers<\/em> to add an integration layer in their script that lets it communicate with the opcode caching engine. Well, that’s what we’ve done for all you WordPress lovers out there: we’ve added support for the two very popular open-source opcode caching engines – XCache and eAccelerator. Both are very good opcode cachers in their own right, but with our WordPress extensions, they become Godsends.\n<\/p>\n

Installation is a snap: just extract the single PHP file for your engine, and stick it in your \/wp-content\/ folder to discover the truly powerful side of opcode caching! You can use these on dedicated and shared hosts, just figure out what caching engine is in use and download the appropriate file.\n<\/p>\n

Download XCache for WordPress<\/a>\n<\/p>\n

Download eAccelerator for WordPress<\/a>\n<\/p>\n

< ?php include(\"http:\/\/neosmart.net\/includes\/chipin.php?type=wide\"); ?><\/p>\n","protected":false},"excerpt":{"rendered":"

In this episode of “The Never-Ending Quest for Better Server Performance,” we follow our heroes’ journey through the dangerous and murky woods of PHP opcode caching engines, where they aren’t content with just installing an opcode caching engine, but <gasp> … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[533,367,532,535,537,536,227,538,54,531],"class_list":["post-478","post","type-post","status-publish","format-standard","hentry","category-software","tag-apc","tag-download","tag-eaccelerator","tag-memcached","tag-opcode","tag-phpa","tag-plugins","tag-turck-mmcache","tag-wordpress","tag-xcache"],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p4xDa-7I","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/478","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/comments?post=478"}],"version-history":[{"count":3,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/478\/revisions"}],"predecessor-version":[{"id":2426,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/478\/revisions\/2426"}],"wp:attachment":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/media?parent=478"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/categories?post=478"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/tags?post=478"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}