Wednesday, November 19, 2008

Building High Performance Applications for Adobe Air

A number of techniques for optimizing the performance of Flex apps running in Air, though many apply to any Flex app.

Memory usage – Virtual memory is not an indication of actual memory use, though it can be used to monitor for memory leaks

Response time
More than 100 msec is perceptible
Place text object on surface that response to mouse movement to measure response time while code is processing

You can modify either
Design ( high impact )
Code ( low impact )
“Premature optimization is the root of all evil.”

Consider working from purpose built test app
Simplifies testing
Rest of application does not need to be optimized
Keeps instrumentation out of app
Does need to be validated in main application

There is not a threading API for Flex. Asynch processing is an implicit (rather than explicit) threading capability.

Chuck up the code to ensure that the application remains responsive

Chunking code

No comments: