Some small details you need to pay attention to to improve your PHP programming efficiency_PHP Tutorial

WBOY
Release: 2016-07-13 17:18:43
Original
761 people have browsed it

Paying attention to some small details will make your PHP run more efficiently


For example, when using echo to output, if the string uses single quotes, it will be more efficient than using double quotes, because PHP will search for variables in the string surrounded by double quotes, but single quotes will not. Note: Only echo can do this. It 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).
If you can define a class method as static (static variable), try to define it as static, and its speed will increase by nearly 4 times. (PS: T good php Q buckle: 304224365, verification: csl)


$row[’id’] is 7 times faster than $row[id].


echo is faster than print, and uses echo's multiple parameters (annotation: referring to commas instead of periods) instead of string concatenation, such as echo $str1,$str2.


Determine the maximum number of loops before executing the for loop. Do not calculate the maximum value every loop. It is best to use foreach instead.


Try to avoid using __get, __set, __autoload.


Unregister unused variables, especially large arrays, to free up memory.


require_once() is expensive.
Try to use absolute paths when including files, because it avoids the speed of PHP searching for files in include_path, and it takes less time to parse the operating system path.


If you want to know the time when the script starts executing (annotation: the server receives the client request), using $_SERVER[‘REQUEST_TIME’] is better than time().


Functions perform the same function instead of regular expressions.


The str_replace function is faster than the preg_replace function, but the strtr function is four times more efficient than the str_replace function.


If a string replacement function accepts arrays or characters as parameters, and the parameter length is not too long, then you can consider writing an additional piece of replacement code so that each parameter passed is a character, instead of just writing one line of code to accept the array as a query and replaced parameters.


Using switch case (select branch statement) is better than using multiple if, else if statements.


Using @ to block error messages is very inefficient, extremely inefficient.


Opening apache's mod_deflate module can improve the browsing speed of web pages.


The database connection should be closed when finished using it, and do not use long connections.


Error messages are expensive.


Incrementing local variables in methods is the fastest. Almost as fast as calling local variables in a function.


Incrementing a global variable is 2 times slower than incrementing a local variable.


Incrementing an object property (e.g. $this->prop++) is 3 times slower than incrementing a local variable.


Incrementing an undefined local variable is 9 to 10 times slower than incrementing a predefined local variable.


Simply defining a local variable without calling it in a function also slows things down (to the same extent as incrementing a local variable). PHP will probably check to see if a global variable exists.


The method calls appear to be independent of the number of methods defined in the class, as I added 10 methods (both before and after testing the method) and there was no change in performance.


Methods in a derived class run faster than the same method defined in a base class.


Calling an empty function with one argument takes as long as incrementing the local variable 7 to 8 times. A similar method call takes close to 15 local variable increment operations.


Apache parses a PHP script 2 to 10 times slower than parsing a static HTML page. Try to use more static HTML pages and less scripts.


Unless the script can be cached, it will be recompiled each time it is called. Introducing a PHP caching mechanism can usually improve performance by 25% to 100% to eliminate compilation overhead.


Try to cache as much as possible, you can use memcached. Memcached is a high-performance memory object caching system that can be used to accelerate dynamic web applications and reduce database load. Caching of OP codes is useful so that scripts do not have to be recompiled for each request.


When operating on a string and need to check whether its length meets certain requirements, you would naturally use the strlen() function. This function executes quite quickly because it does not do any calculations and just returns the known string length stored in the zval structure (C's built-in data structure used to store PHP variables). However, since strlen() is a function, it will be somewhat slow, because the function call will go through many steps, such as lowercase letters (Annotation: refers to the lowercase function name, PHP does not distinguish between uppercase and lowercase function names), hash search, Will be executed together with the called function. In some cases, you can use the isset() trick to speed up the execution of your code.
(Example below)
if (strlen($foo) (Compare with the tips below)
if (!isset($foo{5})) { echo “Foo is too short”$$ }
Calling isset() happens to be faster than strlen() because, unlike the latter, isset(), as a language construct, means that its execution does not require function lookups and lowercase letters. That is, you actually don't spend much overhead in the top-level code checking the string length.


When performing increment or decrement of variable $i, $i++ will be slower than ++$i. This difference is specific to PHP and does not apply to other languages, so please don't modify your C or Java code and expect it to be instantly faster, it won't work. ++$i is faster because it only requires 3 instructions (opcodes), while $i++ requires 4 instructions. Post-increment actually creates a temporary variable that is subsequently incremented. Prefix increment increases directly on the original value. This is a form of optimization, as done by Zend's PHP optimizer. It's a good idea to keep this optimization in mind because not all command optimizers perform the same optimizations, and there are a large number of Internet Service Providers (ISPs) and servers that do not have command optimizers installed.


Not everything has to be object-oriented (OOP), object-oriented is often expensive, and each method and object call consumes a lot of memory.


Not all data structures need to be implemented in classes; arrays are also useful.


Don't break down the methods too much. Think carefully about which code do you really intend to reuse?


You can always break the code into methods when you need to.


Try to use a large number of PHP built-in functions (but in order to find a function that does not exist in PHP, I wasted time that could have been written a custom function, a matter of experience!);.


If there are a lot of time-consuming functions in your code, you might consider implementing them as C extensions.


Profile your code. The checker will tell you which parts of the code take how much time. The Xdebug debugger includes inspection programs that evaluate the overall integrity of your code and reveal bottlenecks in your code.


mod_zip can be used as an Apache module to instantly compress your data and reduce data transfer volume by 80%.


When file_get_contents can be used instead of file, fopen, feof, fgets and other series of methods, try to use file_get_contents because it is much more efficient! But please pay attention to the PHP version problem of file_get_contents when opening a URL file;


Conduct file operations as little as possible, although PHP’s file operations are not inefficient;


Optimize the Select SQL statement and perform as few Insert and Update operations as possible (I was criticized for updating);


Do not declare variables inside the loop, especially large variables: objects (this seems to be not just a problem in PHP?);


Try not to nest assignments in loops for multi-dimensional arrays;


Don’t use regular expressions when you can use PHP’s internal string manipulation functions;


foreach is more efficient, try to use foreach instead of while and for loop;


"Replace i=i+1 with i+=1. It conforms to the habits of c/c++ and is more efficient";


Global variables should be unset()ed after use;

www.bkjia.comtruehttp: //www.bkjia.com/PHPjc/621638.htmlTechArticlePaying attention to some small details will make your PHP run more efficiently. For example, when using echo output, if the string uses Single quotes will be more efficient than using double quotes, because PHP will package...
Related labels:
source:php.cn
Statement of this Website
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
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template