[
https://issues.apache.org/jira/browse/FLEX-33865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812532#comment-13812532
]
Maurice Amsellem commented on FLEX-33865:
-----------------------------------------
@ Benoit:
>when result is null, it's faster to return [ X , Y ] ;
Consider I am dumb, and explain to me why
return [ X, Y ] requires more allocation than result = new Array() ;
result[0] = X; result[1] = Y; return result;
>the screenshots (layout-2-desktop-memory.png, layout-1-desktop-memory.png) are
>from a real world application on desktop.
I am assuming from the screenshots titles that these are memory figures (I
can't tell for sure, because the table headers are missing).
If so, I need speed, not memory comparisons to evaluate the optimization.
If not, please tell me what figures refer to "time".
> 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)
