On Fri, Aug 22, 2014 at 4:04 AM, Dmitry Stogov wrote:
> Hi,
>
> I'm going to commit this on next week, if nobody cares.
> MM is a self containing subsystem, and it must not affect anything else.
>
> Thanks. Dmitry.
I compared this to master on a small PHP array vs SplFixedArray
performance test I
Hi,
I'm going to commit this on next week, if nobody cares.
MM is a self containing subsystem, and it must not affect anything else.
Thanks. Dmitry.
On Mon, Aug 18, 2014 at 10:07 PM, Levi Morrison wrote:
> On Mon, Aug 18, 2014 at 12:04 PM, Nikita Popov
> wrote:
> > On Mon, Aug 18, 2014 at 7
On Mon, Aug 18, 2014 at 12:04 PM, Nikita Popov wrote:
> On Mon, Aug 18, 2014 at 7:59 PM, Levi Morrison wrote:
>>
>> On Mon, Aug 18, 2014 at 6:04 AM, Dmitry Stogov wrote:
>> > Hi,
>> >
>> > Please take a look into the proposed new Memory Manager for PHP:
>> >
>> > https://github.com/php/php-src/p
On Mon, Aug 18, 2014 at 7:59 PM, Levi Morrison wrote:
> On Mon, Aug 18, 2014 at 6:04 AM, Dmitry Stogov wrote:
> > Hi,
> >
> > Please take a look into the proposed new Memory Manager for PHP:
> >
> > https://github.com/php/php-src/pull/777
>
> It looks like the gains are mostly earned by passing
On Mon, Aug 18, 2014 at 6:04 AM, Dmitry Stogov wrote:
> Hi,
>
> Please take a look into the proposed new Memory Manager for PHP:
>
> https://github.com/php/php-src/pull/777
It looks like the gains are mostly earned by passing size information;
is that correct?
--
PHP Internals - PHP Runtime Dev
Hi,
Please take a look into the proposed new Memory Manager for PHP:
https://github.com/php/php-src/pull/777
The patch provides visible performance improvement on real life apps
(tested on Linux 32 and 64 bit). It's based on ideas mainly borrowed from
jemalloc and tcmalloc.
I hope, the patch mu
