A code profiler is most commonly used to measure the effects of object instantiation and method calls. To best take advantage of a profiler, you should also have a good understanding of your application's architecture, as well as the way your application interacts with external resources.
The ActionScript Profiler can examine the ActionScript in your Flex or Macromedia Flash applications so that you can identify bottlenecks. Although the Profiler cannot directly drill down into external resources such as Enterprise JavaBeans (EJBs), you can wrap calls to these resources in ActionScript functions and profile them to gauge the total time.
Before using the Profiler, you should define the most common use cases of your application and target the code paths of those use cases with the Profiler.
Macromedia recommends that you do not run the Profiler against your entire application. Rather, you should isolate sections of ActionScript code in your application and profile each section separately in the form of unit tests. If you try to profile an entire enterprise application, the Profiler might produce too much data.
Version 1.5
Send me an e-mail when comments are added to this page | Comment Report
Current page: http://livedocs.adobe.com/flex/15/flex_docs_en/00000829.htm