Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25375
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Zwiv3hG7yb6N+F99OjTvAkjCuhleZpA+fYvf46qbJPDNuyqvWhpLI08b1zLnIqf2ELUYyZHwvmq+jBDzVxEJ5VpLuA+hwVPm1cT4F65MnMQsHFPNUg56TVl/gsg7p1XgwDIjcNU+HnVhwMY2p57r6GWmysPN04+6zmeCqfZlOO4=
Message-ID: <fe05d1540608160434k7bdeda87t97112e9de745c821@mail.gmail.com>
Date: Wed, 16 Aug 2006 13:34:38 +0200
To: toggg@php.net
Cc: "Antony Dovgal" <antony@zend.com>, internals@lists.php.net
In-Reply-To: <44E30193.8090708@php.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20060816123006.4028b334@pierre-u64> <44E2FDC8.2020503@toggg.com>
	 <44E2FE2A.1000500@zend.com> <44E30193.8090708@php.net>
Subject: Re: [PHP-DEV] Re: increase the default memory limit in 5.2.0+
From: pierre.php@gmail.com (Pierre)

Hello,

On 8/16/06, bertrand Gugger <toggg@php.net> wrote:
> Antony Dovgal wrote:
> > On 16.08.2006 15:13, bertrand Gugger wrote:
> >
> >> Bonjour,
> >> Pierre wrote:
> >>
> >>> Hello,
> >>>
> >>> After having tested 5.2 and the new memory manager for a couple of
> >>> weeks, I notice a significant increase of the reported memory usage. As
> >>> a side effect, many applications reach the 8M memory limit. It can be
> >>> a problem.
> >>>
> >>> A good example is to compare the usage of a pear/pecl command between
> >>> 5.1 and 5.2.
> >>>
> >>> I would suggest to increase the default 8M to 12M. I discussed this
> >>> issue with Dmitry and he agrees on the principle. Any other opinions?
> >>> Or is it fine to increase it?
> >>
> >>
> >> I know a few cms they would be pleased with 12M.
> >> That looks quite fair to me.
> >>
> >> But , why the hell is this not a configurable limit by build ?
> >
> >
> > JFYI: Its value is configurable in php.ini, configure option just
> > enables or disables the limit itself.
> >
> Exactly my question , why is it configurable *only* at run time ?
>
> I want to generate a php with a custom *fixed* limit , but not enable
> memory limit setting at run time.

It is not at runtime, it is a php.ini definition, which is parsed
before the execution. But this is not the subject of this discussion.

--Pierre