I'm not disagreeing with Michiel, this is just where I got interested in
responding.
I think there may be a difference in how people are using the term "memory
leak".
CF will use lots of memory, but as far as I can tell it will eventually
reach a plateau of memory use and not go any higher. The level of this
plateau depends on the application(s), usage, and configuration of the
system, and may be above the amount of memory you have installed, which is
bad.
I would not call this a a memory leak; to me, a program has a memory leak
when it will use more and more memory indefinitely and never reach a
plateau.
-----Original Message-----
From: Michiel Boland [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 27, 2001 11:07 AM
To: CF-Server
Subject: RE: Hmmmm?
> >The
> >one machine was rebooted after an upgrade about a week ago, and it's
memory
> >usage has increased about 100% in that week.
>
> The reason that RAM usage grows over time is because p-code is only cached
> with each initial request to the template. To put in other words, each
time
> a template is called, ColdFusion checks to see if it is in cache. If it is
> not, then it pulls the file off the drive, compiles, caches and executes
it.
CF memory usage is also influenced by other things. For example, if you
run a template like
<cfscript>
for (i = 0; i lt 1000000; i = i + 1)
;
</cfscript>
ColdFusion will gobble up a huge amount of memory without ever releasing
it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
