Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19698 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50637 invoked by uid 1010); 23 Oct 2005 23:06:44 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 50622 invoked from network); 23 Oct 2005 23:06:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Oct 2005 23:06:44 -0000 X-Host-Fingerprint: 200.196.123.37 unknown Received: from ([200.196.123.37:19909] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id F0/44-22302-3871C534 for ; Sun, 23 Oct 2005 19:06:43 -0400 Message-ID: To: internals@lists.php.net Date: Sun, 23 Oct 2005 21:06:37 -0200 References: <4E0C5C8E5F8C994F90134920DD66E93F01129374@pearl.hq.booyahnetworks.com> <30.DD.54476.4AA16434@pb1.pair.com> Lines: 27 User-Agent: KNode/0.9.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Posted-By: 200.196.123.37 Subject: Re: [PHP-DEV] Re: CLI in PHP6 From: cunha17@gmail.com (Cristiano Duarte) Ron Korving wrote: > That would be nice. If all memory, even the stuff allocated by functions, > is freed at the end of the request, I can see where the problem is. It > would be very useful if this memory really would be freed at the moment > all references to it disappear. This would be a lot better for the CLI > environment, but also for a web environment, if you ask me, because the > memory required for handling pages might just be reduced by a big > percentage. I guess the question is: would this be a big performance hit > in processing time? (and I fear the answer is too big a "yes", otherwise I > expect it would've already been implemented). I agree that we should have a better memory aproach when running in CLI environment. I work with PHP since 2000 and I currently have a CLI indexing script that can eat 1Gb of memory (about 1Mb every minute) easily. IMO, for the sucess of the CLI environment, we should have a function call that *really* frees the memory allocated so it never gets to the GC (it's never executed anyway in the process). My company is huge (240000 employees and 50000 temporaries/year) and I'm advocating PHP as a multiple purpose language(not only a web page scripting language) despite what our Java advocating group say. Someone may point out that PHP may not be the correct tool for the job, but I really think we should have one tool that can handle most of our problems. If there is no other way left, and I have to make scripts in Java, Python, Perl, C++, etc please tell me before they know about it (so I have time to give it up: I really don't want to). Cristiano Duarte