do you have used pixelbender yet for outsourcing performance intense stuff?

some points regarding performance i would like to add:
- try to keep framerate low (25 fps) because the higher the framerate the higher the cpu idle usage (in large apps with a lot of displayobject on stage - see: https://bugs.adobe.com/jira/browse/FP-1149)
- use BindingUtils instead of MXML bindings, you got 50% better performance for bindings, at startup MXML does a lot of unnecessary executions. see: http://www.screenshot.at/blog/2009/04/18/databinding-under-the-hood-part-1-performance/
- check out the default values of your flex components and proof if you need them to be activated (scrollPolicy, clipContent, mouseEnabled,…)
- set your values in the declaration if possible
- nullify objects if not needed anymore (i am not sure about this, if and how much performance inprovement it will give at garbage collection time)
- avoid WMODE

Intresting to know, why “Avoid databinding on data transfer objects or AMF objects” is not good?

Regarding the rendering example, I may have to narrow the parameters for when rendering to a single Sprite gives an advantage over rendering to multiple ones. I found a problem in my code with the help of a co-worker and I’m in the process of reworking the example to give a more meaningful result.