Thanks.
I guess the developer in me isn't quite comfortable with so much temporary
object creation and destruction. CFMX pools db connections and threads; why
not pool query objects, instead of instantiating new ones on each request?
Looks like the JRE creates and destroys new query objects
Yes this is normal. Our busy SPARC server has a 2.5 GB JVM and frees
over 600MB when it does a GC. It does this at roughly 30 second
intervals or so, like your figures show.
On 6/6/07, Terry Ford <[EMAIL PROTECTED]> wrote:
> I've never actually paid much attention to CFMX's memory usage before, bu
> ... but I'm wondering if this is
> symptomatic of a memory problem/leak somewhere ...
No, as long as memory used doesn't increase over time.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
Fig Leaf Software provides the highest caliber vendor-authorized
instruction at our training
I've never actually paid much attention to CFMX's memory usage before, but I
just started monitoring our memory, and I'm a little unsure whether what we're
seeing is normal or not.
Setup: CFMX6.1, linux ES4, 800MB Xmx. Server averages 30 templates/second.
Cached queries set to 0 (same thing hap
4 matches
Mail list logo
