This article needs to be updated. The reason given is: Zend OPcache was integrated into PHP 5.5.August 2017)(
Most PHP accelerators work by caching the compiled opcode/bytecode of PHP representation of php files to avoid the overhead of parsing and compiling source code on each request (some or even most of which may never be executed). To further improve performance, the cached code is stored in shared memory and directly executed from there, minimizing the amount of slow disk reads and memory copying at runtime.
The effect on application performance of opcode caching varies widely, depending on factors such as the inherent execution time of the PHP application and the percentage of source code actually executed on a given request, and whether additional optimization steps are performed. While a code optimizer may even slow down overall performance when used in isolation, it can provide an additional performance boost when coupled with a bytecode cache, as the optimization effort is performed just once.
- "PHP on Windows: The WinCache 1.0 Benchmark". Archived from the original on 22 July 2012. Retrieved 2 September 2010.
- "Benchmarking Drupal with PHP op-code caches: APC, eAccelerator and XCache compared". Retrieved 2 September 2010.
- "Performance of Yii". Archived from the original on 19 August 2010. Retrieved 2 September 2010.
- Alternative PHP Cache, a widely used opcode cache.
|This programming-language-related article is a stub. You can help Wikipedia by expanding it.|