Ask a Question
Advertise on boostr.in
Organizational Research By
Surprising Reserch Topic
choosing a php caching technique output caching into files vs opcode caching using -'php,performance,caching,apc,eaccelerator'
choosing a php caching technique output caching into files vs opcode caching ¬†using -'php,performance,caching,apc,eaccelerator'
I've heard of two caching techniques for the PHP code:
When a PHP script generates output it stores it into local files. When the script is called again it check whether the file with previous output exists and if true returns the content of this file. It's mostly done with playing around the "output buffer". Somthing like this is described in this article.
Using a kind of opcode caching plugin, where the compiled PHP code is stored in memory. The most popular of this one is APC, also eAccelerator.
Now the question is whether it make any sense to use both of the techniques or just use one of them. I think that the first method is a bit complicated and time consuming in the implementation, when the second one seem to be a simple one where you just need to install the module.
I use PHP 5.3 (PHP-FPM) on Ubuntu/Debian.
BTW, are there any other methods to cache PHP code or output, which I didn't mention here? Are they worth considering?
Sep 7, 2015
to add a comment.
Related Hot Questions
Government Jobs Opening