Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Just wondering if theres any performance benefits for using something like APC over eAccelerator (for PHP) on a shared environment.

share|improve this question

closed as off-topic by masegaloeh, kasperd, Ward, mdpc, Andrew Schulman Apr 19 '15 at 8:37

This question appears to be off-topic. The users who voted to close gave this specific reason:

If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 2 down vote accepted

Not sure about in replacement of eAccelerator, but generally APC is better to use than eAccelerator as it is more actively developed than the latter and has a much better release cycle. Also it's probably worth pointing out that APC will be integrated as part of the core of PHP with the forthcoming PHP6 (though you'll still have to explicitly enable it in the php.ini file.) which fairly biases my mind towards it as well.

share|improve this answer

It's difficult to quantise the benefit that opcode caching will bring you without knowing much about your environment and code. Generally speaking though, you will see a performance increase of somewhere between a little and a lot, for what is very trouble on your part. So give it a go and observe your metrics.

There is a pretty good statistical comparison of opcode caches over at Stackoverflow. As you'll see from the results; APC is often pipped to the post by eAccelerator in terms of performance. However performance isn't everything. APC is easy to install, configure and has good future backing - frequent releases and adoption into the PHP codebase.

Personally I use APC wherever possible.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.