Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25019 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86812 invoked by uid 1010); 27 Jul 2006 17:33:50 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 86797 invoked from network); 27 Jul 2006 17:33:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jul 2006 17:33:50 -0000 Authentication-Results: pb1.pair.com header.from=iliaal@gmail.com; domainkeys=good DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: iliaal@gmail.com X-Host-Fingerprint: 64.233.162.204 nz-out-0102.google.com Linux 2.4/2.6 Received: from ([64.233.162.204:5776] helo=nz-out-0102.google.com) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 99/F7-23194-BF8F8C44 for ; Thu, 27 Jul 2006 13:33:48 -0400 Received: by nz-out-0102.google.com with SMTP id i1so132442nzh for ; Thu, 27 Jul 2006 10:33:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:in-reply-to:references:mime-version:x-priority:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=qJRJpclppRO4XvZnLu2DMTitT/IfIIjmFppxa8VODwKa4Ix/KvXdtTOKN7nBvDslLLiDNrCkWZxUGP+Riao0Bdj2b4S+dgsgtICARXNOLQbhYmb3cTFXmHXDLxg7ErTbGeYpMj0fBJcX1LZhPMRZxGNp2dLta3D4QC1TJv7+fg8= Received: by 10.64.47.19 with SMTP id u19mr1337551qbu; Thu, 27 Jul 2006 10:33:44 -0700 (PDT) Received: from ?192.168.1.6? ( [72.59.8.142]) by mx.gmail.com with ESMTP id q15sm4582821qbq.2006.07.27.10.33.43; Thu, 27 Jul 2006 10:33:44 -0700 (PDT) In-Reply-To: References: <00d601c6af9d$c18f2d30$0201a8c0@pc1> <003701c6afb1$81b87720$6e02a8c0@thinkpad> <44C6205F.4090808@php.net> <00ed01c6b163$c3d40ad0$0201a8c0@pc1> <44C8B9B8.5030108@toggg.com> <70339B16-D50B-45B9-A55D-B58F9EEB679D@prohost.org> Mime-Version: 1.0 (Apple Message framework v752.2) X-Priority: 3 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-ID: <9137E546-1F31-4157-B7F5-DD0A546A5136@prohost.org> Cc: internals@lists.php.net Content-Transfer-Encoding: 7bit Date: Thu, 27 Jul 2006 13:33:27 -0400 To: Ron Korving X-Mailer: Apple Mail (2.752.2) Sender: Ilia Alshanetsky Subject: Re: [PHP-DEV] memory_get_usage with new Memory Manager From: ilia@prohost.org (Ilia Alshanetsky) On 27-Jul-06, at 1:17 PM, Ron Korving wrote: > Yes, hosting providers would enable the memory limit. But who wants > to use > memory_get_[peak_]usage()? Not the hosting provider, but the > application > developer. > The peak usage function was added with profiling in mind and keeping track of scripts that spike memory, when I added it the intent was it would help with profiling and debugging. Not something used everyday in production environment. In dev environment speed is not an issue, so you can enable memory limit and raise the limit to some very high value such as 1Gb so it does not get in the way. Ilia Alshanetsky