Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71135
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zend.com from 74.125.82.41 cause and error)
MIME-Version: 1.0
In-Reply-To: <a096a68ab53e646135930bb1a9c5b68b.squirrel@webmail.klapt.com>
References: <CA+9eiLtmUgWSZhoHgXy+UfiakGHG5RuJwP6o4txVsU76fRsDpQ@mail.gmail.com>
	<a096a68ab53e646135930bb1a9c5b68b.squirrel@webmail.klapt.com>
Date: Wed, 15 Jan 2014 12:56:35 +0400
Message-ID: <CA+9eiLvbHPRa=R9u2g=X2kKZsAkdOXiYE2NuNVe3hNVM-e_jog@mail.gmail.com>
To: Anatol Belski <ab@php.net>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0149460272739604effe7c11
Subject: Re: [PHP-DEV] New Memory Manager
From: dmitry@zend.com (Dmitry Stogov)

--089e0149460272739604effe7c11
Content-Type: text/plain; charset=UTF-8

Hi Anatol,

It's a Prove of Concept implementation.
I publish it to decide if it makes sense to integrate it into PHP and
implement support for missed things or just forget.
As I wrote, at this moment, it supports only Linux, non-zts, release build.

Thanks. Dmitry.




On Wed, Jan 15, 2014 at 12:44 PM, Anatol Belski <ab@php.net> wrote:

> Hi Dmitry,
>
> On Tue, January 14, 2014 15:21, Dmitry Stogov wrote:
> > Hi,
> >
> >
> > Recently I took a look into jemalloc and tcmalloc internals and tried to
> > borrow some ideas. You may check the result at
> > https://github.com/dstogov/php-src/tree/xx_malloc. It's a dirty prove of
> > concept implementation of New Memory Manager for PHP. It was tested only
> > on Linux, release, non-ZTS build. It misses support for debug mode and
> ZTS
> >  yet. The main advantage is small but consistent speed improvement on
> > real-life applications.
> >
> i've just gave it a try on windows, the compilation breaks with this error
>
> zend\xx_malloc.c(41) : fatal error C1083: Cannot open include file:
> 'sys/mman.h': No such file or directory
>
> Google gave me this link
> https://code.google.com/p/mman-win32/source/browse/trunk/ . I can go for a
> fix using this lib or maybe look for another equivalent after the
> str_size_and_int64 RFC finish.
>
> Regards
>
> Anatol
>

--089e0149460272739604effe7c11--