On 7/23/16, 1:35 PM, "bilbosax" <waspenc...@comcast.net> wrote:
>Two things from the profiler stand out to >me that I don't understand. There is a >mouseEvent that is called one time but has a cumulative time of 5272 >ms(95.72%) of the entire process. I can only assume this is the click >event >on the header. Correct. Everything pretty much happens inside the click event. >But what else I see that is surprising to me is that each >data filter was called 74642 times, and 74642 calls were made to get data >out of the dropdownlists. Why would that happen? During a sort, does the >arraycollection call a refresh regularly? If so, is there a way to avoid >this? Any thoughts or direction would be greatly appreciated. I have >attached an image of the profile to this post. As you posted later, it really is "only" two calls per item. What version of Flex are you using? Still, the cumulative time on the filter calls isn't a major portion of 5272 ms. Did you disable all profiler filters? There is a button on the right side of the screen on the same row as the tabs that controls whether Flex and Flash classes appear in the profiler. I always turn of those filters so I can see how Flex and Flash are participating in the profile. There is a checkbox in the dialog that controls whether global classes appear. Make sure they do too. Then take a fresh look at the results. You could also set some breakpoints in ListCollectionView.as internalRefresh to make sure it only gets called once. You could try looking at some of the calls to the filters to see the call stack. HTH, -Alex
