Hi Paulo,
Thanks for all your help. I don't mind if the jar file uses up 5% when it is used for the first time. And if the reports are generated 10 - 15 times then each does not hog up 5%...
However, I noted that the free memory steadily decreases after every report generation. As a test case ... I generated 15 reports one after another using the same session. No other module of the application was accessed, and no other application hosted on the server was accessed.
I found that my free memory is steadily decreasing.... Here is the copy of the relevant portion of my weblogic log. After 15 reports are generated my free memory is reduced to about 73%.
Shubhrajit
GC[0] in 19 ms: (128Mb, 97% free) -> (128Mb, 98% free)
GC[0] in 35 ms: (128Mb, 97% free) -> (128Mb, 98% free)
GC[0] in 39 ms: (128Mb, 97% free) -> (128Mb, 97% free)
GC[0] in 19 ms: (128Mb, 96% free) -> (128Mb, 97% free)
GC[0] in 36 ms: (128Mb, 96% free) -> (128Mb, 97% free)
GC[0] in 27 ms: (128Mb, 95% free) -> (128Mb, 96% free)
GC[0] in 48 ms: (128Mb, 95% free) -> (128Mb, 95% free)
GC[0] in 12 ms: (128Mb, 94% free) -> (128Mb, 95% free)
GC[0] in 12 ms: (128Mb, 94% free) -> (128Mb, 95% free)
GC[0] in 12 ms: (128Mb, 94% free) -> (128Mb, 95% free)
GC[0] in 14 ms: (128Mb, 94% free) -> (128Mb, 95% free)
GC[0] in 29 ms: (128Mb, 94% free) -> (128Mb, 95% free)
GC[0] in 49 ms: (128Mb, 94% free) -> (128Mb, 94% free)
GC[0] in 18 ms: (128Mb, 93% free) -> (128Mb, 94% free)
GC[0] in 23 ms: (128Mb, 93% free) -> (128Mb, 94% free)
GC[0] in 11 ms: (128Mb, 92% free) -> (128Mb, 94% free)
GC[0] in 11 !
ms: (128Mb, 92% free) -> (128Mb, 94% free)
GC[0] in 16 ms: (128Mb, 92% free) -> (128Mb, 93% free)
GC[0] in 45 ms: (128Mb, 92% free) -> (128Mb, 93% free)
GC[0] in 26 ms: (128Mb, 91% free) -> (128Mb, 92% free)
GC[0] in 33 ms: (128Mb, 91% free) -> (128Mb, 92% free)
GC[0] in 13 ms: (128Mb, 90% free) -> (128Mb, 92% free)
GC[0] in 11 ms: (128Mb, 90% free) -> (128Mb, 92% free)
GC[0] in 13 ms: (128Mb, 90% free) -> (128Mb, 92% free)
GC[0] in 21 ms: (128Mb, 90% free) -> (128Mb, 91% free)
GC[0] in 49 ms: (128Mb, 90% free) -> (128Mb, 91% free)
GC[0] in 18 ms: (128Mb, 89% free) -> (128Mb, 90% free)
GC[0] in 30 ms: (128Mb, 89% free) -> (128Mb, 90% free)
GC[0] in 12 ms: (128Mb, 89% free) -> (128Mb, 90% free)
GC[0] in 37 ms: (128Mb, 89% free) -> (128Mb, 90% free)
GC[0] in 13 ms: (128Mb, 89% free) -> (128Mb, 90% free)
GC[0] in 27 ms: (128Mb, 89% free) -> (128Mb, 89% free)
GC[0] in 47 ms: (128Mb, 89%!
free) -> (128Mb, 89% free)
GC[0] in 18 ms: (128Mb, 87% free) -> (128Mb, 89% free)
GC[0] in 23 ms: (128Mb, 87% free) -> (128Mb, 89% free)
GC[0] in 11 ms: (128Mb, 87% free) -> (128Mb, 89% free)
GC[0] in 16 ms: (128Mb, 87% free) -> (128Mb, 88% free)
GC[0] in 17 ms: (128Mb, 87% free) -> (128Mb, 88% free)
GC[0] in 44 ms: (128Mb, 87% free) -> (128Mb, 88% free)
GC[0] in 25 ms: (128Mb, 86% free) -> (128Mb, 87% free)
GC[0] in 31 ms: (128Mb, 86% free) -> (128Mb, 87% free)
GC[0] in 13 ms: (128Mb, 85% free) -> (128Mb, 87% free)
GC[0] in 11 ms: (128Mb, 85% free) -> (128Mb, 87% free)
GC[0] in 13 ms: (128Mb, 85% free) -> (128Mb, 87% free)
GC[0] in 20 ms: (128Mb, 85% free) -> (128Mb, 86% free)
GC[0] in 48 ms: (128Mb, 85% free) -> (128Mb, 86% free)
GC[0] in 19 ms: (128Mb, 84% free) -> (128Mb, 85% free)
GC[0] in 27 ms: (128Mb, 84% free) -> (128Mb, 85% free)
GC[0] in 12 ms: (128Mb, 84% free) -> (1!
28Mb, 85% free)
GC[0] in 11 ms: (128Mb, 84% free) -> (128Mb, 85% free)
GC[0] in 15 ms: (128Mb, 84% free) -> (128Mb, 85% free)
GC[0] in 31 ms: (128Mb, 84% free) -> (128Mb, 84% free)
GC[0] in 47 ms: (128Mb, 83% free) -> (128Mb, 84% free)
GC[0] in 16 ms: (128Mb, 82% free) -> (128Mb, 84% free)
GC[0] in 24 ms: (128Mb, 82% free) -> (128Mb, 83% free)
GC[0] in 10 ms: (128Mb, 82% free) -> (128Mb, 83% free)
GC[0] in 104 ms: (128Mb, 82% free) -> (128Mb, 83% free)
GC[0] in 17 ms: (128Mb, 82% free) -> (128Mb, 83% free)
GC[0] in 47 ms: (128Mb, 82% free) -> (128Mb, 83% free)
GC[0] in 23 ms: (128Mb, 81% free) -> (128Mb, 82% free)
GC[0] in 35 ms: (128Mb, 81% free) -> (128Mb, 82% free)
GC[0] in 13 ms: (128Mb, 80% free) -> (128Mb, 82% free)
GC[0] in 11 ms: (128Mb, 80% free) -> (128Mb, 82% free)
GC[0] in 14 ms: (128Mb, 80% free) -> (128Mb, 82% free)
GC[0] in 20 ms: (128Mb, 80% free) -> (128Mb, 81% free!
)
GC[0] in 44 ms: (128Mb, 80% free) -> (128Mb, 81% free)
GC[0] in 20 ms: (128Mb, 79% free) -> (128Mb, 80% free)
GC[0] in 31 ms: (128Mb, 79% free) -> (128Mb, 80% free)
GC[0] in 11 ms: (128Mb, 79% free) -> (128Mb, 80% free)
GC[0] in 11 ms: (128Mb, 79% free) -> (128Mb, 80% free)
GC[0] in 12 ms: (128Mb, 79% free) -> (128Mb, 80% free)
GC[0] in 29 ms: (128Mb, 79% free) -> (128Mb, 79% free)
GC[0] in 47 ms: (128Mb, 78% free) -> (128Mb, 79% free)
GC[0] in 17 ms: (128Mb, 77% free) -> (128Mb, 78% free)
GC[0] in 27 ms: (128Mb, 77% free) -> (128Mb, 78% free)
GC[0] in 10 ms: (128Mb, 77% free) -> (128Mb, 78% free)
GC[0] in 11 ms: (128Mb, 77% free) -> (128Mb, 78% free)
GC[0] in 16 ms: (128Mb, 77% free) -> (128Mb, 78% free)
GC[0] in 56 ms: (128Mb, 77% free) -> (128Mb, 77% free)
GC[0] in 27 ms: (128Mb, 76% free) -> (128Mb, 77% free)
GC[0] in 32 ms: (128Mb, 76% free) -> (128Mb, 77% free)
GC[0] in 1!
2 ms: (128Mb, 75% free) -> (128Mb, 77% free)
GC[0] in 12 ms: (128Mb, 75% free) -> (128Mb, 77% free)
GC[0] in 13 ms: (128Mb, 75% free) -> (128Mb, 76% free)
GC[0] in 21 ms: (128Mb, 75% free) -> (128Mb, 76% free)
GC[0] in 50 ms: (128Mb, 75% free) -> (128Mb, 76% free)
GC[0] in 19 ms: (128Mb, 74% free) -> (128Mb, 75% free)
GC[0] in 32 ms: (128Mb, 74% free) -> (128Mb, 75% free)
GC[0] in 13 ms: (128Mb, 73% free) -> (128Mb, 75% free)
GC[0] in 11 ms: (128Mb, 73% free) -> (128Mb, 75% free)
GC[0] in 15 ms: (128Mb, 73% free) -> (128Mb, 75% free)
GC[0] in 28 ms: (128Mb, 73% free) -> (128Mb, 74% free)
GC[0] in 48 ms: (128Mb, 73% free) -> (128Mb, 74% free)
GC[0] in 18 ms: (128Mb, 72% free) -> (128Mb, 73% free)
GC[0] in 24 ms: (128Mb, 72% free) -> (128Mb, 73% free)
GC[0] in 10 ms: (128Mb, 72% free) -> (128Mb, 73% free)
GC[0] in 14 ms: (128Mb, 72% free) -> (128Mb, 73% free)
Some elements are cached to be used next time. What you have to see is if
generating 10 documents the memory stays at 5% aftwards or not. It's also
useful to see if those 5% referres exclusively to iText and remember that
the jar itself takes 1.2M of class space and something more after being
loaded, this without even creating a single object. Maybe 5% is not such a
big number.
Best Regards,
Paulo Soares
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, January 31, 2002 11:40
> To: Paulo Soares; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: RE: [iText-questions] Memory Hogging
>
> Hi,
>
> I understand that java will be heavy... however 5% memory remains used
> even after the request has b! een served. I expected that most of the things
> will be garbage collected since the thread has completed execution, page
> has been thrown to the client and all references removed.
>
> BTW I was creating about 150 objects in the page other than Strings. Most
> of the Strings I have wrapped up in Paragraphs and the Paragraphs in
> cells. I have created only 2 font objects which I am using in all the
> paragraphs.
>
> Shubhrajit
>
>
>
> "Paulo Soares" wrote:
>
>
>
>
> Memory usage depends on what you put inside the report (images,
> fonts,
> number of pages) and I've yet to find a "light-weight" java
> application. If
> more users access your application you'll have to add more memory,
> there's
> no miracles.
>
> Best Regards,
> Paulo Soares
>
> > -----Original Message-----
> > From:! [EMAIL PROTECTED]
> [SMTP:[EMAIL PROTECTED]]
> > Sent: Thursday, January 31, 2002 11:04
> > To: [EMAIL PROTECTED]
> > Subject: [iText-questions] Memory Hogging
> >
> > Hi,
> >
> > I am new to this tool. I am using it inside weblogic to generate
> reports
> > on the fly. Our weblogic runs with an assigned memory of 128 MB.
> >
> > Since we had some performance issues earlier, we run weblogic in
> Verbose
> > mode to see the garbage collection activities. Currently I am the
> only> user accessing the test server and I am accessing only the PDF
> generation
> > module.
> >
> > I found that after every report , this tool is hogging up about 5%
> of the
> > memory. Is it an error in the part of the tool or I am using it
> wrongly
> > ???
> >!
> > This might turn into a big issue as in my production server 150
> users will
> > access the application, which has other heavy modules.
> >
> > Any help is appreciated.
> >
> > Shubhrajit
> >
> >
> >
> >
> >
> >
> >
> > _____
> >
> > Get Your Private, Free E-mail at Mailmetoday.com
>
>
> _____
>
> Get Your Private, Free E-mail at Mailmetoday.com
Get Your Private, Free E-mail at Mailmetoday.com http://mailmetoday.com
