Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25018 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84853 invoked by uid 1010); 27 Jul 2006 17:23:24 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 84838 invoked from network); 27 Jul 2006 17:23:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jul 2006 17:23:24 -0000 X-PHP-List-Original-Sender: brianm@dealnews.com X-Host-Fingerprint: 129.41.69.185 smtp.dealnews.com Linux 2.5 (sometimes 2.4) (4) Received: from ([129.41.69.185:46341] helo=smtp.dealnews.com) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 8F/A7-23194-A86F8C44 for ; Thu, 27 Jul 2006 13:23:24 -0400 Received: (qmail 2747 invoked from network); 27 Jul 2006 13:23:20 -0400 Received: from unknown (HELO mail.dealnews.com) (10.1.1.7) by 10.1.1.24 with (DHE-RSA-AES256-SHA encrypted) SMTP; 27 Jul 2006 13:23:20 -0400 Received: (qmail 5458 invoked from network); 27 Jul 2006 13:23:20 -0400 Received: from ip10.fa1-0-2.occ.iinet.com (HELO ?10.10.12.75?) (brianm@198.145.33.10) by 10.1.1.7 with ESMTPA; 27 Jul 2006 13:23:20 -0400 Message-ID: <44C8F682.1020109@dealnews.com> Date: Thu, 27 Jul 2006 10:23:14 -0700 User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060406) MIME-Version: 1.0 To: Ron Korving CC: internals@lists.php.net 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> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] memory_get_usage with new Memory Manager From: brianm@dealnews.com (Brian Moon) > 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. We have some process, that if cache has gotten stale and needs to be recreated, the process can use 100MB or memory. We don't want to cap it. However, we do want to know about it and use apahce_child_terminate() to end that process. Right now, I have to actually read /proc to figure out my memory usage. I would much rather have a function. I guess I could enable a memory limit and set to like 1GB. Seems silly though. -- Brian Moon ------------- http://dealnews.com/ Its good to be cheap =)