PHP ~Performance comparison with various acceleration tools~

Introduction to Xcache

The principles and functions of the PHP accelerator have been introduced before (see the PHP-FPM server of the LAMP architecture). As one of the most widely used PHP accelerators, xcache has better performance than the early eAccelerator accelerator, so this time we will compare PHP programs. The performance impact of accelerator xcache during execution.



Install xcache

Copy code
# Install
tar xf xcache-3.0.3.tar.gz
cd xcache-3.0.3
/usr/local/php/bin/phpize # xcache is installed as an external module of php
./configure --enable-xcache --with-php-config=/usr/local/php/bin/php-config
make && make install
# When the installation is completed, a line similar to the following will appear:
Installing shared extensions: /usr/local/php/lib/php/extensions/no-debug-non-zts-20100525/
# Edit php.ini to integrate php and xcache:
# First import the sample configuration provided by xcache into php.ini
mkdir /etc/php.d # This is the configuration file scanning directory configured when installing PHP earlier
cp xcache.ini /etc/php.d # The xcache.ini file is in the source code directory of xcache.
# Next edit /etc/php.d/xcache.ini, find the line starting with extension, and change it to the following line:
extension = /usr/local/php/lib/php/extensions/no-debug-non-zts-20100525/xcache.so
# If there are multiple extension command lines in the php.ini file, make sure this new line is ranked first.
# Check if xcache has been installed successfully:
/usr/local/php/bin/php -m |grep -i xcache
Copy code


Introduction to Opcache

The new generation PHP accelerator was developed by Zend. Its implementation principle is similar to Xcache. It buffers the data after PHP execution into memory to avoid repeated compilation processes. It can directly use the compiled code in the buffer to increase speed and reduce Server load, but performance is superior to Xcache, see test results for details

Install Opcache



Copy code
wget http://pecl.php.net/get/zendopcache-7.0.2.tgz
tar xzf zendopcache-7.0.2.tgz
cd zendopcache-7.0.2
/usr/local/php/bin/phpize
./configure --with-php-config=/usr/local/php/bin/php-config
make
make install
# For configuration file settings, you can directly add the following content at the end of php.ini, but here, configure the new file opcache.ini under the scanning directory php.d of the PHP configuration file for easy management. php-config-scan-dir is in Defined when compiling and installing PHP
# vi /etc/php.d/opcache.ini
[opcache]
zend_extension=/usr/local/php/lib/php/extensions/no-debug-non-zts-20100525/opcache.so
opcache.memory_consumption=128 # The allocated memory size in MB, that is, how much precompiled php code can be stored
opcache.interned_strings_buffer=8 # The memory size of interned strings in MB
opcache.max_accelerated_files=4000 # Maximum number of files allowed to be cached
opcache.revalidate_freq=60 # How often to check file timestamp to change shared memory allocation, unit is s
opcache.fast_shutdown=1 # Whether to enable fast shutdown of the queue, 1 means enabled
opcache.enable_cli=1 # Allow caching of PHP programs under CLI
#Check that the module is installed successfully: /usr/local/php/bin/php -m |grep -i opcache
Copy code
Introduction to hhvm

HipHop VM (HHVM) is a virtual machine launched by Facebook to execute PHP code. It is a JIT (Just-In-Time) compiler for PHP and has the advantages of generating fast code and just-in-time compilation;

hhvm compiles and converts PHP code into C++ programs for execution, and the execution efficiency is significantly improved;

According to Facebook, HHVM has achieved significant improvements in speed, being 60% faster than the currently used PHP interpreter and using 90% less memory

Install hhvm

Because hhvm is still in the research and development stage, there are still very few domestically used in production environments, and the environment required for installation is relatively complex (for example, the versions of boost-system and boost-filesystem under CentOS6.5 are too low), so I am still During the debugging and testing phase, wait until the test results are available, and then post the hhvm test results together.



Test steps

# Find another virtual machine and perform a stress test on the HTTPD server (192.168.1.110)
# For testing tools, just use the benchmark testing tool ab that comes with Apache
# The test method is as follows:
ab -c 20 -n 2000 http://192.168.1.110:8080/index.php
# Note: The test uses 20 concurrency to check the acceleration effect of the xcache accelerator without affecting access; the test page can use the login page index.php of phpMyAdmin just deployed in the previous lecture
# Note: In order to better test the caching characteristics of the PHP accelerator, you can test several times in a row to get a stable value