StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Flex Builder 3 includes a <a href="http://labs.adobe.com/wiki/index.php/Flex_3:Feature_Introductions:_Performance_and_Memory_Profiling" rel="nofollow noreferrer">performance and memory profiler</a>. I haven't used it, but it looks pretty snazzy. I'm not sure if it can be used for non-Flex content, but it will definitely only work for AS3.</p> <p>Apart from that, over the years I've found a couple of workable methods for a certain level of profiling. At the simplest you can obviously just build an FPS meter and watch how it behaves. For more info about code-heavy applications one thing I've done is to whip up a simple framework for making <code>getTimer()</code> calls at the beginning and end of methods and tracking the cumulative time, but I've never used any pre-made tools for that. In practice it's usually pretty obvious where the bottlenecks are for code-heavy work, and in those cases I just put timer directly around what I'm trying to optimize.</p> <p>When the bottlenecks are in rendering, the first thing to try is to simply publish at your target FPS, and use an FPS meter to track when actual playback falls below that (on target hardware). You can get more detailed information about rendering by, for example, invoking a 1ms timeout that calls <code>refreshAfterUpdate</code>, and monitoring the actual time between refreshes. Unfortunately you can't get any more granular than "per refresh" though - you can't directly see how much time is spent rasterizing, compositing, etc. (Though you can often infer these things. For example, you can enable bitmap caching on vector-heavy objects to take rasterization off the table, and observe the results.)</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload