What’s in store for PHP performance?

PHP 7.0 made significant improvements in terms of performance and memory use for real applications. Many applications deliver twice the throughput with much less memory just without any changes to the application code.

But with networked API driven architectures individual response times are increasingly critical for end-user experience. Luckily, there are quite a few unbeaten paths for regarding PHP performance.

As web application architectures increasingly move toward microservices (over HTTP or WebSockets) that communicate through the network, response time grows in importance. As an external API powered application is only as fast as the lowest common denominator, developers need to focus on response time (milliseconds for response), instead of just thoughput (request/second) — the norm for benchmarks.

PHP itself can be scaled horizontally quite easily due to it’s shared-nothing architecture, which allows you to just add more nodes to deliver ever higher thoughput. Optimising for minimum response time is not so easy as CPUs simply don’t get exponentially faster these days.

PHP 7 improves response times significantly, as the recent example graph from Dailymotion’s PHP 7 upgrade shows:

In addition there are methods developers can use intermediary technologies such as a dumb data pump written in PHP, JavaScript, Go or something else in front of a complex application to access a dumbed-down data source for faster response times.

Async just means less waiting (for nothing)


Originally published at laravelfeed.com.