Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: uima-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of twgoetz@gmx.de designates
 213.165.64.20 as permitted sender)
Message-ID: <46CBF3DA.6070609@gmx.de>
Date: Wed, 22 Aug 2007 10:29:14 +0200
From: Thilo Goetz <twgoetz@gmx.de>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: uima-user@incubator.apache.org
Subject: Re: Questions regarding the Heap class and the heap size.
References: <ad72a08f0708201806n4168bc61yb899850694bfc6e@mail.gmail.com>
	 <46CA4DC0.7070905@schor.com> <46CADE9C.1030204@gmx.de>
 <ad72a08f0708211452s1ab79edby8bcd021375959d21@mail.gmail.com>
In-Reply-To: <ad72a08f0708211452s1ab79edby8bcd021375959d21@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Danai Wiriyayanyongsuk wrote:
> Thanks Marshall and Thilo for shading some light.
> 
> 
> 
> Besides the instances of feature structures (which I guess that it usually
> does not require much of the "Heap.heap" space), are there any kinds of
> information that might require big chunks of the "Heap.heap" space e.g.
> hundreds of array's elements that I should be aware of?
[...]

All the data that your analysis generates (with a few exceptions) lives
on the heap.  So depending on how many annotations you create, the heap
may grow very large.  It is usually several times the size of the input
document.  I've personally had applications where the CAS (most of which
is the heap) would on average be about 50 times the size of the input
document.

Unfortunately there is no good way to get at this data via APIs.  The
way I got this information was by triggering Java heap dumps and looking
at the size of the data structures on the Java heap.

HTH,
Thilo