[Mulgara-general] Mulgara size limits

Life is hard, and then you die ronald at innovation.ch
Tue Jul 8 16:32:31 PDT 2008


On Tue, Jul 08, 2008 at 04:36:03PM -0400, Alex Hall wrote:
> Chuck Borromeo wrote:
> > Hi Everyone,
> >   I just wanted to check to see if anyone has figured out the issue I was encountering when I tried to load RDF/XML files larger than 98 MB.
> 
> I've been looking at this off and on since last week, but with little 
> results to show.  I can tell the offending class that is filling the 
> heap, and I can tell where it is being allocated, but I haven't been 
> able to track down where the references to the class are not being 
> released.  To add a degree of difficulty, I'm developing on a 32-bit 
> Windows laptop so I can't duplicate the conditions causing the 
> out-of-memory error.
[snip]
> In both cases, I would also gather the heap profile, just to be sure 
> that the AVLNode class is still the culprit.
[snip]

In this case I'd recommend run under jdk 1.6 and get a binary heap
dump shortly before it runs out of memory using

  jmap -dump:live,format=b,file=heap.bin <mulgara-pid>

The resulting dump can analyzed via jhat, or I think some of the other
profilers may be able to read that too. The problem is that the
resulting dump can be quite large, but if it's manageable maybe you
can upload somewhere where somebody can grab it to take a look;
otherwise we may need you to poke around at it.


  Cheers,

  Ronald



More information about the Mulgara-general mailing list