Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66376
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAAyV7nF=nOGzG+Y1nv8sL8g34p4iVJrdd31GT8UHM3MnD9VViQ@mail.gmail.com>
References: <435a322ccb14090d3bcf6bf8a110396d@mail.gmail.com>
 <CAF+90c-FeWE960EJsvpdNu+CpCOyK84=mTyfH_vgUzPRSmD7gA@mail.gmail.com>
 <3206872690693024300@unknownmsgid> <CAAyV7nH9jafLksLG105sySTzVZmWCFJ6D-4nE6CFAxU1rF9kpg@mail.gmail.com>
 <512FBDCD.3030507@lerdorf.com> <CAA9esyS48hze6_39bu_P22TP=mtVm-wzTKKRrpABwmhv99=ohg@mail.gmail.com>
 <CAFMT4NqHwSHwpN6NZHK2fQPjTFSdCZqYX5=f5cqk0DBrLXkUTw@mail.gmail.com>
 <CAA9esyS-Eu2=s66r8YC1nmE0TtOSOW0xv_MebpaV-YYKm4y2uA@mail.gmail.com> <CAAyV7nF=nOGzG+Y1nv8sL8g34p4iVJrdd31GT8UHM3MnD9VViQ@mail.gmail.com>
Date: Fri, 1 Mar 2013 00:00:49 +0200
Message-ID: <CAA9esyQLnfOz01PwMnvXDy_epi3N5Ju54pDSTzGimyg9reajgw@mail.gmail.com>
To: Anthony Ferrara <ircmaxell@gmail.com>
Cc: Levi Morrison <morrison.levi@gmail.com>, Rasmus Lerdorf <rasmus@lerdorf.com>, 
	Zeev Suraski <zeev@zend.com>, Nikita Popov <nikita.ppv@gmail.com>, 
	PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP distribution
From: florinpatan@gmail.com (Florin Razvan Patan)

On Thu, Feb 28, 2013 at 11:47 PM, Anthony Ferrara <ircmaxell@gmail.com> wrote:
> Florin
>
>> Would you run PHP against 10k+ req/s in production without opcode caching?
>> On how many machines without / with?
>
>
> I'm not sure about your stack, but every stack I've seen at that high of a
> load is built very custom for the problem at hand. And it isn't typically
> upgraded across minor versions (in fact, it's typically only upgraded for
> security). At least that's my experience everywhere I've seen that big of a
> farm... And when it is upgraded, it's usually a very coordinated effort that
> takes a LOT of planning and has a lot of moving parts...
>
> And to be fair, how many installs are there that get 10k req/s? A few
> hundred? That's not the kind of system we should be targeting when
> discussing a language feature/change. Sure it's sexy, but it represents less
> than 1% of the install base of PHP (much less, prob on the order of 0.01%).
> So while I wouldn't write them off (far from it), justifying a change
> because it matters to that scale is like justifying ejection seats in cars
> because hitting a wall at 200mph on a race track can kill you...
>
>

Anthony and Levi,


True but could we please get back to the whole mail and actually see
what the users want?

I would vote in the RFC if would be allowed to do so and I think I've
explained my perspective really well and the fact that I'm just one of
the hundred of thousands of PHP users.

I'm part of a very small group of people who have these problems, I
agree, but what I'm proposing should help out instead of just assuming
things.

The point is that this is yet another: we should this but that but
then and what if ... that could be solved by just asking the users and
taking that into account.

I could bet that people could care less about a stable release cycle
when things like this are at stake for certain versions.

Also, as a mention, I think that the current release every year target
is highly unrealistic unless you want to fragment the market the same
way that Google does it with Android. And look at the problems they
have with the adoption. If they can't serve as an example, I don't
know how can. Especially with PHP 5.4 experience. Are you willing to
bet that PHP 5.5 will do any better?



Best regards
----
Florin Patan
https://github.com/dlsniper