Accessibility

Table of Contents

  1. Introduction
  2. The ActionScript Profiler Architecture
  3. What Does the ActionScript Profiler Do?
  4. Installing the ActionScript Profiler
  5. Running the Profiler: An Example
  6. Troubleshooting the ActionScript Profiler
  7. Some Final Thoughts

Macromedia Flex Profiler: Identifying Performance Bottlenecks in ActionScript

The ActionScript Profiler Architecture

You don't need to fully understand the ActionScript Profiler architecture to use it. But some knowledge of its inner workings is helpful. The ActionScript Profiler consists of two parts: a version of Flash Player that can output performance data and an application that analyzes performance data and generates reports. Macromedia Flex ships with a version of Flash Player with enhanced debugging and profiling capabilities. This Player supports the Macromedia Flash 7 SWF file format. When the Player runs a SWF application (you must compile it in debug mode, that is, a SWD must be present), it measures the time required for functions to execute in microsecond intervals (1 millisecond = 1000 microseconds) and outputs timing data in binary format to a file. The binary data in the file represents the execution trace of the SWF application during the profiling session. The second part of the ActionScript Profiler is a report generator. This report generator in Macromedia Flex is a J2EE web application. Flex users use their browsers to view and navigate the HTML/JSP-based reports and to identify performance bottlenecks.

Page 2 of 7
Previous Page
Next Page