You guys really know the guts of CF, I hardly have any idea of what is really going on behind the scenes.
Actually this brings up a much bigger issue:
Don't optimize unless you know you have a performance problem!
Computer experts the world over tell us this constantly. Premature Optimization is just plain out bad. We spend cycles doing something fancy - and often don't know whether what we're doing is helping or not.
Here's some basic guidelines:
1. Don't optimize unless you know you have a performance problem.
2. *IF* you have a performance problem, you need to start load testing and use profiling to discover where the performance problem lies. CF's debugging execution times aren't much help here - you're better off using getTickCount() to track where your time is going.
3. Having identified one or more 'hotspots', consider *algorithmic* changes to improve performance. One or two line changes to the actual code constructs you use will have less impact on performance than changing the overall algorithm you're using.
The CF Product Team did a good job of optimizing performance for common use cases. They also provided a good default set of parameters for the JVM.
In general, write 'clean' simple code and don't get hung up on low-level performance tweaks.
Regards, Sean
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
