Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67028
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain zend.com does not designate 209.85.215.47 as permitted sender)
References: <CA+9eiLsjK0wTT4L0UN9uJdSJgO8se3YDebZwSHycrqAJswJufQ@mail.gmail.com>
 <CAL0xaBECR92ur0SDVZzYyh23+d-UnBE+DUjqkEAJZ=1EtUyNTQ@mail.gmail.com> <CAA9esyQg1trZcmr-7oR05eTGr87kDm4nHLXsvHnc983Ei=tNmg@mail.gmail.com>
In-Reply-To: <CAA9esyQg1trZcmr-7oR05eTGr87kDm4nHLXsvHnc983Ei=tNmg@mail.gmail.com>
MIME-Version: 1.0
Thread-Index: AQFVPpSNbOGMJmTVWXvN9y+HxauxBwDgUUw9ATMC2FqZsMQW8A==
Date: Wed, 10 Apr 2013 16:22:14 +0300
Message-ID: <54fcf4b0bdf8a7d5d335f2e64498d529@mail.gmail.com>
To: Florin Patan <florinpatan@gmail.com>, Arvids Godjuks <arvids.godjuks@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: RE: [PHP-DEV] OPcache optimizer improvement in PHP-5.5?
From: zeev@zend.com (Zeev Suraski)

> If applying optimizations in multiple passes would be a problem for speed,
> especially on the first request, then maybe a way to solve this would be
> to have
> a configurable variable like: opcache.passes which is between 1 and 10
> (lets say)
> and then have the engine do something like
> this:

My gut/educated guess is that in fact it's not going to be a problem with
the kinds of optimizations that are practical for our execution engine (our
ability to be ultra-creative with optimizations is very limited, compared to
say gcc).  I'd defer solutions to that problem until we actually see that
it's a real problem to begin with.  Generally, the book-keeping involved
with selectively and intelligently applying optimizations is probably going
to be more costly than doing them in the first place - but that obviously
depends on the nature of optimizations we'll come up with.

Zeev