com web/php: changes to wording: archive/entries/2014-05-27-1.xml

Commit: 92ff984bfb5ab7707f095a6636ba563b2f6d695e Author: krakjoe <joe.watkins@live.co.uk> Tue, 27 May 2014 20:46:30 +0100 Parents: 0e6e8d2c1b3feb2254e1d9f0874d4021b562dd75 Branches: master Link: http://git.php.net/?p=web/php.git;a=commitdiff;h=92ff984bfb5ab7707f095a6636ba563b2f6d695e Log: changes to wording Changed paths: M archive/entries/2014-05-27-1.xml Diff: diff --git a/archive/entries/2014-05-27-1.xml b/archive/entries/2014-05-27-1.xml index a04650e..9c60cb9 100644 --- a/archive/entries/2014-05-27-1.xml +++ b/archive/entries/2014-05-27-1.xml @@ -9,10 +9,10 @@ <link href="http://php.net/archive/2014.php#id2014-05-27-1" rel="via" type="text/html"/> <content type="xhtml"> <div xmlns="http://www.w3.org/1999/xhtml"> - <p>When we aren't looking for pictures of kittens on the internet, internals developers are nearly always looking for ways to improve PHP, Zend, and a few developers besides have a focus on performance.</p> - <p>Over the last year, Zend have been researching the possibility of adding JIT compilation capabilities to the Zend Engine.</p> - <p>During this time, the realization was made that in order to achieve optimal performance from the Zend Engine, some internal API's should be changed.</p> - <p>This necessitated the birth of the phpng branch, authored by Dmitry Stogov (from Zend), Xinchen Hui, and Nikita Popov. This branch does not include JIT capabilities, but rather seeks to solve those problems that prohibit the current, and any future implementation of a JIT capable executor achieving optimal performance by improving memory usage and cleaning up some core API's.</p> + <p>When we aren't looking for pictures of kittens on the internet, internals developers are nearly always looking for ways to improve PHP, a few developers have a focus on performance.</p> + <p>Over the last year, some research into the possibility of introducing JIT compilation capabilities to PHP has been conducted.</p> + <p>During this research, the realization was made that in order to achieve optimal performance from PHP, some internal API's should be changed.</p> + <p>This necessitated the birth of the phpng branch, authored by Dmitry Stogov, Xinchen Hui, and Nikita Popov. This branch does not include JIT capabilities, but rather seeks to solve those problems that prohibit the current, and any future implementation of a JIT capable executor achieving optimal performance by improving memory usage and cleaning up some core API's.</p> <p>In solving these problems, the phpng branch gives us a considerable performance improvement in real world applications, for example a 20% increase in throughput for Wordpress. The door may well now be open for a JIT capable compiler that can perform as we expect, but it's necessary to say that these changes stand strong on their own, without requiring a JIT capable compiler in the future to validate them.</p> <p>The name "Next Generation" was optimistically presumptuous, which we all like, in reality phpng is an internal project that we are working on, it is not a production ready branch that anyone should deploy, or judge as they would a release of PHP.</p> <p>The work on phpng, the doors it opens, the conversations it has started, the collaboration it is inspiring, are all worth getting excited about. But, we need to stay grounded, honest, and open; and say that there is much work to do in order to make the "Next Generation" a reality, this is only the start.</p>