I would try Vector directly if possible, I think ArrayCollecton or ArrayList are designed for driving UI List/Grid.
On Mon, Aug 1, 2016 at 10:13 PM, bilbosax <waspenc...@comcast.net> wrote: > So, I finally got Scout to work with my program which turned out to be a > pain(Scout would time out, saying it was out of memory during the hour that > it took for the program to complete the calculations) > > The results are both interesting, and a little confusing. The main loop > took > 2560 seconds. ObjectProxy.getProperty (mx utils) took 787 seconds. > ListCollectionView.getProperty (mx.collections) took 713 seconds. Garbage > Collection took 184 seconds. ListCollectionView.getlength took 29 > seconds(this is easily fixed). And the trig method I wrote only took 14 > seconds. > > This clearly shows that the math is not the bottleneck, getting information > out of the arraycollection and objectproxy objects is the slowest process. > I am addressing the arraycollection as myAC[1].someProperty in all of my > comparisons and calculations as was suggested. I don't know if this is > treating it more as an array or an array collection. I don't know if it > would all process faster if I initially passed the arraycollection data off > to a regular array to do all of the processing. I need the objectproxies > because my itemrenderers won't bind to my arraycollection otherwise. > > So the question now is, should I find an alternative to the ObjectProxies > and try and optimize working with my arraycollection, or should I simply > make another worker to chop down this processing time? Math is not the > bottleneck, getting the data together to do the math is the slow part. > > > > -- > View this message in context: > http://apache-flex-users.2333346.n4.nabble.com/Workers-and-Speed-tp13098p13134.html > Sent from the Apache Flex Users mailing list archive at Nabble.com. >
