as
>> you said, it's working great when I bypass the CFC so no sense
beating
>> it to death.
Do you have debugging on by any chance? That can really slow down a
CFC-intensive request.
Jon
>>> [EMAIL PROTECTED] 03/09/04 11:29AM >>>
On Mar 9, 2004, at 12:38 PM, Craig Dudley wrote:
> I can only assume you were getting 14000 instances of the cfc
object,
> not sure why. You could try creating one instance and storing it in
> say,
> the Application scope, and use that, might help. But since it's
> working
> now anyway, might be a waste of time.
I definitely was only instantiating the object once, prior to the
looping. I was calling the method however, using this syntax:
<cfset obj.writeStaticFile(param1,param2)/>
Not sure if that would be the problem. I a testing right now using:
<cfset temp = obj.writeStaticFile(param1,param2)/>
And that seems to be gobbling as much RAM as before. In any event, as
you said, it's working great when I bypass the CFC so no sense beating
it to death.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
