Since the birth of PHP in 1994, PHP language has experienced many improvements, among which performance is one of the main criteria that developers consider when evaluating new versions.
Let’s not mention the previous version for the time being. Let’s talk about the current version of php7.3. We all know that when PHP 7 was released, it was claimed to be twice faster than php5.6. How about the performance of php7.3?
Phoronix conducted a benchmark test when PHP 7.3 alpha 1 was released. The results showed that in the commonly used phpbench benchmark (below), PHP 7.3.0 alpha 1 was about 7% faster than the previous stable version of PHP 7.2, and 22% faster than PHP 7.0;
It can be said that the performance of php7.3 has reached a certain level, but in fact, these optimizations seem to have reached the limit. Now JIT starts from the bottom and is considered to be the best way to improve the performance of PHP. The official vote on whether php8 should be introduced into JIT was announced on the 1st of this month, because some big guys (including bird Brothers) voted for it!
According to the official statement: PHP JIT may not be obvious for websites using PHP, because JIT works best on CPU intensive code, so the JIT role of php8 is mainly to play in the field of mathematics.
In general, programs written in PHP are I / O intensive. In people’s words, PHP programs are often limited by I / O rather than CPU. The factors that slow down the running speed of PHP code are the I / O operations they are performing, including connection, reading and writing to database, cache, file and socket, etc.
At this time, the emergence of swote is just to solve the IO intensive problem. It has the advantages of permanent memory, avoiding performance loss caused by repeated loading, improving massive performance, asynchronous coroutine, improving concurrent processing ability of I / O intensive scenes (such as Baidu map, baidu order center, tiger tooth live broadcast, etc.); it is convenient to develop HTTP, websocket, TCP and UDP So PHP can also use the high-performance swoft microservice architecture to redefine PHP!
It is not necessary for advanced programmers to master PHP and PHP, but it is necessary for advanced programmers to master this knowledge!
I hope the above can help you,Many PHPer will encounter some problems and bottlenecks when they are advanced. There is no sense of direction when writing too much business code, and I don’t know where to start to improve. For this, I have sorted out some data, including but not limited to: distributed architecture, high scalability, high performance, high concurrency, server performance tuning, tp6, laravel, redis, swote, swoft, Kafka, MySQL optimization, shell feet This, docker, microservice, nginx and other knowledge points can be shared with you for freeYou need to poke it herePHP advanced architect > > > practical video and interview document for free