I think the other experiment is to drop the frame rate to something
very low when the idle loop is empty to see if that lowers the idle CPU.
On 2009-06-04, at 12:15EDT, Henry Minsky wrote:
I tried an app with 5000 views, as tags inline, and didn't see any
change
reported in the inittimer tool for startup time, but maybe that
wasn't the
right thing to be looking at, perhaps there is some other
performance metric
we should be checking.
On Thu, Jun 4, 2009 at 9:01 AM, P T Withington <[email protected]> wrote:
This makes me wonder if we should revisit the idea of auto-
adjusting the
frame rate in the LZX runtime:
With just 4 simple tips, you can dramatically improve the memory/
CPU usage
footprint of your application.
Use the lowest framerate possible
Dynamically change the framerate to fit your application needs
Only use Event.ENTER_FRAME handlers when necessary
Have as few Event.ENTER_FRAME handlers and Timers as possible
[Building CPU efficient Adobe AIR apps | Serge Jespers](
http://www.webkitchen.be/2009/06/04/building-cpu-efficient-adobe-air-apps/
)
--
Henry Minsky
Software Architect
[email protected]
