APC vs EAccelerator vs XCache
 

Just out of curiousity, which one do you use? (If any)

APC, EA or Xcache?

Any paticular reason for choosing either?

The VB tech staff member (who's name I forget) always says to use Xcache, but I'm a little concerned that it hasn't been updated since 2007.

They all serve the same purpose, there is hardly any difference performance wise.
I personally use APC as it is more actively maintained compared to eA and Xcache.

yes its eva2000 aka George who always suggests XCache, which is the best.

JFYI, visit their news page. XCache 1.3.0 compatible with PHP 5.3 is under development.

Ther is not that much difference except:

• XCache has separate segments for code and data
• eAccelerator supports caching opcode on disk

I'd recommend APC as it is developed by the PHP team and is subject to be part of PHP 6 core.

XCache is a little faster compared to APC, but APC is more actively maintained - take your pick.

My first encounter a couple of years ago with APC was not good: frequent crashes...even Apache was crashing. Found out the version I had wasn't all that good, so we upgraded it, and APC has been running flawlessly since then. Completely "hands off" since the upgrade, in fact.

For the miniscule performance gain others have mentioned, I won't bother with Xcache. I do know that based on server load averages, APC cut our server load in half. Nothing to sneeze at!

I use Xcache but i have to switch to something else. I'm getting lots of clogs and there's no fixes available for it. The support for Xcache itself isint that bad, but no one has concrete answers.

As mentioned, APC is a very valid replacement to XCache.

xcache and it works great

I'm trying to switch to APC, but they stopped making windows builds and ive only found one place that has windows builds, but im not sure its trustable and i think they're old versions.

Xcache all the way.

Wish I could help. Anyone with the right tools could compile it on Windows from source code. I can compile a few things on a *nix system, but have never done so with Windows. I'd like to have a Windows build myself, just for my testing platform...

Here's the site i was talking about:

http://www.sitebuddy.com/PHP/Acceler...inaries_builds

Sadly, they dont have recent builds.

I also don't know if the source is legitimate.

XCache doesn't seem to play nice with IonCube, so today, I switched to APC :)

See http://blog.harddisk.is-a-geek.org/i...hp-on-windows/ on how to compile your own on windows.

Hmmm, step 1 could be a show stopper :)

I actually doubt that is really required, but there are also free versions available: http://msdn.microsoft.com/nl-nl/expr...lt(en-us).aspx

Hi Marco,

That page shows how to compile PHP, but not APC. Still, it should not be too much different from compiling APC on *nix systems, other than hoping that the dependencies are not too difficult to figure out. I just don't know my way around Visual Studio 2008 enough to recommend anything here just yet. :(

Still learning after all these years! ;)

Hmm actually that page was linked from the official APC manual page. Didn't fully read it.

I'll have to look at that manual page myself, too. Sometimes semi-"official" builds are buried deep in a site somewhere...

I went back to Xcache and I think i fixed my Xcache issues. I loaded ioncube before Xcache and now i dont have any more issues with the compiler crashing.

Xcache for us.

We refuse to use any software that uses IonCube.

We do not run encrypted PHP code on our site, code we cannot peek into or modify, as a matter of policy.

We are "open source" server and "open PHP" all the way !

If you are running vBulletin, then you are not running open source software.

Maybe not, but we can modify the code... so it is open "enough" "Open PHP" ...... Linux is open. Apache2 is open. PHP for vB is not encrypted, so that is "open source" in a manner of speaking, it is source code and it is open PHP.

Anything else Marco? Or do you want to argue semantics?

--------------- Added [DATE]1252584854[/DATE] at [TIME]1252584854[/TIME] ---------------

From Wikipedia:

:D ;)

"A small number of people" are still using it in the wrong way.

Open Source means that it may be changed and redistributed.

vBulletin is Visible Source, ie. it is not encrypted but it is copyrighted software and may not be distributed.

If you're using windows it may be worth investigating this:
http://blog.calevans.com/2009/09/06/wincache/