Home >Backend Development >PHP Tutorial >How to enable Opcode in PHP7 to create powerful performance Detailed explanation of PHP skills

How to enable Opcode in PHP7 to create powerful performance Detailed explanation of PHP skills

jacklove
jackloveOriginal
2018-06-25 17:03:271823browse

This article mainly introduces to you the relevant information on how to enable Opcode in PHP7 to create powerful performance. The article introduces it in great detail through sample code. It has certain reference and learning value for everyone's study or work. Friends who need it can follow Let’s learn together with the editor

Preface

Brother Niao said in his blog that there are several tips to improve the performance of PHP 7, The first is to enable opcache:

Remember to enable Zend Opcache, because PHP7 is faster even without Opcache than PHP-5.6 with Opcache enabled, so during the previous testing period, someone did not enable Opcache.

So what is Opcache?

The predecessor of Opcache is Optimizer, which is a closed-source but free-to-use PHP optimization acceleration component developed by Zend, the official company of PHP. The Optimizer caches the script file Opcode generated by precompiling the PHP code in the shared memory for repeated use in the future, thereby avoiding the time consumption of reading the code from the disk and compiling it again. At the same time, it also applies some code optimization modes to make the code execute faster. Thereby speeding up the execution of PHP.

The normal execution process of PHP is as follows

request request (nginx, apache, cli, etc.) -->Zend engine reads .php file-- >Scan its dictionary and expressions-->Parse the file-->Create computer code to be executed (called Opcode)-->Finally execute the Opcode--> response returns

every time Requesting a PHP script will perform the above steps once. If the PHP source code does not change, then the Opcode will not change. Obviously there is no need to regenerate the Opcode every time. Combined with the ubiquitous caching mechanism in the Web, we can cache the Opcode for future use. Wouldn't it be faster to access cached Opcode directly? The flow chart after enabling Opcode cache is as follows:

The purpose of Opcode cache is to avoid repeated compilation and reduce CPU and memory overhead. .

The following introduces the installation of Opcache

Installation:

1. Find the extension of opcache, mine is php7.1

yum list php71*

2. Install extension

yum install php71w-opcache.x86_64

Configuration:

zend_extension=opcache.so
[opcache]
;Enable opcache
opcache.enable=1

;In CLI environment, PHP enables OPcache
opcache.enable_cli=1

;OPcache shared memory storage size, unit MB
opcache.memory_consumption=128

;PHP uses a technology called string interning to improve performance. For example, if you use the string "foobar" 1000 times in your code, PHP will only allocate an immutable memory area to store the string the first time it is used, and the other 999 times it will be used. Point directly to this memory area. This option will take this feature to the next level - by default this immutable memory area will only exist in a single php-fpm process. If this option is set, it will exist in all php-fpm processes. shared in. In larger applications, this can be very effective in saving memory and improving application performance.
The value of this option is in megabytes. If it is set to 16, it means 16MB. The default is 4MB
opcache.interned_strings_buffer=8

;This option is used Used to control the maximum number of PHP files that can be cached in memory. This option must be set large enough to be larger than the sum of all PHP files in your project.
The minimum value of the setting value range is 200, the maximum value is 100000 before PHP 5.5.6, and 1000000 after PHP 5.5.6. That is to say between 200 and 1,000,000.
opcache.max_accelerated_files=4000

;Set the cache expiration time (in seconds). If it is 0, it must be checked every time.
opcache.revalidate_freq=60

;From Literally means "allowing for faster shutdown". Its role is to provide a faster mechanism to call the destructor in the code at the end of a single request, thereby speeding up PHP's response speed and recycling of PHP process resources, so that the application can respond to the next request more quickly . Set it to 1 to use this mechanism.
opcache.fast_shutdown=1

;If enabled (set to 1), OPcache will check the file timestamp (timestamp) in the number of seconds set by opcache.revalidate_freq to check whether the script has been updated.
If this option is disabled (set to 0), opcache.revalidate_freq is ignored and PHP files are never checked. This means that if you modify your code, and then you update it to the server, and then request the function corresponding to the updated code on the browser, you will not see the effect of the update.
It is strongly recommended that you use it in a production environment Set to 0. After updating the code, restart PHP and the web server smoothly.
opcache.validate_timestamps=0

;Enable Opcache File Cache (experimental). By enabling this, we can let Opcache cache the opcode cache to an external file. For some scripts, there will be obvious Performance improvement.
In this way, PHP will cache some Opcode binary export files in the /tmp directory, which can exist across the PHP life cycle.
opcache.file_cache=/tmp

View phpinfo :

Test results:

The same interface has been improved from a few hundred milliseconds to about 50ms now

Summary

##Articles you may be interested in:

PHP solves the problem of rabbits giving birth to rabbits based on recursive algorithm php tips

Detailed explanation of exception handling in ThinkPHP_php examples

PHP7 PHP skills based on curl-based image upload function

##

The above is the detailed content of How to enable Opcode in PHP7 to create powerful performance Detailed explanation of PHP skills. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn