You will probably need to do more research to determine where in the process the bottleneck is. Check out my Census Benchmark app to see what the different parts of process you can measure (right-click to get the source code): http://www.jamesward.org/census
My guess is that it's not blaze that is slow but the data transformation and display of the data in the charts. I hope that helps. -James ----- Original Message ----- From: [email protected] <[email protected]> To: [email protected] <[email protected]> Sent: Wed Mar 26 05:27:37 2008 Subject: [flexcoders] blazeds performance I am wondering if anyone has an idea about increasing blazeds performance. I am receiving information from a database for a chart. Each record is a java object and the entire set of aproximately 180K records is contained in two separate arrays since it is a multi-series chart. I convert the records into actionscript objects from java objects when I get them. From the time the records are sent to the flex app, til the time they get drawn on the screen takes approximately 45+ seconds. This seems pretty long to me. Is this on par with what should be expected? If not, what could I do to improve this performance?
