info/php-the-right-way
1
0
Fork 0
mirror of https://github.com/codeguy/php-the-right-way.git synced 2025-08-07 22:46:39 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #463 from maglnet/rename-bytecode-to-opcode

Browse Source 
renaming bytecode to opcode
This commit is contained in:
Phil Sturgeon
2014-11-10 06:38:03 -03:00
parent 81c366e1a2 662b5db35f
commit 82914671b1
2 changed files with 25 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
_posts/14-02-01-Bytecode-Cache.md
View File

@@ -1,25 +0,0 @@
---
isChild: true
anchor: bytecode_cache
---
## Bytecode Cache {#bytecode_cache_title}
When a PHP file is executed, under the hood it is first compiled to bytecode (also known as opcode) and, only then, the bytecode is executed.
If a PHP file is not modified, the bytecode will always be the same. This means that the compilation step is a waste of CPU resources.
This is where Bytecode cache comes in. It prevents redundant compilation by storing bytecode in memory and reusing it on successive calls.
Setting up bytecode cache is a matter of minutes, and your application will speed up significantly. There's really no reason not to use it.
As of PHP 5.5, there is a built-in bytecode cache called [OPcache][opcache-book]. This is
also available for earlier versions.
Read more about bytecode caches:
* [OPcache][opcache-book] (built-in since PHP 5.5)
* [APC](http://php.net/manual/en/book.apc.php) (PHP 5.4 and earlier)
* [XCache](http://xcache.lighttpd.net/)
* [Zend Optimizer+](http://www.zend.com/products/server/) (part of Zend Server package)
* [WinCache](http://www.iis.net/download/wincacheforphp) (extension for MS Windows Server)
[opcache-book]: http://php.net/manual/en/book.opcache.php

25
_posts/14-02-01-Opcode-Cache.md Normal file
View File

@@ -0,0 +1,25 @@
---
isChild: true
anchor: opcode_cache
---
## Opcode Cache {#opcode_cache_title}
When a PHP file is executed, under the hood it is first compiled to opcodes and, only then, the opcodes are executed.
If a PHP file is not modified, the opcodes will always be the same. This means that the compilation step is a waste of CPU resources.
This is where opcode caches come in. They prevent redundant compilation by storing opcodes in memory and reusing it on successive calls.
Setting up an opcode cache takes a matter of minutes, and your application will speed up significantly. There's really no reason not to use it.
As of PHP 5.5, there is a built-in opcode cache called [OPcache][opcache-book]. It is also available for earlier versions.
Read more about opcode caches:
* [OPcache][opcache-book] (built-in since PHP 5.5)
* [APC](http://php.net/manual/en/book.apc.php) (PHP 5.4 and earlier)
* [XCache](http://xcache.lighttpd.net/)
* [Zend Optimizer+](http://www.zend.com/products/server/) (part of Zend Server package)
* [WinCache](http://www.iis.net/download/wincacheforphp) (extension for MS Windows Server)
* [list of PHP accelerators on Wikipedia](http://en.wikipedia.org/wiki/List_of_PHP_accelerators)
[opcache-book]: http://php.net/manual/en/book.opcache.php