From: Mark Ireland [mailto:markinc...@hotmail.com]
Sent: Sunday, 8 November 2009 12:43 PM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Persistent Scopes and Memory
You tried everything he suggested, all at once?
From: st
@googlegroups.com
Subject: [cfaussie] Re: Persistent Scopes and Memory
You tried everything he suggested, all at once?
From: st...@cfcentral.com.au
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Persistent Scopes and Memory
Date: Sun, 8 Nov 2009 05
I tried this on my CF8.01 64 Bit server and the server wouldn't restart..had
to roll it back
_
From: Kevin Pepperman [mailto:chorno...@gmail.com]
Sent: Saturday, 7 November 2009 11:21 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Persistent Scopes and Memory
I believe he
You tried everything he suggested, all at once?
From: st...@cfcentral.com.au
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Persistent Scopes and Memory
Date: Sun, 8 Nov 2009 05:17:12 +1100
I tried this on my CF8.01 64 Bit server and the server
wouldn't restart..had to roll
yep. put them all in, restarted the server and it wouldnt start
_
From: Mark Ireland [mailto:markinc...@hotmail.com]
Sent: Sunday, 8 November 2009 12:43 PM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Persistent Scopes and Memory
You tried everything he suggested, all
...@cfcentral.com.au wrote:
yep. put them all in, restarted the server and it wouldnt start
From: Mark Ireland [mailto:markinc...@hotmail.com]
Sent: Sunday, 8 November 2009 12:43 PM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Persistent Scopes and Memory
You
I read a blog by the Indian developers saying that CF is doing 'small' garbage
collection and 'large' garbage collection.
You can test this using the built in gc() function. Just watch the graph in the
Performance Monitor while running your test.
Date: Wed, 4 Nov 2009 15:44:11 -0800
Technically it's not 'CF' doing the GC, it's the JVM, and that is controlled
by whatever garbage collection settings you have in your jvm.config file.
I'm not sure what you mean by 'small' and 'large'? do you have a link to the
blog post?
Mark
On Fri, Nov 6, 2009 at 8:05 AM, Mark Ireland
Really, I don't think there is any specific way to tell.
The JVM does it's own optimisation about when and where a object is held,
depending on how long its been alive, and quite possibly how often it is
accessed and various other forms of black magic.
Is the real question you are asking: I am
yep, memory issues.
You can tell by storing something of a reasonable size in a persistent
scope, and watch the garbage collection to see what each generation is
doing, which is what I may do.
Barry
On Thu, Nov 5, 2009 at 12:46 PM, Mark Mandel mark.man...@gmail.com wrote:
Really, I don't think
When tracking down memory leaks for clients, I tend to use Eclipse Memory
Analyzer. I've also heard very good things about VisualVM, which I've been
meaning to look at.
Mark
On Thu, Nov 5, 2009 at 11:41 AM, Barry Chesterman barrychester...@gmail.com
wrote:
yep, memory issues.
You can tell by
I have been using JRockit Mission Control, which is very good.
I'm looking at overall memory at the moment to narrow down things which I
can test with JRockit Mission Control.
On Thu, Nov 5, 2009 at 1:43 PM, Mark Mandel mark.man...@gmail.com wrote:
When tracking down memory leaks for clients, I
One nasty one I have seen (this may not apply to you) on CF is if you are
running a SQL Server db that is under heavy load, the CF JDBC database
connection pool can leak like crazy.
It only happens under high load, but it can be a real pain to track down.
I don't know if that applies to you
13 matches
Mail list logo
