From the code level, low code quality will also have a great impact on execution efficiency.
In terms of hardware, the server configuration is low, and the server configuration is the basis. If it cannot run, it will definitely be slow.
In terms of data volume, the amount of query data is too large, the SQL statements are too complex, and the execution is slow.
Improvements in configuration are quite obvious for the overall execution efficiency of the system. There is nothing to question about this, as long as you have the strength , naturally we can make more improvements in this aspect.
The optimization of this query involves sql optimization or database optimization. There are several simple optimization plans below.
SQL optimization, use linked list query appropriately, and use connection (JOIN) instead of subquery. Generally, avoid using JOIN in the case of large tables and multiple tables. In this case, using JOIN will be the opposite. It cannot achieve the effect of simplifying the query.
#SQL optimization, when querying table data, query the exact field name to avoid unnecessary field queries.
#SQL optimization, use primary foreign keys and indexes appropriately.
#SQL optimization, use in query appropriately and fuzzy query appropriately.
···········
Database optimization, fields use reasonable field types, another way to improve efficiency is to use it when possible Next, you should try to set the field to NOTNULL to avoid wasting space.
Optimization of database and reasonable design of table structure.
··········
Code optimization also varies from person to person, and everyone may Different coding habits and styles have different opinions on improving code performance. Here are some of my views.
Use foreach reasonably and try to use loops within loops as little as possible. If there are too many loops, it will be very performance-intensive.
During the loop, try to avoid data operations, especially query operations. When there are too many loops, the efficiency of multiple calls is very low. You can obtain the data once and then splice it. .
Similarly, in the loop, avoid multiple acquisitions of the configuration and calls to the time() function method. This single declaration can be used repeatedly.
In php, there is a difference between single quotes and double quotes. As a habit, I use single quotes for strings because it does not require compilation. For efficiency, it may I can’t talk about the size of the difference, maybe just a little
Make reasonable use of the functions in php, such as array functions, which are very rich. Make full use of them. Generally, don’t do them yourself. The function methods it supports
can use the concept of dictionary to store the array in the form of a new index. I often use it in data reorganization
According to the scenario, reasonable use of cache can reduce repeated data queries and improve efficiency
Reasonably split functions, such as a list query, and With detailed view, this can be split into two interface implementations to obtain data when needed and reduce resource waste.
Related recommendations:
The reason why PHP’s fsockopen method is slow to access the interface and the optimization plan
PHP efficiency Common methods of improvement and optimization
php code optimization methods, summary of techniques to speed up running speed
The above is the detailed content of Reasons for PHP's slow interface execution efficiency and optimization solutions. For more information, please follow other related articles on the PHP Chinese website!