flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Harui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-33829) Improve ArrayList performance
Date Thu, 17 Oct 2013 14:31:41 GMT

    [ https://issues.apache.org/jira/browse/FLEX-33829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797951#comment-13797951

Alex Harui commented on FLEX-33829:

Can you provide a test case where this makes a difference.  This will save time on each ArrayList
instance, but how many ArrayLists are being created per AMF response?  Does your data have
a lot of child arrays?

For those that don't have data with a lot of child arrays and are just getting a lot of data
items per response, if you can write your data class to implement mx.core.IUID because there
is already a unique identifier in the data (customer account #, employee id, etc) that should
also save on UID generation per-item.  Or you can try lazy generation of the UID in your data
item as well.


> 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

View raw message