Slashdot Mirror
PHP 7.3 Performance Benchmarks Are Looking Good Days Ahead Of Its Release (phoronix.com)
PHP 7.3 RC6 was released earlier this week. Phoronix ran some benchmarks and compared the performance of v7.3 RC6 with releases going back to the v5.5 series. From the story: I ran some fresh benchmarks over the past day on PHP 5.5.38, PHP 5.6.38, PHP 7.0.32, PHP 7.1.24, PHP 7.2.12, and the PHP 7.3.0-RC6 test release. All of the PHP5/PHP7 builds were configured and built in the same manner. All tests happened from the same Dell PowerEdge R7425 dual EPYC server running Ubuntu 18.10 Linux.
Besides continuing to evolve the performance of PHP7, the PHP 7.3 release is also delivering on FFI (the Foreign Function Interface) to access functions / variables / data structures from the C language, a platform-independent manner for obtaining information on network interfaces, an is_countable() call, WebP support within GD's image create from string, updated SQLite support, improved PHP garbage collection performance, and many other enhancements. PHP 7.3 is just shy of 10% faster than PHP 7.2 in the popular PHPBench. PHP 7.3 is 31% faster than PHP 7.0 or nearly 3x the speed of PHP5.
Besides continuing to evolve the performance of PHP7, the PHP 7.3 release is also delivering on FFI (the Foreign Function Interface) to access functions / variables / data structures from the C language, a platform-independent manner for obtaining information on network interfaces, an is_countable() call, WebP support within GD's image create from string, updated SQLite support, improved PHP garbage collection performance, and many other enhancements. PHP 7.3 is just shy of 10% faster than PHP 7.2 in the popular PHPBench. PHP 7.3 is 31% faster than PHP 7.0 or nearly 3x the speed of PHP5.
Who cares? It is convenient and flexible, it offers a lot of control and it works well.
While this all makes sense, my problem with PHP ain't CPU burn, it's memory usage. What I need from my PHP CMS is for it to use less RAM, not for it to use less CPU. CPU is cheap, RAM ain't.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
I tried to come up with a more balanced view on PHP, synthesizing Eevee's popular "fractal" essay, ManiacDan's "hardly" rebuttal, and Douglas Crockford's JavaScript: The Good Parts, to form coding standards and things that are still broken.