Yes Alex, clearly it's what's missing in Scout and I've reported it a long time ago (with many other enhancements) but you have an idea how much it consumes in that particular function. Of course if we had consumption average per call would be even better. Like Darren I was unable to run the profiler with FB because of the application size but Scout helped me to find a lot of bottlenecks like wrong kind of invalidations or script blocks that looked inoffensive but were wasting precious ms.
It was also Scout that made me realize how much heavier is to deserialize large collections with properties as ArrayCollections instead of simple Arrays. On 18 March 2014 16:23, Alex Harui <aha...@adobe.com> wrote: > I haven't found a way to get call counts in Scout. I still find the FB > profiler's call counts a very useful tool in figuring out the root cause > of many performance problems. > > -Alex > > On 3/18/14 8:59 AM, "João Fernandes" <joaopedromartinsfernan...@gmail.com> > wrote: > > >A faster way to check the bottlenecks in performance is to use Adobe Scout > >instead of the Performance profiler > > > > > >On 18 March 2014 15:19, Maurice Amsellem > ><maurice.amsel...@systar.com>wrote: > > > >> SDK 4.9.1 chart optimization was on style initialization, which was done > >> for every chart , while it was required only once per module. > >> So the performance gain is only when you have many charts. > >> > >> You say that your test has one chart, and it takes 8 seconds to > >>initialize > >> the axis. > >> > >> - Can you run the performance profiler on that part and see what is > >>taking > >> that 8 sec ? > >> - your example is missing the data that is used in the chart. Can you > >> please take the time to build a fully operational test case that show > >>the > >> issue, and post the source code here, so that we can help you more > >> efficiently. > >> > >> Thanks > >> > >> Maurice > >> > >> -----Message d'origine----- > >> De : DarrenEvans [mailto:darren.ev...@allocatesoftware.com] > >> Envoyé : mardi 18 mars 2014 15:50 > >> À : users@flex.apache.org > >> Objet : RE: Patching Flex 4.6 SDK chart functionality > >> > >> Hi Maurice, > >> > >> Thanks for helping out too. > >> > >> Moving to anything above 4.6 is impossible without severe development > >>from > >> our end. Our primary limiting factor is we use the IBM ILOG Elixir Gantt > >> Chart component and it is critical to our application. This was not > >> originally owned by IBM and was well supported in the early days. > >>Nowadays > >> following the buy out, development and support is virtually none > >>existant. > >> The last working version of Flex SDK that is compatible is 4.6, anything > >> above that results in the following error: > >> > >> ReferenceError: Error #1065: Variable > >> com.ibm.ilog.elixir.utils::LicenseHandler is not defined. > >> > >> As a result we need to write our own component to replace this one but > >> that will require significant man days of effort or get them to support > >> later SDK version which will also result in a long wait (if it ever > >> happens)! > >> > >> So....... > >> > >> Maurice/Alex, I have downloaded the 4.9.1 SDK and reconfigured the > >> application to use it. Ignoring the fact the gantt control based > >> functionality breaks, I can test the chart functionality as it's in a > >> completely different area. *With the 4.9.1 SDK the chart is still as > >>slow > >> initialising, so that change does not help after all*. > >> > >> I have a chart defined thus (it's only partially based on the real one > >>but > >> what I'm testing against at the moment): > >> > >> <mx:LineChart id="requiredVsActualLineChart" > >> dataProvider="{requiredVsActualDataProvider}" showDataTips="true" > >> dataTipFunction="requiredVsActualDataTipFunction" height="210" > >> width="100%" > >> paddingTop="4" paddingRight="20"> > >> <mx:horizontalAxis> > >> <mx:CategoryAxis id="requiredVsActualCategoryAxis" > >> categoryField="On"/> > >> </mx:horizontalAxis> > >> </mx:LineChart> > >> > >> Now if after the chart has shown I run the following code to set up the > >> vertical axis, it takes 8 seconds!!!! > >> > >> var linearAxis:LinearAxis = new LinearAxis(); linearAxis.interval = 0.1; > >> linearAxis.baseAtZero = true; linearAxis.maximum = 100; > >>linearAxis.minimum > >> = 0; requiredVsActualLineChart.verticalAxis = linearAxis; > >> > >> So what is up with that?! > >> > >> > >> > >> > >> > >> > >> > >> > >> -- > >> View this message in context: > >> > >> > http://apache-flex-users.2333346.n4.nabble.com/Patching-Flex-4-6-SDK-char > >>t-functionality-tp5527p5597.html > >> Sent from the Apache Flex Users mailing list archive at Nabble.com. > >> > > > > > > > >-- > > > >João Fernandes > > -- João Fernandes
