You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Justin Mclean (JIRA)" <ji...@apache.org> on 2013/05/04 03:46:16 UTC
[jira] [Updated] (FLEX-27905) Adding/Removing children to same
parents sometimes causes unnecessary style invalidation
[ https://issues.apache.org/jira/browse/FLEX-27905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Mclean updated FLEX-27905:
---------------------------------
Labels: performance (was: )
> Adding/Removing children to same parents sometimes causes unnecessary style invalidation
> ----------------------------------------------------------------------------------------
>
> Key: FLEX-27905
> URL: https://issues.apache.org/jira/browse/FLEX-27905
> Project: Apache Flex
> Issue Type: Bug
> Components: Styles
> Affects Versions: Adobe Flex SDK 4.5.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
> Reporter: Adobe JIRA
> Labels: performance
>
> Steps to reproduce:
> 1. Run attached PerformanceTests3.mxml -- remove the monkey-patched version of UIComponent
> 2. Notice how slow remove and then re-adding those 200 Groups are (each Group has 10 Button children)
>
> Actual Results:
> Since adding/removing to the same parent (and the styles haven't changed), styles shouldn't need to be regenerated. Unfortunately, for a typical application, especially when using includeIn/excludeFrom with state, this can happen a lot. On my computer, the time it takes for me is:
> 430ms, 2159ms, 18ms (code, validation, render)
>
> Expected Results:
> After a few changes (will explain in comment below), the result I was getting on my computer was:
> 88ms, 13ms, 18ms (code, validation, render)
> On more complicated examples, with more children and more styles, this can make an even bigger difference
>
> Workaround (if any):
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Updated] (FLEX-27905) Adding/Removing children to same parents sometimes causes unnecessary style invalidation
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I don't belong here. Please remove me from this mailing list.
> My emailID is sujithr04@gmail.com.
If you send a blank email to dev-unsubscribe@flex.apache.org it will unsubscribe from the list.
Alternatively setting up a few email filters to place Apache Flex or Apache JIRA emails into seperate folders works nicely.
Thanks,
Justin
Re: [jira] [Updated] (FLEX-27905) Adding/Removing children to same
parents sometimes causes unnecessary style invalidation
Posted by sujith Reddy <su...@gmail.com>.
I don't belong here. Please remove me from this mailing list.
My emailID is sujithr04@gmail.com.
I am getting lot of mails and missing very important mails.
Thanks,
Sujith
On Fri, May 3, 2013 at 7:46 PM, Justin Mclean (JIRA) <ji...@apache.org>wrote:
>
> [
> https://issues.apache.org/jira/browse/FLEX-27905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Justin Mclean updated FLEX-27905:
> ---------------------------------
>
> Labels: performance (was: )
>
> > Adding/Removing children to same parents sometimes causes unnecessary
> style invalidation
> >
> ----------------------------------------------------------------------------------------
> >
> > Key: FLEX-27905
> > URL: https://issues.apache.org/jira/browse/FLEX-27905
> > Project: Apache Flex
> > Issue Type: Bug
> > Components: Styles
> > Affects Versions: Adobe Flex SDK 4.5.1 (Release)
> > Environment: Affected OS(s): All OS Platforms
> > Language Found: English
> > Reporter: Adobe JIRA
> > Labels: performance
> >
> > Steps to reproduce:
> > 1. Run attached PerformanceTests3.mxml -- remove the monkey-patched
> version of UIComponent
> > 2. Notice how slow remove and then re-adding those 200 Groups are (each
> Group has 10 Button children)
> >
> > Actual Results:
> > Since adding/removing to the same parent (and the styles haven't
> changed), styles shouldn't need to be regenerated. Unfortunately, for a
> typical application, especially when using includeIn/excludeFrom with
> state, this can happen a lot. On my computer, the time it takes for me is:
> > 430ms, 2159ms, 18ms (code, validation, render)
> >
> > Expected Results:
> > After a few changes (will explain in comment below), the result I was
> getting on my computer was:
> > 88ms, 13ms, 18ms (code, validation, render)
> > On more complicated examples, with more children and more styles, this
> can make an even bigger difference
> >
> > Workaround (if any):
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>