The logic has 3 or 4 major branches, so the total number of methods called is about a third or a quarter of the total.
So the choice is to instantiate one 3000 line cfc with 107 methods only some fo which get used, against 2 or 3 smaller cfcs where al the methods get used. So does anyone have an feel for whether there is a performance hit from instantiating methods that never end up being used? On this machine JRun is bloating up to 500MB or more so the technique i'd normally use of putting the cfc into a shared scope isnt an option. We have to reduce things in memory as much as possible. On my test machine, I run this cfc on 250 records in quick succession and it brings the machine to its knees. Jrun bloats to the point where nothing else will run. I hate to think what would happen if i released this thing into the wild Cheers Mike Kear Windsor, NSW, Australia Adobe Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month On Tue, Jul 22, 2008 at 10:11 PM, Aaron Rouse <[EMAIL PROTECTED]> wrote: > Even if you split it out, would the processing page not still end up calling > the same amount of methods unless you could redesign the build process > somehow? I sometimes wonder if speed is the ultimate goal and at any cost > if it might just be better to use included files with UDFs when needed over > CFCs. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:309443 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
