> A fraction of a second on a major application that gets > millions of hits a day can make or break a system. Remember > that when you do the big jobs <g>.
While it's a good idea to code for efficiency wherever possible, the above statement just isn't that accurate. Almost every system I've seen had enough major flaws to make the minor ones truly unimportant. The lesson to draw from this is, look for the major flaws, and don't worry so much about whether one use of a CFOUTPUT tag will be slightly faster or slower than another. Instead, look to see how you can reduce the amount of work done at runtime; look at caching on every level (browser, web/app server, database server); maximize the performance of database interactions, and so on. If you think you're really done with that, look again! Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (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
