Commit: 87554f65236c7aa002ecddb02bcf9a1c786f1a75 Author: krakjoe <joe.watk...@live.co.uk> Tue, 27 May 2014 20:12:36 +0100 Parents: 836ba8e883166a51a363c69b8d4a61b5fd0a6237 Branches: master
Link: http://git.php.net/?p=web/php.git;a=commitdiff;h=87554f65236c7aa002ecddb02bcf9a1c786f1a75 Log: correct nikic's name 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 3230b61..a04650e 100644 --- a/archive/entries/2014-05-27-1.xml +++ b/archive/entries/2014-05-27-1.xml @@ -12,7 +12,7 @@ <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 Poppov. 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>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>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> -- PHP Webmaster List Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
