Performance tuning is required during development. Use xdebug to analyze the thinkphp framework function call graph.
Refer to these 2 articles for the installation of xdebug
NetBeans configures Xdebug to remotely debug PHP
php extension xdebug installation and system analysis using kcachegrind
1. Install xdebug
You need to go to http://www.xdebug.org to read some documents first. xdebug is installed as a php extension
# http://www.xdebug.org/files/xdebug-2.3.3.tgz
# tar -xzf xdebug-2.3.3.tgz
# cd xdebug-2.3.3
# /usr/local/php/bin/phpize
# ./configure --enable-xdebug --with-php-config=/usr/local/php/bin/php-config
# make && make install
2.Give permission
# mkdir -p /tmp/xdebug
# chmod 755 /tmp/xdebug
# chown nobody:nobody /tmp/xdebug
3. Modify php configuration
Modify the php.ini file
[Xdebug]
zend_extension=xdebug.so
xdebug.profiler_enable=on
xdebug.trace_output_dir=/tmp/xdebug
xdebug.profiler_output_dir=/tmp/xdebug
4. Restart php-fpm
# killall php-fpm
# /etc/init.d/php-fpm
5. Run PHP to generate logs
After configuration, running the php file will generate a log file similar to this under /tmp/xdebug
-rw-r--r-- 1 nobody nobody 4615252 Oct 27 17:31 cachegrind.out.29293
6. Use kcachegrind to analyze logs graphically
windows port of kcachegrind
Each function call is clearly visible:
The most serious problem lies in execute, which is actually a large number of SQl queries. called is the number of function calls.
There are many ways to optimize. Use memcached or directly use the respective caches that come with thinkphp. This is the optimized picture. It is obvious that there are fewer calls.
Query Cache
http://document.thinkphp.cn/manual_3_2.html#query_cache
For data queries that do not require high timeliness, we can use the query cache function to improve performance, and there is no need to use caching methods for caching and retrieval ourselves.
The query cache function supports all databases, and supports all caching methods and validity periods.
When using query cache, you only need to call the cache method of the Model class, for example:
1.$Model->cache(true)->where('status=1')->select();
SQL parsing cache
http://document.thinkphp.cn/manual_3_2.html#sql_build_cache
In addition to query caching, ThinkPHP also supports SQL parsing caching. Because of ThinkPHP's ORM mechanism, all SQL is dynamically generated and then executed by the database driver.
So if your application has a large number of SQL query requirements, you can turn on the SQL parsing cache to reduce SQL parsing and improve performance. To enable SQL parsing caching, just set:
1.'DB_SQL_BUILD_CACHE' => true,
You can turn on the SQL creation cache for database queries. The default cache mode is file mode. It can also support xcache and apc mode cache. You only need to set:
1.'DB_SQL_BUILD_QUEUE' => 'xcache',
We know that the amount of SQL query for a project may be very huge, so it is necessary to set the cache queue length. For example, if we hope that the SQL parsing cache does not exceed 20 records, we can set:
1.'DB_SQL_BUILD_LENGTH' => 20, // Queue length of SQL cache.
How profilers lie: the cases of gprof and KCachegrind
Speed up, speed up, speed up your PHP applications! , Part 2: Analyze PHP applications to find, diagnose, and speed up slow code