One of the most computationally expensive operations in the Flex component life cycle is the constructor and initialization routine. If you are adding and removing lots of complex components, this can become very taxing on the system, and reduce overall application performance. The more complex the component, the more taxing it will be. One way to reduce the impact that this has on your system is through object caching, (also known as object pooling).
Reduce, Reuse, Recycle
When using object caching, you create a cache of objects that the application can use. When the application is finished with these objects, you return the objects to the cache so that they can be reused again. This technique reduces the number of object instances created by the runtime, reduces the overall memory used when running the application, stabilizes the required resources to run the application (less spikes in both cpu and memory), and leads to better overall performance and scalability of the application when applied correctly. More1 More2 More3
1 comment:
Hi,
In the component life cycle u have mentioned about validation methods, could u please elaborate it further? like i'm not clear with the fact that whenever u call invalidateProperties() method, the commitProperties method does not get called immediatly rather than it registers it for the next render event...so i just want to know what does that render event mean?
Post a Comment