>oi CF-Talk,!! > > ok don't flog me.. but since most app variables are locked and >set to a > request scope......is there any loss of "performance" or is just >putting all > app scoped variables as request scoped variables in the >application.cfm > acceptable...? >
The performance "degradation" is virtually negligible. For non-CFMX applications I write, I use local-scoped variables (variables or request, depending on if I need them for custom tags) in an included file in my Application.cfm file. In one scenario, I tested setting 30 variables with a stress testing tool (15 simultaneous threads over a 10 minute span) and the *worst* it ever got was 28 milliseconds. Those results and others I've done make this approach much easier because I don't have to worry about locking (except in race conditions, of course). But that's just my approach. Others swear by locking. To each their own, as long as you lock where appropriate. Regards, Dave. ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
