Mailing-List: contact poi-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "POI Users List" <poi-user@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of krisztian.koller@gmail.com
 designates 64.233.182.191 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=JVlZSfV5Eb3bvQrK9HNtIc7+hvspHjc45jzNV5PqYwcZcWyXMpPf+6YDrBAzzMVRWb3ioKnRIWH7wsKfaSp9SUAeStuUwSRqkKxLvUJNsXTbD+JzucJD7aiaHlYuGqi59O9g5iZibkx0N1C038zVF8e67XWiLE2hQOALnCIKACc=
Message-ID: <4089cf250606070424j5de63ac7g1f125c1c7547363a@mail.gmail.com>
Date: Wed, 7 Jun 2006 13:24:15 +0200
From: "Koller Krisztian" <krisztian.koller@gmail.com>
To: "POI Users List" <poi-user@jakarta.apache.org>, danny@apache.org
Subject: Re: hssf -> long running Garbage Collector
In-Reply-To: <5ec229170606070117n488c4d0fh3f291da9eaa1d7cf@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_605_20446993.1149679455305"
References: <4089cf250606070019m4b25e42fr7cb4afb49d37567@mail.gmail.com>
	 <5ec229170606070117n488c4d0fh3f291da9eaa1d7cf@mail.gmail.com>

------=_Part_605_20446993.1149679455305
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

Thanks.

We had the following jvm parameters:

-Xms50m -Xmx512m

I have logged the free memory size after every new row creation in the excel
sheet.
It runs very fast until we have enough free memory (and the whole
application is ok too).
But after we run out of the free memory something is happening (i think the
jvm runs the gc)
and the whole application is unavailable for 2-3 minutes.

The excel file is about 3-4 Mb.

Regards,
Krisztian

On 6/7/06, Danny Angus <danny.angus@gmail.com> wrote:
>
> nothing will "block" the garbage collector, but you may want to modify
> certain settings to make it more efficient for your circumstances.
>
> I'd suggest you increase the sizes of the new space (-Xmn) if you are
> running through a lot of loops, increase the starting size of the heap
> (-Xms) and the size of the permanent space too. There is a problem
> whereby failure to allocate into the permanent space results in a loop
> of compating collections, the symptom of which is 100% cpu use an no
> work done.
>
> The parallel collectors can also use a lot of CPU if initial sizes
> aren't big enough.
>
> If you want to know more why not attend my talk on the subject at
> ApacheconEU ... it'll be great :-)
>
> d.
>
> On 07/06/06, Koller Krisztian <krisztian.koller@gmail.com> wrote:
> > Hi
> >
> > We are using the POI-HSSF to generate ms excel files. It works fine if
> the
> > excel sheet contains only a few rows. In our production environment the
> > excel files have more then 5000 rows. (20-30 columns / row)
> > Some times during the generation of the excel sheet the jvm executes the
> > garbage collector. Unfortunately the garbage collector runs more then
> two
> > minutes long.
> > Something - maybe the POI objects in the memory? - blocks the gc (and
> the
> > whole application)...
> > (without the poi objects the gc runs very fast (only a few millisec))
> >
> > Any idea please?
> >
> > Regards,
> > Krisztian
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-user-unsubscribe@jakarta.apache.org
> Mailing List:     http://jakarta.apache.org/site/mail2.html#poi
> The Apache Jakarta Poi Project:  http://jakarta.apache.org/poi/
>
>

------=_Part_605_20446993.1149679455305--