This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: How to minimize (unshareable) memory usage?

From: David Daney <ddaney at caviumnetworks dot com>
To: Hans Boehm <Hans dot Boehm at hp dot com>
Cc: Andrew Haley <aph at redhat dot com>, Justin Santa Barbara <justin at fathomdb dot com>, "java at gcc dot gnu dot org" <java at gcc dot gnu dot org>
Date: Mon, 18 Jan 2010 09:56:27 -0800
Subject: Re: How to minimize (unshareable) memory usage?
References: <a3fa9dad1001180133h252738bfl5d887cb2670475e3@mail.gmail.com> <a3fa9dad1001180140y3bc2cb2dmd6ebd342b95f5a6b@mail.gmail.com> <4B542EE9.7030503@redhat.com> <alpine.LNX.1.10.1001181104150.30290@192.168.2.2>

Hans Boehm wrote:


The output of GC_dump() might also tell you something.  It won't
list heap sections associated with the system malloc.  Note that the
collector doesn't insist on a contiguous heap.

And if you want even more details about how memory is being used, there is always the gnu.gcj.util.GCInfo class. That and the gnu.gcj.tools.gc_analyze.MemoryAnalyze post processor give quite a bit of information.

These facilities are built on top of GC_dump() but provide a more detailed analysis of the contents of the memory.

David Daney

Follow-Ups:
- Re: How to minimize (unshareable) memory usage?
  - From: Justin Santa Barbara

References:
- How to minimize (unshareable) memory usage?
  - From: Justin Santa Barbara
- Re: How to minimize (unshareable) memory usage?
  - From: Andrew Haley
- Re: How to minimize (unshareable) memory usage?
  - From: Hans Boehm

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]