> Plus, my guess is/was that the general server load would be > balanced out by the reduction of any number of <CFLOCK>s down > to one (in application.cfm) - tho this could be a wrong-headed > way of thinking about it. > > Anyone got any opinions - even better, stats! - on the impact of > using this session > request transference technique on server > performance/load? At what sort of stage / under what circumstances > would it become a real issue?
I don't have any handy statistics, but in most of the cases I've encountered, this technique has been significantly detrimental to performance. That doesn't mean that it's always a bad thing to do, or that there's always a better way, just that in most cases, applications have enough data in the session or application scopes that it's less expensive to reference the bits of it that you need within separate CFLOCKs than it is to copy it back and forth to a local nonpersistent scope. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ phone: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.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
