> > Everything between cfoutput tags needs to be parsed. So a big > > page would slow performance, by how much is prob negligible > > but worth testing to find out. > > Remember that this would only be a hit once each time the file was > changed, as once it's compiled down to bytecode it doesn't have to be > parsed again. Back in the CF5 days the code was parsed with each page > view, but that hasn't been the case since CFMX 6.
While the general statement you made about bytecode is true, the conclusion you draw from it is one that I'd be reluctant to make without load testing. CF still has to substitute values for expressions in your CFOUTPUT blocks, and we don't know whether the cost of multiple CFOUTPUTs vs single, larger CFOUTPUTs is a compilation cost or an execution cost. At least, I don't know, and I've never seen any real evidence one way or the other. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:351625 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
