Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65831
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <7de2703f77537a47b457c4479a19ac3a@mail.gmail.com>
References: <e8aaa4ce59a801e53c6abc9d287d1859@mail.gmail.com>
	<511BFC81.8020400@oracle.com>
	<7de2703f77537a47b457c4479a19ac3a@mail.gmail.com>
Date: Thu, 14 Feb 2013 19:34:00 +0400
Message-ID: <CAOc_q_wT5Umo1c2C-H33+n79sBRa64a1BRZYh1bHj3NdRer7jg@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: Christopher Jones <christopher.jones@oracle.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Zend Optimizer+ Source Code now available
From: indeyets@gmail.com (Alexey Zakhlestin)

On Thu, Feb 14, 2013 at 7:21 PM, Zeev Suraski <zeev@zend.com> wrote:

> O+ does perform some optimizations in addition to caching code, in a pretty
> sophisticated manner actually (block optimizations).  Optimizations - which
> can be expensive to carry out - are definitely a good fit with an opcode
> cache, that ensures that you wouldn't have to do these optimizations more
> than once.  I'm obviously subjective but I think the name Optimizer+ does a
> good job at suggesting that it's both an Optimizer but also something else.
> Perhaps we should call it OptiCache? :)
>
>> Questions (I haven't dug through the code):
>>
>>   - What do CLI processes share?
>
> IIRC nothing, presently it's not very useful for CLI except for testing
> (it'll only apply to a single run).  I could be wrong though, Dmitry?

Well, if it does block-level optimizations, that is already enough to
make it useful for CLI-scripts, as even though caching is not relevant
for long-running processes, optimizations should make things faster.

Are optimizations documented?


-- 
Alexey Zakhlestin,
http://github.com/indeyets