[Mulgara-general] Mulgara size limits

[Life is hard, and then you die]

On Tue, Jul 01, 2008 at 03:35:16PM -0400, Alex Hall wrote:
> Chuck Borromeo wrote:
[snip]
> The logical next step would be to get a heap profile.  You can do this 
> by adding "-Xrunhprof:heap=sites" as a Java VM argument.  The resulting 
> java.hprof.txt will probably be too big to send to the list in its 
> entirety, but if you can cut and paste the table at the end of the file, 
> or post the whole file somewhere for us to download, somebody can take a 
> look and see if there's anything out of the ordinary.

I can't say much about Mac OS X specifics, but on Linux in jdk 1.5 the
-Xrunhprof significantly slows things down and increases the memory
footprint. This has changed dramatically with 1.6, where you can run
without any extra command line params and then generate a heap dump at
any time with 'jmap -heap <pid>' (or 'jmap -dump:...' for a binary
dump usable by jhat). (Btw., jmap exists for 1.5 too, but at least on
Linux I've found it extremely unreliable, wedging things more often
than not, whereas on 1.6 I've not run into any issues so far).

I know you said you're running 1.5, but if you may want to try 1.6 for
debugging.


  Cheers,

  Ronald