Your best bet is to separate CFCs into their logical parts. This will aid in usuability and readablity. Performance differences would be negligable(sp?).
Remember that CFCs are "components" and most developers will see them as that. So instead of having one big CFC for "ecommerce app", you would have a component for each component of the ecommerce application (customers,orders,cart,etc..). My $0.02 -- Ryan Emerle -----Original Message----- From: Ian Skinner [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2003 10:25 AM To: CF-Talk Subject: CFC Performance Best Practice The question I have, is there any performance advantages and/or disadvantages to one large CFC file versus several smaller ones? I'm writing an application using a CFC for all my administration database tasks. Currently I have everything in one CFC file. The tasks could probably be logically broken up into three or four smaller CFC files by function type. My question is there any performance reason to do this? The single large file will probably top out at about 20K, does this add to the overhead of any template calling on the CFC? -------------- Ian Skinner Web Programmer BloodSource Sacramento, CA ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
