Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95426
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain mudsite.com designates 209.85.217.171 as permitted sender)
MIME-Version: 1.0
References: <CADVQu1QXag1h_hnOcFYejMbsDrV+4ZQCwKNJmb4EedBB6S33Ww@mail.gmail.com>
 <b26cbcf7-191d-10d2-5ea0-c9982c44592e@pascal-martin.fr>
In-Reply-To: <b26cbcf7-191d-10d2-5ea0-c9982c44592e@pascal-martin.fr>
Date: Wed, 24 Aug 2016 14:58:34 +0000
Message-ID: <CADVQu1TAfk78AeMnG4jy+gZXQ+hgFuRGO4hVWC085-8b5i3LJg@mail.gmail.com>
To: "Pascal MARTIN, AFUP" <mailing@pascal-martin.fr>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a114e51d6959516053ad28446
Subject: Re: [PHP-DEV] [RFC][VOTE] E_WARNING on invalid container read-adccess
From: dave+php@mudsite.com (David Walker)

--001a114e51d6959516053ad28446
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Internals,

My original time for vote ending was yesterday, however Yasuo requested I
provide some benchmarking stats to see performance impact.  I apologize I
wasn't able to provide the information sooner, I was off getting married.
I'd like to extend the vote through Sunday evening in the event anyone had
reservations based on potential performance impact.  The RFC is currently
sitting 15-0 in favor.

(added to RFC)
Execution Time (DualCore 3ghz; 2g ram)
  * Current Master : ~0.09s (~489k operations)
  * Current Master w/RFC Displaying Warnings: ~33.25s
  * Current Master w/RFC Hiding Warnings: ~0.82s (~4.091m operations)

We can see there is a significant increase in operations on huge loads.
However, I wouldn't suspect 1m of these errors per request almost ever.
So, yes there is; but I'd call it useful information overhead.

--
Dave

On Tue, Aug 23, 2016 at 12:50 PM Pascal MARTIN, AFUP <
mailing@pascal-martin.fr> wrote:

> Le 16/08/2016 =C3=A0 17:55, David Walker a =C3=A9crit :
> > I'd like to go ahead and open up the RFC to voting to the scope
> > that it is written.
>
> Hi,
>
> At AFUP, we would be +1 on this RFC.
>
> Basically: it could/will help detect problems, and the behavior change
> should not cause too many bc-breaks (actually, when it does cause some,
> it'll - probably - mostly be by detecting problems/bugs).
>
> Thanks for your work on this!
>
> --
> Pascal MARTIN, AFUP - French UG
> http://php-internals.afup.org/
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001a114e51d6959516053ad28446--