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] [Comment Edited] (FLEX-33890) Style engine : style matching allocates a lot of memory even if everything is in cache
Date Mon, 11 Nov 2013 17:55:22 GMT

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

Benoit Wiart edited comment on FLEX-33890 at 11/11/13 5:54 PM:
---------------------------------------------------------------

for point (2)
Pros :
- use less memory
- code is easier to understand
- faster (inaccurate measurement)

Cons :
- change the content of StyleManagerImpl#typeHierarchyCache (but the getter is @ private in
the interface)



was (Author: benoitw):
for point (2)
Pros :
- use less memory
- code is easier to understand

Cons :
- change the content of StyleManagerImpl#typeHierarchyCache (but the getter is @ private in
the interface)


> Style engine : style matching allocates a lot of memory even if everything is in cache
> --------------------------------------------------------------------------------------
>
>                 Key: FLEX-33890
>                 URL: https://issues.apache.org/jira/browse/FLEX-33890
>             Project: Apache Flex
>          Issue Type: Improvement
>          Components: Mobile: Performance, Performance: Framework, Styles
>    Affects Versions: Apache Flex 4.11.0
>         Environment: mobile desktop
>            Reporter: Benoit Wiart
>              Labels: memory, performance
>         Attachments: 0001-gettypehierarchy-optimizations.patch, gettypehierarchy-example-1.png,
gettypehierarchy-example-2.png, gettypehierarchy-example-3.png, gettypehierarchy-example-4.png
>
>
> StyleProtoChain#getTypeHierarchy is called often and is responsible for a lot of unneeded
memory allocations even if the type hierarchy is cached.
> This patch has 2 parts :
> - (1) : exception handling reworking in order to avoid the closure/activation creation
by the try/catch
> - (2) : replace the use of a flash proxy with a custom class : It seems that the proxy
was only used as an array.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message