Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76291
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.172 as permitted sender)
MIME-Version: 1.0
Sender: laruence@gmail.com
In-Reply-To: <CC.52.08276.5963AD35@pb1.pair.com>
References: <25.82.08559.C1852D35@pb1.pair.com> <CABBJUpfb0MejZQfvofuS072ooMOisyu+pYU3LYXENPVRdM8rsQ@mail.gmail.com>
 <CC.52.08276.5963AD35@pb1.pair.com>
Date: Thu, 31 Jul 2014 22:23:33 +0800
Message-ID: <CABBJUpcNB+9aaDB5jHbeQnvYgRWObbapdWZqieU+LqgQ_GRzfg@mail.gmail.com>
To: Pascal Chevrel <pascal.chevrel@free.fr>, Dmitry Stogov <dmitry@zend.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Reporting bugs for phpng
From: laruence@php.net (Laruence)

Hey:

On Thu, Jul 31, 2014 at 8:29 PM, Pascal Chevrel <pascal.chevrel@free.fr> wr=
ote:
> Le 26/07/2014 04:42, Laruence a =C3=A9crit :
>
>> Hey:
>>
>> On Fri, Jul 25, 2014 at 9:14 PM, Pascal Chevrel <pascal.chevrel@free.fr>
>> wrote:
>>>
>>> Hi,
>>>
>>> I tried the .deb package for phpng that Zend provides since yesterday
>>> (thanks for that!) and I hit a memory consumption issue with the first =
of
>>> my
>>> scripts I tried:
>>>
>>> PHPNG:
>>> Memory peak: 62914560 (55.97MB)
>>> Elapsed time (s): 0.3383
>>>
>>> PHP 5.5:
>>> Memory peak: 1835008 (1.64MB)
>>> Elapsed time (s): 0.0717
>>>
>>> How/where can I make a bug report about it? Is https://bugs.php.net/ ok
>>> for
>>> PHPNG bugs?
>>
>>   PHPNG is not listed in bugs.php.net yet. but as it's a branch of PHP
>> , I think it's okey to report it there, and note it's PHPNG in the
>> comment. for now.
>>
>> thanks
>
>
> Hi,
>
> I opened this bug:
> https://bugs.php.net/bug.php?id=3D67725
>
> I put a testcase triggering the memory leak in a github repo referenced i=
n
> the bug.
I am afraid this is not a bug.

it's due to our new immutable array implementation.

all these langs map array are constant array, such it will be treat as
immutable array, which means it will not be released untill the
request shutdown. (which will bring significant performance
improvement for saving array construct/destruct while use with
opcache)

I suggest you to increase the memory_limit as a workaround ..

Anyway, Dmitry, what do you think?  maybe something like interned_string_si=
ze?

thanks
>
> Regards
>
>
> Pascal
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>



--=20
Laruence  Xinchen Hui
http://www.laruence.com/