From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27968 invoked by alias); 18 Jan 2010 17:56:35 -0000 Received: (qmail 27958 invoked by uid 22791); 18 Jan 2010 17:56:34 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail3.caviumnetworks.com (HELO mail3.caviumnetworks.com) (12.108.191.235) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 18 Jan 2010 17:56:29 +0000 Received: from caexch01.caveonetworks.com (Not Verified[192.168.16.9]) by mail3.caviumnetworks.com with MailMarshal (v6,7,2,8378) id ; Mon, 18 Jan 2010 09:56:33 -0800 Received: from caexch01.caveonetworks.com ([192.168.16.9]) by caexch01.caveonetworks.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 18 Jan 2010 09:56:27 -0800 Received: from dd1.caveonetworks.com ([12.108.191.236]) by caexch01.caveonetworks.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 18 Jan 2010 09:56:27 -0800 Message-ID: <4B54A0CB.3090301@caviumnetworks.com> Date: Mon, 18 Jan 2010 17:56:00 -0000 From: David Daney User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Hans Boehm CC: Andrew Haley , Justin Santa Barbara , "java@gcc.gnu.org" Subject: Re: How to minimize (unshareable) memory usage? References: <4B542EE9.7030503@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact java-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-owner@gcc.gnu.org X-SW-Source: 2010-01/txt/msg00024.txt.bz2 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