info/php-the-right-way
1
0
Fork 0
mirror of https://github.com/codeguy/php-the-right-way.git synced 2025-08-17 11:10:37 +02:00
Code Issues Projects Releases Wiki Activity

spelling fixes

Browse Source
This commit is contained in:
Roman Marintsenko
2012-07-10 19:04:20 +03:00
parent 655e5ad2a1
commit 154a7677e9
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
_posts/10-02-01-Bytecode-Cache.md
View File

@@ -7,11 +7,11 @@ isChild: true
When PHP file is executed, under the hood it is first compiled to bytecode (also known as opcode) and only then, the bytecode is executed. When 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 PHP file is not modified, then bytecode will always be same, which means that compilation step is a waste of CPU resources. If PHP file is not modified, then bytecode will always be same, which means that 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. 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. 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.
Popular bytecodes caches are: Popular bytecodes caches are:
[APC](http://php.net/manual/en/book.apc.php) [APC](http://php.net/manual/en/book.apc.php)
[xCache](http://xcache.lighttpd.net/) [XCache](http://xcache.lighttpd.net/)
[Zend Optimizer+](http://www.zend.com/products/server/) (part of Zend Server package) [Zend Optimizer+](http://www.zend.com/products/server/) (part of Zend Server package)