Home >Backend Development >PHP Tutorial >Tips for PHP performance optimization_PHP tutorial
Tips for PHP performance optimization_PHP tutorial
- WBOYOriginal
- 2016-07-13 17:35:15872browse
About the performance of require and include
Test data:
There is an array with a total of 30,000 pieces of data and 1MB in size. I divided the data into 2 ways to test //sexinsex
1. array. php directly create a new empty php file and put the array in it
2. array.txt serialize the array and save it
Test program:
Copy content to clipboard code: for ($i=0; $i<100; $i++) {
require(dirname(__FILE__)./array.php);
}
Results:
Page execution time: 12.8904 seconds
Page execution time: 12.8863 seconds
Page execution time: 12.8942 seconds
Page execution time: 12.8992 seconds
Page execution time: 12.9013 seconds
The speed of require and include are the same, and the result is not written
Test program:
Copy the content 97gan to the clipboard code: for ($i=0;$i<100; $i++) {
$all = unserialize(file_get_contents(dirname(__FILE__)./array.txt));
}
Result:
Page execution time: 3.7988 seconds
Page execution time: 3.8125 seconds
Page Execution time: 3.8118 seconds
Page execution time: 3.8062 seconds
Page execution time: 3.8311 seconds
Therefore, two conclusions are drawn. This tutorial comes from 97xxoo Tutorial Network (www.97xxoo.org)
To view the complete tutorial, please click: http://www.97xxoo.org/article/1/2008/20081124428.shtml
1. When writing some classes or functions, do not put large arrays in the program. You should use The file_get_contents method reads
2. The way to do caching, file_get_contents unserialize is faster than require and include. For example, there are problems with the caching methods of sablog and discuz. They read the content in the database and then save it in the program. I haven’t looked at the specific procedure for the require array. It can be done with var_export, but to implement it, serialize is much more convenient and intuitive.
3. Regarding security, PHP requires directly, although it can be added overhead defined() to determine
But the security of the file_get_contents method can be done like this, put all important data in a directory, such as /data/ and then put a .htaccess in /data/, write deny from all, or in the root You can put .htaccess in the directory and add a file suffix even if the rules prohibit it
Tips, just so so....