Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Subject: Re: [MEMORY] Derby full fill my the JVM memory
From: yves pielusenet <yvespielusenet@free.fr>
To: Derby Discussion <derby-user@db.apache.org>
In-Reply-To: <4471F616.5040901@gmail.com>
References: <1148313606.7209.13.camel@localhost.localdomain>
	 <4471F616.5040901@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Date: Mon, 22 May 2006 20:38:23 +0200
Message-Id: <1148323103.7209.26.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit

How thank you I didn't see this answer before.
therefore, It seems complicated :c\


Le lundi 22 mai 2006 � 10:34 -0700, Stanley Bradbury a �crit :
> yves pielusenet wrote:
> 
> >Hello,
> >I have this error : java.lang.OutOfMemoryError: Java heap space
> >So I used a profiler to see what was wrong. I have very lots of object
> >of that classes :
> >org.apache.derby.impl.store.raw.data.StoreRecordHeader
> >org.apache.derby.impl.store.raw.data.RecordId
> >(I can't find those classes into derby javadoc :c( )
> >  
> >
> ====  SNIP ===
> 
> Yes, record headers are objects created when a page is brought into the 
> cache.  The maxHeap to pageCache ratio I talked about in my previous 
> message accounts for these and the many other objects created to support 
> the activities of the Derby database engine.
> 
> Please see the information in my response to your previous post (Iterate 
> over big table...) and if you are still having problems after increasing 
> the ratio of the JVM-maximum-Heap to Derby-pageCache please post the 
> ratio you are using and the settings for maxHeap and pageCache.
> 
> In case you missed the reply the archive of message can be viewed at:
> http://www.nabble.com/forum/ViewPost.jtp?post=4476273
> 
> HTH
> 
>