flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Wiart (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLEX-33874) Binding management is memory inefficient when using the defaultDestFunc
Date Mon, 04 Nov 2013 13:53:19 GMT

     [ https://issues.apache.org/jira/browse/FLEX-33874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Benoit Wiart updated FLEX-33874:

    Attachment: binding-4-before-mobile-cpu.png

scout cpu profiling on mobile (binding-3-before-mobile-cpu.png and binding-4-before-mobile-cpu.png)

I don't have the 'after' version

> 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
>              Labels: memory, performance
>         Attachments: 0001-binding-optimization.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

View raw message