Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25370 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96836 invoked by uid 1010); 16 Aug 2006 11:07:29 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 96819 invoked from network); 16 Aug 2006 11:07:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Aug 2006 11:07:29 -0000 X-PHP-List-Original-Sender: bertrand@toggg.com X-Host-Fingerprint: 212.27.42.29 smtp3-g19.free.fr Linux 2.4/2.6 Received: from [212.27.42.29] ([212.27.42.29:42692] helo=smtp3-g19.free.fr) by pb1.pair.com (ecelerity 2.1.1.8 r(12549M)) with ESMTP id 80/9D-11355-D6CF2E44 for ; Wed, 16 Aug 2006 07:07:26 -0400 Received: from [192.168.0.3] (lns-bzn-44-82-64-121-227.adsl.proxad.net [82.64.121.227]) by smtp3-g19.free.fr (Postfix) with ESMTP id C51FD4970D; Wed, 16 Aug 2006 13:07:22 +0200 (CEST) Message-ID: <44E2FDC8.2020503@toggg.com> Date: Wed, 16 Aug 2006 13:13:12 +0200 Reply-To: bertrand@toggg.com User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc3 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pierre.php@gmail.com CC: internals@lists.php.net References: <20060816123006.4028b334@pierre-u64> In-Reply-To: <20060816123006.4028b334@pierre-u64> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: increase the default memory limit in 5.2.0+ From: bertrand@toggg.com (bertrand Gugger) 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 ? Why do we need to --enable-memory-limit to be able to get a custom value but then at run time only ? In clear, I would like to be able to generate php with a limit given in ./configure. This limit may be different from an install to another , depending on the applications. I hope my poor english is understandable. Regards.