Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6858
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 8 Jan 2004 18:22:27 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1251495731562.20040108182227@marcus-boerger.de>
To: Christian Schneider <cschneid@cschneid.com>
Cc: Stanislav Malyshev <stas@zend.com>, Andi Gutmans <andi@zend.com>,
	internals@lists.php.net
In-Reply-To: <3FFD5A11.3040500@cschneid.com>
References: <5.1.0.14.2.20040108100152.02029de8@127.0.0.1>
 <Pine.LNX.4.44.0401081014110.1418-100000@shire.zend.office>
 <3FFD5A11.3040500@cschneid.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Ability to lower PHP memory usage
From: helly@php.net (Marcus Boerger)

Hello Christian,

Thursday, January 8, 2004, 2:24:33 PM, you wrote:

> Stanislav Malyshev wrote:
>> I'm concerned that this problem of breaking common platform might be more
>> dangerous than the performance benefit. Which, BTW, I estmate as pretty 
>> minimal - code space is shared on all modern OSes anyway, so a little 

> I think that's a good point for leaving it the way it is: Minimal 
> benefit while opening a can of worms of possible problems.

> Another reason not to do it is the amount of work to decide which 
> function should go where. Let's keep it simple and focus on IMHO more 
> pressing problems.

Same thoughts here. The benefit is far to low. There are a lot of places
we could put our efforts into better: bug-fixing instead of creating new
bug fixes and increasing the WFT factor.

The only real reason is it php would have been meant to serve cellphones or
other small devices. But hey those run java. So we shouldn't care about a
few kilobytes (or hundreds of them).

Best regards,
 Marcus                            mailto:helly@php.net