Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of aharui@adobe.com designates
 64.18.1.181 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Mon, 23 Jan 2012 11:52:16 -0800
Subject: Re: Flex 5 UIComponent - Behavior Pattern
Thread-Topic: Flex 5 UIComponent - Behavior Pattern
Thread-Index: AczZ/V4+327iCrGORmObL5j62brvFwACyOaZ
Message-ID: <CB42FA70.3AC8E%aharui@adobe.com>
In-Reply-To: 
 <CA+ckY6ta-mqb4ksXnpRRD=pe-j0BT4JRZEL6deoLwkZ4XT9Cyw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 1/23/12 10:31 AM, "Doug McCune" <doug@dougmccune.com> wrote:

> Alex, first, thanks for that memory breakdown, very helpful.
>=20
>=20
>> The issue was not in the cost of the
>> allocations, it was in the cost of an additional function call to run th=
e
>> actual work.  Everything is now being proxied.
>=20
>=20
> What if when setting the composited piece you always stored a hard
> reference to all the functions, so something like this:
>=20
> private var setFocusFunction:Function;
> public function set focusBehavior(value:IFocusBehavior):void {
>=20
> this.setFocusFunction =3D value.setFocus; //where setFocus() is a functio=
n
>=20
> }
>=20
> and then when needing to set the focus, UIComponent calls
> this.setFocusFunction() instead of calling focusBehavior.setFocus()
>=20
> Since now the function is stored in UIComponent, does that get around the
> perf. problem of always calling a proxy like focusBehavior.setFocus()?
Actually, that makes it worse, espeically from a memory standpoint.  Every
cached function reference is just making the allocation size of the
UIComponent larger and more inefficient.  And, a function reference itself
is some 100 bytes or so because it is a closure, not a pointer into code.

I think the answer lies in selecting high-traffic sub-objects and caching
their references (or not making them sub-objects at all and baking in their
behaviors).  As I keep saying, no one rule can be universally applied.

--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui