[
https://issues.apache.org/jira/browse/FLEX-33865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812529#comment-13812529
]
Maurice Amsellem commented on FLEX-33865:
-----------------------------------------
>splitting into 2 methods the cost saving is more likely to be in reduced
>garbage collection (which can have a large effect on performance).
Ok ,I understand and that's also what Benoit says about memory allocations.
I am not familiar with Flash GC, especially on Mobile. How do you measure the
speed gain of reduced GC ? Is this possible with Scout ? does it occur
incrementally on temp short-lived objects ?
Any reading on this topic (preferably on the web)?
> ConstraintLayout / LayoutElementHelper are memory inefficient (and slow)
> ------------------------------------------------------------------------
>
> Key: FLEX-33865
> URL: https://issues.apache.org/jira/browse/FLEX-33865
> Project: Apache Flex
> Issue Type: Improvement
> Components: Mobile: Performance, Spark: Layout
> Affects Versions: Apache Flex 4.11.0
> Environment: mobile desktop
> Reporter: Benoit Wiart
> Assignee: Maurice Amsellem
> Labels: mobile, performance
> Attachments: 0001-ConstraintLayout-optimizationsV2.patch,
> layout-1-desktop-memory.png, layout-2-desktop-memory.png,
> layout-3-mobile-memory.png
>
>
> ConstraintLayout / LayoutElementHelper are doing too many memory allocation.
> it's really bad on mobile
> the attached screenshots were taken on desktop
--
This message was sent by Atlassian JIRA
(v6.1#6144)
