So I'm developing what will be a good-sized application, but I'll be
carefully planning for download speed and runtime efficiency through
ModuleLoader, SWFLoader, etc. 

Right now I've barely begun but have finished the ground level for the
Data Retrieval, Normalization and Management (no FDS). The memory
monitor object shows about 40 megabytes of memory being used when the
data comes in, and drops to 24 MB if I leave the app still for a a
couple minutes afterward (I assume that's garbage collection kicking
after the data normalization). 

Flex is one my first forays into needing to worry about things like
memory management, so I'm looking for best practice and a baseline of
what's expected and acceptable. 

1) What's "average" memory load for a Flex application? When do I
start freaking out about using too much memory? 

2) How do I optimize memory management during run time? What's the
best way to encourage good garbage collection? 

Ideally this app will cache the data it receives over the course of
its runtime so switching back to older sets is faster than reloading
it from the server, but if this seriously chokes memory, I need to
come up with a new strategy.

Any help is appreciated!


Reply via email to