Performance problems with really big reports

[2005 IR Help]

By: Diego Buzzalino - chuza

Performance problems with really big reports

2003-09-03 09:49

im having problems with big reports because of the high use of heap of Jasper.

I made many tests with the options -Xms:100m -Xmx:350m and all worked fine during mid-load tests.

But for really big tests, all hang-up for hours.

Using a profiler I could define that:

- 5% of the time is the process of compiliation (.xml to .jasper)

- 60% is the time of filling the report IN MEMORY (.jasper to .jrprint)

- 35% is the export to PDF (.jrprint to .pdf)

 

the question is..

is there an easy way of avoid filling the report in memory and try to do that in the .jrprint file?

(It will take a little more time, but It wil never be running out of resources)

 

Has anyone done something like this?

Changed the Jasper code?

 

let me now...

 

thanks in advance

 

 

 

 

By: Barra - booleong

RE: Performance problems with really big reports

2004-01-05 02:36

I had the same problem.

However I am not as patient as you, waiting for it to finish hours after.

I thought it hung.

 

The weird thing is, I didn't have this problem before. Modified some of my sub reports and suddenly exporting to a file takes ages.

Also, if I export to a HTML file, it takes up few hundred Mbytes to more than 1GByte !!

 

Really have no idea what's happening.