Home>Article>Backend Development> PHP performance optimization example sharing
If a method can be static, declare it as static, and the speed can be increased by 1/4. Even when I tested, this increased by nearly 1/4. three times.
Of course, this test method needs to be executed at level 100,000 or above for the effect to be obvious.
In fact, the main difference in efficiency between static methods and non-static methods is memory: static methods generate memory when the program starts, and instance methods generate memory while the program is running, so static methods can be called directly, and instance methods must first generate instances. Calling methods through instances is very fast statically, but will take up more memory.
Any language operates on memory and disk. As for whether it is object-oriented, it is just a matter of the software layer. The bottom layer is the same, but the implementation method is different. Static memory is continuous because it is generated at the beginning of the program, while the instance applies for discrete space, so of course it is not as fast as the static method.
Static methods always call the same piece of memory. The disadvantage is that it cannot be automatically destroyed, but can be destroyed by instantiation.
Test:
Echo
0.000929 - 0.001255 s (average 0.001092 seconds )
Print
0.000980 - 0.001396 seconds (average 0.001188 seconds)
The difference is about 8%. Generally speaking, echo is faster.
Note that when echoing large strings, performance will be seriously affected if no adjustments are made. Use mod_deflate to open apached for compression or open ob_start to put the content into the buffer first.
All fools understand this.
Arrays and objects occupy a lot of memory in PHP. This is caused by the underlying zend engine of PHP.
Generally speaking, the memory utilization of PHP arrays is only 1/10. In other words, an array with 100M of memory in C language requires 1G in PHP.
Especially in systems where PHP is used as a backend server, the problem of excessive memory consumption often occurs.
For functions starting with __, name them Magic functions, such functions are first accessed under specific conditions. In general, there are the following magic functions
__construct(), __destruct(), __get(), __set(), __unset(), __call(), __callStatic(), __sleep(), __wakeup(), __toString (), __set_state(), __clone(), __autoload()
In fact, if __autoload cannot efficiently compare the class name with the actual disk file (note, this refers to the actual disk file, not just file name), the system will have to make a large number of judgments about whether files exist (which need to be searched in the paths included in each include path), and judging whether files exist requires disk I/O operations. As we all know, disk I/O operations The efficiency of /O operations is very low, so this is the reason why the autoload mechanism is less efficient.
Therefore, when we design the system, we need to define a clear mechanism for mapping class names to actual disk files. The simpler and clearer this rule is, the more efficient the autoload mechanism will be.
Conclusion: The autoload mechanism is not naturally inefficient. Only abuse of autoload and poorly designed autoload functions will lead to a reduction in its efficiency.
So try to avoid using the __autoload magic The method is open to question.
This is because requirere_once needs to determine whether the file has been referenced), so it should be used as little as possible. Commonly used require/include methods to avoid.
If a relative path is included, PHP will traverse the include_path to find the file.
Using absolute paths will avoid such problems, so it will take less time to resolve the operating system path.
As you can imagine. One is ready-made and can be used directly, and the other requires the result obtained by the function.
Needless to say, regular expressions consume the most performance.
Are there any useful functions that you missed? For example: strpbrk()strncasecmp()strpos()/strrpos()/stripos()/strripos() speeds up strtr. If all that needs to be converted is a single character,
use a string instead of an array to do strtr:
'e', )); // bad ?>
Efficiency improvement: 10 times.
In addition, do not make unnecessary replacements. Even if there is no replacement, str_replace will be Its parameters allocate memory. very slow! Solution:
Use strpos to search first (very fast) to see if replacement is needed. If necessary, replace again. Efficiency: - If replacement is needed: The efficiency is almost equal, and the difference is about 0.1%.
If no replacement is required: using strpos is 200% faster.
If a function can accept both arrays and simple characters as parameters, such as a character replacement function, and the parameter list is not too long, you can consider writing additional A piece of replacement code so that each parameter passed is a character, instead of accepting arrays as search and replace parameters. Make big things small, 1+1>2;
Using @ actually involves a lot of operations in the background. The efficiency difference between using @ and not using @ is: 3 times. Especially do not use @ in a loop. In the test of 5 loops, even if you use error_reporting(0) to turn off the error first and then turn it on after the loop is completed, it is faster than using @.
It is recommended to develop the habit of adding quotes to array keys;
For example, For($x=0; $x ebf182cf31f7d4a0b6c310a02a956193prop++) is 3 times slower than a local variable;
PHP may check whether this global variable exists;
Because I added 10 There is no difference in performance after adding multiple methods or methods to the tested class (these methods are before and after the test method);
Because PHP will search for variables in the string surrounded by double quotes, single quotes will not.
The PHP engine allows the use of single quotes and double quotes to encapsulate string variables, but there is a big difference! Using double-quoted strings tells the PHP engine to first read the contents of the string, find the variables in it, and change them to the values corresponding to the variables. Generally speaking, strings have no variables, so using double quotes will lead to poor performance. It is better to use string concatenation instead of double quoted strings.
BAD: $output = "This is a plain string"; GOOD: $output = 'This is a plain string'; BAD: $type = "mixed"; $output = "This is a $type string"; GOOD: $type = 'mixed'; $output = 'This is a ' . $type .' string';25. It is faster to use commas instead of dot connectors when echoing strings. echo is a "function" that can take multiple strings as parameters (Annotation: The PHP manual says that echo is a language structure, not a real function, so the function is enclosed in double quotes).
例如echo $str1,$str2。
尽量多用静态HTML页面，少用脚本。
高性能的分布式内存对象缓存系统，提高动态网络应用程序性能，减轻数据库的负担;
也对运算码 (OP code)的缓存很有用，使得脚本不必为每个请求做重新编译。
这几乎能降低1/4的存储空间。同时可以很容易对地址进行排序和快速查找;
这个内置函数能保证每一个的域名对应一个IP地址;
在你想在彻底重做你的项目前，看看PEAR有没有你需要的。PEAR是个巨大的资源库，很多php开发者都知道;
理想的错误报告应该被完全禁用在php.ini文件里。可是如果你在用一个共享的虚拟主机，php.ini你不能修改，那么你最好添加error_reporting(0)函数，放在每个脚本文件的第一行(或用
require_once()来加载)这能有效的保护敏感的SQL查询和路径在出错时不被显示;
这种内置的函数使用gzip算法能压缩到90%;
你可以在变量前加个“&”来表示按地址传递而非按值传递;
Fully understand “magic quotes” and the dangers of SQL injection. I’m hoping that most developers reading this are already familiar with SQL injection. However, I list it here because it’s absolutely critical to understand. If you’ve never heard the term before, spend the entire rest of the day googling and reading.
当操作字符串并需要检验其长度是否满足某种要求时，你想当然地会使用strlen()函数。此函数执行起来相当快，因为它不做任何计算，只返回在zval 结构（C的内置数据结构，用于存储PHP变量）中存储的已知字符串长度。但是，由于strlen()是函数，多多少少会有些慢，因为函数调用会经过诸多步骤，如字母小写化（译注：指函数名小写化，PHP不区分函数名大小写）、哈希查找，会跟随被调用的函数一起执行。在某些情况下，你可以使用isset() 技巧加速执行你的代码。
（举例如下）if (strlen($foo) < 5) { echo “Foo is too short” } （与下面的技巧做比较） if (!isset($foo{5})) { echo “Foo is too short” }
调用isset()恰巧比strlen()快，因为与后者不同的是，isset()作为一种语言结构，意味着它的执行不需要函数查找和字母小写化。也就是说，实际上在检验字符串长度的顶层代码中你没有花太多开销。
When incrementing or decrementing the value of the variable $i++ happens to be a tad slower then ++$i. This is something PHP specific and does not apply to other languages, so don’t go modifying your C or Java code thinking it’ll suddenly become faster, it won’t. ++$i happens to be faster in PHP because instead of 4 opcodes used for $i++ you only need 3. Post incrementation actually causes in the creation of a temporary var that is then incremented. While preincrementation increases the original value directly. This is one of the optimization that opcode optimized like Zend’s PHP optimizer. It is a still a good idea to keep in mind since not all opcode optimizers perform this optimization and there are plenty of ISPs and servers running without an opcode optimizer.
当执行变量$i的递增或递减时，$i++会比++$i慢一些。这种差异是PHP特有的，并不适用于其他语言，所以请不要修改你的C或Java代码并指望它们能立即变快，没用的。++$i更快是因为它只需要3条指令(opcodes)，$i++则需要4条指令。后置递增实际上会产生一个临时变量，这个临时变量随后被递增。而前置递增直接在原值上递增。这是最优化处理的一种，正如Zend的PHP优化器所作的那样。牢记这个优化处理不失为一个好主意，因为并不是所有的指令优化器都会做同样的优化处理，并且存在大量没有装配指令优化器的互联网服务
提供商（ISPs）和服务器。
有时候为了使 PHP 代码更加整洁，一些 PHP 新手（包括我）会把预定义好的变量复制到一个名字更简短的变量中，其实这样做的结果是增加了一倍的内存消耗，只会使程序更加慢。试想一下，在下面的例子中，如果用户恶意插入 512KB 字节的文字到文本输入框中，这样就会导致 1MB 的内存被消耗！
BAD: $description = $_POST['description']; echo $description; GOOD: echo $_POST['description'];
switch case好于使用多个if，else if语句,并且代码更加容易阅读和维护。
在可以用file_get_contents替代file、fopen、feof、fgets等系列方法的情况下，尽量用file_get_contents，因为他的效率高得多！但是要注意file_get_contents在打开一个URL文件时候的PHP版本问题；
(这好像不只是PHP里面要注意的问题吧？)；
（提到过echo 大变量的问题）
split() 0.001813 - 0.002271 seconds (avg 0.002042 seconds) explode() 0.001678 - 0.003626 seconds (avg 0.002652 seconds) Split can take regular expressions as delimiters, and runs faster too. ~23% on average.
以上都是关于php代码的优化，下面是从整体结构方面优化PHP性能：
1.将PHP升级到最新版
提高性能的最简单的方式是不断升级、更新PHP版本。
2.使用分析器
网站运行缓慢的原因颇多，Web应用程序极其复杂，让人扑朔迷离。而一种可能性在于PHP代码本身。这个分析器可以帮助你快速找出造成瓶颈的代码，提高网站运行的总体性能。
Xdebug PHP extension提供了强大的功能，可以用来调试，也可以用来分析代码。方便开发人员直接跟踪脚本的执行，实时查看综合数据。还可以将这个数据导入到可视化的工具 KCachegrind中。
3.检错报告
PHP支持强大的检错功能，方便你实时检查错误，从比较重要的错误到相对小的运行提示。总共支持13种独立的报告级别，你可以根据这些级别灵活匹配，生成用户自定义的检测报告。
4.利用PHP的扩展
Everyone has always complained that PHP content is too complex. In recent years, developers have made corresponding efforts to remove some redundant features in the project. Even so, the number of libraries and other extensions available is impressive. Some developers are even starting to consider implementing their own extensions.
5.PHP cache, use PHP accelerator: APC
Under normal circumstances, PHP scripts are compiled and executed by the PHP engine and will be converted into machine language, also known as is the operation code. If a PHP script gets the same result after compiling it over and over again, why not skip the compilation process completely?
You can achieve this through the PHP accelerator, which caches the machine code of the compiled PHP script. Allows code to be executed immediately upon request without going through a tedious compilation process.
For PHP developers, there are currently two available caching solutions. One is APC (Alternative PHP Cache, optional PHP cache), which is an open source accelerator that can be installed through PEAR. Another popular solution is Zend Server, which not only provides opcode caching technology, but also provides caching tools for corresponding pages.
6. Memory Cache
PHP usually plays an important role in retrieval and data analysis, and these operations may cause performance degradation. In fact, some operations are completely unnecessary, especially repeatedly retrieving some commonly used static data from the database. You may wish to consider using the Memcached extension to cache data in the short term. Memcached's extended cache works with the libMemcached library to cache data in RAM and also allows users to define the cache period, helping to ensure real-time updates of user information.
7.Content Compression：
Almost all browsers support Gzip compression method. Gzip can reduce the output by 80%. The cost is about a 10% increase in CPU calculations. But what you gain is that not only the bandwidth occupied is reduced, but your page loading will become faster, optimizing the performance of your PHP site.
You can turn it on in PHP.ini
zlib.output_compression = On
zlib.output_compression_level = (level) (level may be a number between 1-9, you can set different numbers to make it Suitable for your site. )
If you use apache, you can also activate the mod_gzip module, which is highly customizable.
8. Server cache:
Mainly based on the static servers nginx and squid based on web reverse proxy, as well as the mod_proxy and mod_cache modules of apache2
9. Database optimization: database cache, etc.
By configuring the database cache, such as turning on QueryCache cache, when the query receives a query that is the same as before, the server will retrieve it from the query cache. Results, instead of re-analyzing and executing the last query
and data storage procedures, connection pool technology, etc.
Related recommendations:
Sharing of PHP performance optimization tips
Detailed examples of PHP performance optimization
Five PHP performance optimization tips
The above is the detailed content of PHP performance optimization example sharing. For more information, please follow other related articles on the PHP Chinese website!