Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60653
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain punkave.com designates 209.85.213.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <dc8d907937746d7e5d0fda277f5d290d.squirrel@www.l-i-e.com>
References: <CADqTB_g+3HBb8qBBS989dedUNnock-SpjRY770C4No4dGyLQTw@mail.gmail.com>
	<4FBA8FB0.80104@sugarcrm.com>
	<CAORXhGLd7EfaAWtxywgp7ZVFonDcGyaN36Qake=ov3mJuvg9Ew@mail.gmail.com>
	<dc8d907937746d7e5d0fda277f5d290d.squirrel@www.l-i-e.com>
Date: Tue, 22 May 2012 10:06:46 -0400
Message-ID: <CAORXhGKo4eFAa6VawW2fTA2KZmFVHtgwCGhDUXc8LZq5vKh5PA@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] memory usage ouchy
From: tom@punkave.com (Tom Boutell)

Actually, I just updated Rasmus' demo program to use assocative arrays
instead of objects.

In PHP 5.4.x, the associative array version uses more memory than the
object oriented version.

That's because PHP 5.4.x is using a flat array for predeclared
properties, as was mentioned earlier by Gustavo.

Associative arrays:

524288 bytes

Objects:

262144 bytes

The object-oriented version is also faster, by about 20%.

Interestingly these results don't change much if I make the property
names/keys much shorter. Probably there's a minimum allocation of 64
bytes for these or something.

It would appear there is no longer a penalty simply for using many
objects vs. many associative arrays in PHP 5.4. The opposite, in fact.
I'm sure arrays didn't get slower, but objects now take advantage of
some optimizations that become possible when properties are
predeclared.

However this doesn't mean that calling lots of setters will
necessarily be as fast as direct property access... oh what the heck,
let's test that too:

Calling dead-simple setters for the four properties rather than
setting them directly slows down the OOP version to the point where it
runs at just about the same speed as the associative array version.
That's not terrible. Direct property access is still fastest (after
all that's what the setters do after they pay the overhead of the
function call).

On Mon, May 21, 2012 at 9:23 PM, Richard Lynch <ceo@l-i-e.com> wrote:
> No offense intended, but if you've got so many OOP objects flying
> around that they are sucking down that much memory...
>
> You probably need to refactor your code and just "don't do that"
>
> Just my opinion.
>
> --
> brain cancer update:
> http://richardlynch.blogspot.com/search/label/brain%20tumor
> Donate:
> https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>



-- 
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com