Re: Outrigger memory leak?

Greg Trasuk wrote:
> On Wed, 2007-01-03 at 11:52, Gregg Wonderly wrote:
>> Greg Trasuk wrote:
>>>         Am I missing something in the configuration?  The problem is
>>> independent of whether Outrigger is run under Harvester or from the
>>> Launch-All script in the starter kit.  I haven't found any other bug
>>> reports, and I find it hard to believe I've found a bug in a mature
>>> product.  Any suggestions?
>> Can you try the same application with Blitz to see if there is any difference?
>> I'd guess that you are not using enough heap.  Are you configuring -mx512m on
>> the command line, or how are you starting the JVM that you think has a 512M heap?
>>
>> Gregg Wonderly
>
> Hi Gregg:
>
>         Thank you for responding.  Blitz is my next step.  I was hoping to use
> Outrigger because I've already got it running inside a Harvester
> container, whereas I'll have to either deploy Blitz separately or write
> a wrapper to run inside Harvester (not a bad idea anyway, but extra
> work).
>

Well there's LocalSpace which might serve as a useful example for you to
work from or if you can give me more details on what's involved I'll see
if I can't hack it up for you.

>         I've played with -Xmx settings up to 1GB; I always get the
> out-of-memory condition, it just takes more operations.  I'm in the
> process of trying to track it down with the Netbeans profiler.  One
> thing that's interesting is that although the "Used Memory" indicator
> always gets to the total heap size, the detail results show only a tiny
> fraction of that memory.  I don't know whether that's a sampling
> artifact or whether the memory is going somewhere that the profiler
> doesn't pick up.
>

So this may not be it but I've seen similar behaviours in other cases -
might be worth hooking up visualgc to see what's going on.  What I've
seen with Blitz is similar and it seems to come down to the garbage
collector gradually increasing heap to:

(a)     Attempt to find some more objects worth tenuring

(b)     Allow the program longer to run between collections

Whilst all of that goes on Blitz itself will for many tests happily be
using just 7-24Mb consistently so the allocated heap grows larger but
Blitz's usage of the heap remains way lower.

Dan.

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html