php/archived-web-php
1
0
Fork 0
mirror of https://github.com/php/web-php.git synced 2026-03-23 23:02:13 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' of git://git.php.net/web/php

Browse Source 
* 'master' of git://git.php.net/web/php:
  correct nikic's name
  add short entry regarding the existence of phpng
This commit is contained in:
Levi Morrison
2014-05-27 13:19:48 -06:00
parent 78286b7a10 87554f6523
commit 95a54dacca
1 changed files with 21 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
archive/entries/2014-05-27-1.xml Normal file
View File

@@ -0,0 +1,21 @@
<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom">
<title>PHP Next Generation</title>
<id>http://php.net/archive/2014.php#id2014-05-27-1</id>
<published>2014-05-27T17:28:16+00:00</published>
<updated>2014-05-27T17:28:16+00:00</updated>
<category term="frontpage" label="PHP.net frontpage news"/>
<link href="http://php.net/index.php#id2014-05-27-1" rel="alternate" type="text/html"/>
<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>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>
</div>
</content>
</entry>