Sorry, that one was kind of deceiving... each property was a UIComponent and I was creating a new UIComponent each iteration, so it averaged out about the same. If I change each property to a Number and just increment it, it looks like this:
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
performance.BindablePerformance (10,000 iterations)
Tests [Bindable] performance in Flex
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
method...............................................................ttl ms...avg ms
A_DefaultBinding 118 11.80
A_DefaultBinding_Again 119 11.90
B_CustomBindingEvent 87 8.70
B_CustomBindingEvent_Again 91 9.10
C_CustomBindingEventWithCondition 23 2.30
C_CustomBindingEventWithCondition_Again 20 2.00
D_NoBinding 11 1.10
D_NoBinding_Again 12 1.20
... SECOND ROUND:
A_DefaultBinding 134 13.40
A_DefaultBinding_Again 122 12.20
B_CustomBindingEvent 83 8.30
B_CustomBindingEvent_Again 78 7.80
C_CustomBindingEventWithCondition 23 2.30
C_CustomBindingEventWithCondition_Again 26 2.60
D_NoBinding 12 1.20
D_NoBinding_Again 12 1.20
... So it looks like just adding that conditional statement to check for the event listener is kind of expensive. But it's only a 2x performance hit instead of ~7-8x for dispatching an unnecessary event (like setting alpha in the UIComponent when nothing is bound to it), and the default binding, which is 10-11x more expensive!
1x: No binding
2x: Custom binding event, not dispatched (because there's no event listener)
7-8x: Custom binding event, dispatched (by default by Flex)
10-11x: Default binding event, dispatched (by default by Flex)
This might be a factor in why animating UIComponents is sooo much slower/choppier than animating Sprites or whatnot, because alpha, x, y, and whatever else dispatch events when there's nothing bound to them.
> grep -r "\"xChanged\"" ./*
> ./framework/src/mx/containers/utilityClasses/ConstraintColumn.as: [Bindable("xChanged")]
> ./framework/src/mx/containers/utilityClasses/ConstraintColumn.as: dispatchEvent(new Event("xChanged"));
> ./framework/src/mx/core/UIComponent.as: [Bindable("xChanged")]
> ./framework/src/mx/core/UIComponent.as: dispatchEvent(new Event("xChanged"));
> ./framework/src/mx/core/UIComponent.as: dispatchEvent(new Event("xChanged"));
There is nothing in the framework listening/bound to "xChanged", or most of the other properties dispatching events.
That "set x" accessor shouldn't be dispatching an event every time its set, neither should y, width, height, alpha, explicitWidth/height...
override public function set x(value:Number):void
{
if (x == value)
return;
if (_layoutFeatures == null)
{
super.x = value;
}
else
{
_layoutFeatures.layoutX = value;
invalidateTransform();
}
invalidateProperties();
dispatchEvent(new Event("xChanged"));
}
...should become
override public function set x(value:Number):void
{
if (x == value)
return;
if (_layoutFeatures == null)
{
super.x = value;
}
else
{
_layoutFeatures.layoutX = value;
invalidateTransform();
}
invalidateProperties();
if (hasEventListener("xChanged"))
dispatchEvent(new Event("xChanged"));
}
...That should help out in animations, and just make performance better in general.
Best,
Lance
10
Replies
AdChoices