WordPress.org

1. houseofstrauss
   Member
   Posted 2 years ago #

   W3 Total Cache supports APC, but is there any point, or even dissadvantage to useing this plugin with other accelerators like Eaccelerator, zend or xCache? I'm about to set up a new LAMP server and really want to know crucial modules/services required to achieve maximum wp performance.
   Thanks for any advice...

   http://wordpress.org/extend/plugins/w3-total-cache/

2. Frederick Townes
   Member
   Posted 2 years ago #

   You don't need to use APC to use W3TC. Eaccelerator is quite popular as is xcache, you can try any of the available opcode caches quite easily in a single sitting (provided you have some benchmark scheme like apache bench). Sorry there's no direct answer, but mileage varies site to site and based on hardware configuration as well.

   Then use memcached instances + memcache PHP extension for all of your memory caching or use disk caching where applicable.

3. houseofstrauss
   Member
   Posted 2 years ago #

   Thanks for that Frederick, I was not aware that other opcode caches could be used as well. These extended options make setup easier.

4. dschmidt20
   Member
   Posted 2 years ago #

   I use XCache as my opcode cache and have tried both WP-Supercache and Hyper Cache with Thaya Kareeson's Wp-Minify plugin along with Wp-Smush It for image optimization. I should probably do some benchmark testing and since I just started looking into W3TC there is more to unveil...

   I do believe the universal name of the game is to use gzip/mod deflate, have both a static and dynamic cache, and limit HTTP requests, load external css at the top, external js at the bottom, use CSS sprites and keep your files small. This might be an over simplification, but sometimes I just have to remind myself of what has already worked. I tend to over engineer my blog sometimes.

   Best of luck and please let me know how it goes.

5. Frederick Townes
   Member
   Posted 2 years ago #

   I've done extensive testing of opcode caches against PHP 5.2+ and default WordPress install (the latest at a given time) and nothing scales better than APC on debian, centos/redhat/fedora in my testing.

   I do believe the universal name of the game is to use gzip/mod deflate, have both a static and dynamic cache, and limit HTTP requests, load external css at the top, external js at the bottom, use CSS sprites and keep your files small. This might be an over simplification, but sometimes I just have to remind myself of what has already worked.

   Yes these are some things to consider, but there's also proper use of headers, various types of caching and use of the CDN. And within any of the things we've all listed here, enumerable use cases and considerations throughout. Unfortunately, web site optimization is not plug and play, but W3TC takes you very far already (most of the optimizations are even difficult to explain to people), and will continue to press forward.

Topic Closed

This topic has been closed to new replies.