Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84037
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAAyV7nHpf8JT0nAF-M9d-65JQHDbYnK7F+c9CUtoyLkkfRiROg@mail.gmail.com>
References: <CA+9eiLv+HzuLrECzV37Q1mnNCGNbUj1OocCH3Q7b7PSyWBPtfg@mail.gmail.com>
	<CAAyV7nF53g0wt9Gva5MwULvHDxrqNhLQJMsNTiLP2m0wOAHJkg@mail.gmail.com>
	<ABB24B2E-9456-485E-8510-941076AAAD77@zend.com>
	<54F08FF3.3040404@seld.be>
	<CA+9eiLumXUD6SowadcfcbtzKYT96ut9fFt-fy5afrGOU1rZhSA@mail.gmail.com>
	<CAAyV7nFF_F+k-9cWqSrLp1vUY+GWxqKqfH6ABZZovZj9d4o8jw@mail.gmail.com>
	<CA+9eiLvZW-myYa9TW6Q0rhLbFRQNLq3iH16FHVyzeThdCUgvGA@mail.gmail.com>
	<63262a9c0edd51bbf38df2a00c87340e@mail.gmail.com>
	<CAAyV7nHpf8JT0nAF-M9d-65JQHDbYnK7F+c9CUtoyLkkfRiROg@mail.gmail.com>
Date: Fri, 27 Feb 2015 23:20:44 +0400
Message-ID: <CA+9eiLsa6UpK_e_tRESS6MvXYpbJcFo+Oqd0CC4gByPVNzXNJA@mail.gmail.com>
To: Anthony Ferrara <ircmaxell@gmail.com>
Cc: Zeev Suraski <zeev@zend.com>, Jordi Boggiano <j.boggiano@seld.be>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0115f048da5fdb051016c386
Subject: Re: [PHP-DEV] Re: Zend JIT Open Sourced
From: dmitry@zend.com (Dmitry Stogov)

--089e0115f048da5fdb051016c386
Content-Type: text/plain; charset=UTF-8

On Fri, Feb 27, 2015 at 9:55 PM, Anthony Ferrara <ircmaxell@gmail.com>
wrote:

> Zeev,
>
> >> Right now it compiles script (php file) at once.
> >> So yes, our JIT uses some kind of AOT approach, but completely
> >> transparently for the rest of PHP.
> >
> > Just to slightly further clarify - we don't compile the whole codebase at
> > once, but we keep the existing semantics that every file is independent,
> may
> > change independently of other files, and include() may end up load one
> file
> > in one flow and another one in another flow.  There's isn't any
> cross-file
> > optimization.
> >
> >> We also tried few different approaches to collect formation about hot
> >> functions and generate code only for them.
> >> Unfortunately, this didn't change the picture.
> >
> > (again, the picture being no performance gains in common Web apps).
>
> Well, I just want to make one clarification here to your point:
> there's no performance gains to this AOT approach for common web apps.
>
> It's not really fair to judge a true JIT implementation based on this
> because it lacks crucial runtime information that a real JIT compiler
> would have (such as input types, values, etc). So it would be left
> generating generic native code instead of specific code. I just want
> to point out that the results here aren't really applicable to a JIT
> approach. And that should be made clear when discussing it.
>

Nobody talk about JIT in general, only about this PoC.
And yes, some other approaches may provide better gain.
At least I think so.
However, we may just guess, until implement them.


> That's not to say there's anything wrong with this approach, nor that
> there isn't a ton we can learn from it. I think it's a fantastic
> research effort and plan on digging through it myself. Thank you for
> open sourcing it.
>

Thanks for good words :)

This work may be adopted for some specific cases.
25-30 times speedup on Mandelbrot allows usage for numeric calculation
instead of C.

https://gist.github.com/dstogov/12323ad13d3240aee8f1

anyone may repeat the language battle :)

Thanks. Dmitry.


>
> Anthony
>

--089e0115f048da5fdb051016c386--