flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Mclean (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-33874) Binding management is memory inefficient when using the defaultDestFunc
Date Tue, 24 Dec 2013 00:43:50 GMT

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

Justin Mclean commented on FLEX-33874:
--------------------------------------

Applied new patch and checked into develop, MX binding tests pass.

> Binding management is memory inefficient when using the defaultDestFunc
> -----------------------------------------------------------------------
>
>                 Key: FLEX-33874
>                 URL: https://issues.apache.org/jira/browse/FLEX-33874
>             Project: Apache Flex
>          Issue Type: Improvement
>          Components: Data Binding, Mobile: Performance, Performance: Framework
>    Affects Versions: Apache Flex 4.11.0
>         Environment: Mobile desktop
>            Reporter: Benoit Wiart
>            Assignee: Justin Mclean
>              Labels: memory, patch, performance
>             Fix For: Apache Flex 4.12.0
>
>         Attachments: 0001-binding-regression.patch, binding-1-desktop-memory.png, binding-2-desktop-memory.png,
binding-3-before-mobile-cpu.png, binding-4-before-mobile-cpu.png
>
>
> This issue is mainly about memory optimization
> It comes from profiling a real world (complex) application on mobile & desktop
> Optimizations will also apply to desktop
> mx.binding.Binding use exception/error as control flow.
> While it's perfectly valid, it's seems to be very bad from the memory allocation side
(as reported by Scout)
> Will provide a patch as a basis for discussion.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message