[
https://issues.apache.org/jira/browse/FLEX-33829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797979#comment-13797979
]
Benoit Wiart commented on FLEX-33829:
-------------------------------------
Alex
the arraylist were created by the mapping AMF<->ActionScript classes NOT by the
amf deserailization code by itself
So the performance improvements depend on the data
In our case, a cross plateform Air application (desktop, mobile) this patch was
a real improvement (20% of the deserialization)
To test it you can do something like
var list:ArrayList;
var start:Number = new Date().time;
var nr:Number = 10000;
for (var i:Number = 0; i < nr; i++)
{
list = new ArrayList();
}
var end:Number = new Date().time;
Before and after the patch
You should see a difference on desktop, and much more on mobile
> Improve ArrayList performance
> -----------------------------
>
> Key: FLEX-33829
> URL: https://issues.apache.org/jira/browse/FLEX-33829
> Project: Apache Flex
> Issue Type: Improvement
> Components: Collections
> Affects Versions: Apache Flex 4.10.0
> Environment: Macos, Mobile (Air)
> Reporter: Benoit Wiart
> Labels: performance
> Attachments: 0001-ArrayList-creation-optimization.patch, flex.png
>
>
> Arraylist creation is a performance pb when deserializing amf response.
> On mobile the uid creation in the constructor is the bottleneck source
> With this patch the uid is lazily created in the getter
> Profiling was done with Adobe Scout
--
This message was sent by Atlassian JIRA
(v6.1#6144)
