Did you try to load your CFCs into the session scope for every session. You
can easily eat the memory...

Murat. 

> -----Original Message-----
> From: Adrocknaphobia [mailto:[EMAIL PROTECTED] 
> Sent: Friday, December 17, 2004 6:59 PM
> To: CF-Talk
> Subject: Re: Number of functions in a CFC?
> 
> The poor man's way. I specify a number of objects to load, pull up
> task manager, then monitor the difference. I've found that even my
> cfcs with alot of functions have a very _very_ small RAM imprint.
> 
> -Adam
> 
> 
> On Fri, 17 Dec 2004 11:50:37 -0500, Burns, John D
> <[EMAIL PROTECTED]> wrote:
> > I'm using Firefox because M$ is evil...just kidding Adam.  I'm not
> > really currently doing monitoring on this because I'm not quite sure
> > how.  That's one of my concerns.  The other reason I asked 
> the question
> > is because I am using a lot of these functions over and over and I'm
> > caching the CFC in the application scope.  The thing I'm 
> wondering is if
> > I cache 1 CFC in the application scope with 100 functions 
> in it will it
> > use more/less memory and will it perform better/worse than 
> caching 20
> > different CFCs in the application scope and call each separately.
> > Obviously, these numbers are just examples and I don't plan 
> on having 1
> > CFC with 100 functions, but I'm just looking for 
> statistics/measurements
> > on which is a better practice.  How are you testing memory 
> usage of CFCs
> > (if at all)?
> > 
> > John Burns
> > Certified Advanced ColdFusion MX Developer
> > AI-ES Aeronautics, Web Developer
> > 
> > -----Original Message-----
> > From: Adrocknaphobia [mailto:[EMAIL PROTECTED]
> > Sent: Friday, December 17, 2004 11:44 AM
> > To: CF-Talk
> > Subject: Re: Number of functions in a CFC?
> > 
> > On the topic, how is everyone testing memory usage of CFCs?
> > 
> > -Adam
> > 
> > On Fri, 17 Dec 2004 11:37:39 -0500, Jim Davis
> > <[EMAIL PROTECTED]> wrote:
> > > I always feel that CFC should encompass a single, well-defined
> > concept.
> > >
> > > Put as many functions in the CFC as you need to address 
> the needs of
> > > that concept, but keep an eye on creep.  Usually (but not 
> always) a
> > > large number of functions in a CFC indicates that you may 
> have set the
> > 
> > > concept too broadly and should consider multiple CFCs.
> > >
> > > There isn't a specific number (or range of numbers or 
> size) that this
> > > happens at and it's different every time.  A CFC might 
> start overreach
> > 
> > > its scope and indicate the need for a new CFC after the 
> 30th function,
> > 
> > > the 5th or the 100th.
> > >
> > > As long as the scope of the CFC is well-defined and well-bordered
> > > don't worry about the number of functions in it.
> > >
> > > That being said I personally DO sometimes worry about 
> this.  I tend to
> > 
> > > possibly make multiple CFCs were multiple ones might not 
> be needed,
> > > but are still logical.
> > >
> > > For example, I've got a CFC-based security system made up 
> of about a
> > > dozen cooperating CFCs.  The main "Security.cfc" contains 
> most of the
> > > system-level stuff (the authentication caches, the instantiated
> > > collections, etc).  It has, I think, about 15 functions in it.
> > >
> > > However there are at least two sets of functions that may 
> have gone in
> > 
> > > there... but didn't.  One was installation and 
> deinstallation routines
> > 
> > > for the system (which create database tables, Verity collections,
> > > etc).  These functions tended to be very long and only used once.
> > >
> > > So I created a "SecurityConfiguration.cfc" that JUST handles these
> > tasks.
> > > Some people don't like this idea (they think an 
> application should be
> > > "self-contained) and that's a valid opinion.  The point 
> is consistency
> > > however: I set my boundaries for logical reasons and 
> maintained that
> > > reasoning throughout the development of the system (and other
> > systems).
> > >
> > > Essentially there has to be some systemic, logical reason for the
> > splits.
> > > Saying "there's too many functions" is NOT such a reason and you
> > > should never (I think) consider splitting up a logically 
> consistent
> > > CFC for that reason.
> > >
> > > Jim Davis
> > >
> > >
> > 
> > 
> 
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Special thanks to the CF Community Suite Silver Sponsor - RUWebby
http://www.ruwebby.com

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:188013
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to