Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65358
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAA9esySzjXeeQ1RWWB96JN7YhRtr7Y4cQET2wu4j1yjy=vk6yA@mail.gmail.com>
References: <5d21b42656d49b4a71d9f808541bd745@mail.gmail.com>
	<CAA9esySzjXeeQ1RWWB96JN7YhRtr7Y4cQET2wu4j1yjy=vk6yA@mail.gmail.com>
Date: Tue, 29 Jan 2013 12:32:18 +0100
Message-ID: <CAH-PCH7WGkquQBcdY=GeYyvXsL0wLA0S=_EafMczXyZkAA-c_A@mail.gmail.com>
To: Florin Razvan Patan <florinpatan@gmail.com>
Cc: Zeev Suraski <zeev@zend.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=e89a8f3bb01f07122604d46bbf9f
Subject: Re: [PHP-DEV] [RFC] Integrating Zend Optimizer+ into the PHP distribution
From: tyra3l@gmail.com (Ferenc Kovacs)

--e89a8f3bb01f07122604d46bbf9f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 29, 2013 at 11:26 AM, Florin Razvan Patan <florinpatan@gmail.co=
m
> wrote:

> Thank you for this great initiative!
>
> As a user, I could definitely wait for 2-3 more months and get
> a good implementation/integration of this rather that have to
> wait for at least one year.
>
> I think it would also be nice if this could come as default
> enabled since this way people would be able to notice the
> advantages of having it enabled. Or you can run a survey on
> php.net to see what are the options.
>
> I do have one thing to ask you about this.
>
> If we do wait 2 months, will the underlaying changes be able
> to integrate easy with APC/XCache/eAccelerator/others?
>
> Opcodes are a must for large traffic websites like those I'm
> working on right now, so we clearly want to have such a thing
> installed on our servers as soon as we install a new PHP
> version. But if including O+ will mean that APC gets delayed
> 6+ months (see PHP 5.4) it would be a show stopper for us
> upgrading to PHP 5.5.
>
> Our upgrade process is like this: be at least one year on market
> to iron out major/obvious bugs. If APC gets on the market 6
> months after PHP 5.5 only because of this then we'll be near
> PHP 5.6 by then. And we can't just change from APC to others
> as we'll need to test them as well as see which other use data
> caching like APC has.
>
> It would make sense to actually see how the whole ZE can
> be improved so that it makes life of opcode cachers easier
> and then ship O+ bundled with a PHP version that has better
> support for them out of the box if I were to choose.
>
>
>
please don't top on this list, we prefer bottom or inline posting around
here, see http://www.php.net/reST/README.MAILINGLIST_RULES
back to the topic: personally I think that even two months seems like a
tight schedule as we are talking about incorporating an opcode cache, which
I'm pretty sure that it is similar in complexity to apc, and are only like
a handful of people on the planet has any experience working with, and
needs some polishing and has at least one known shortcoming (thread safety)=
.
my opinion is that we should wait for the code to be released before
thinking about the release dates.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--e89a8f3bb01f07122604d46bbf9f--