Jump to content
Changes to the Jaspersoft community edition download ×

Performance of large reports


2004 IR Help

Recommended Posts

By: mrp157 - mpilquist

Performance of large reports

2005-01-10 06:21

Does JasperReports handle reports in the tens of thousands of pages range? When tested on a new desktop quality machine, I ran out of memory trying to create a report > 10,000 pages. After adjust the VM settings, the report completed after 21 minutes of 100% CPU utilization. Is this the expected performance or am I doing something incorrectly?

 

 

 

 

By: chris - christinaku

RE: Performance of large reports

2005-01-10 16:32

Yeah.. i have the same question. Although i haven't try it yet but in theory it should hang the computer.

 

I am creating a reporting off a database in jasperviewer.

 

i noe that jasperviewer process a completely fill report generated by jasperPrint object . I try experimenting by inserting around 20 thousand record into my database and jasperviewer took a long time to display the report out as it is busy processing the fill report into the jasperPrint object. So, if i have 1 million records in the database, It would take ages to fill the jasperprint object. Even worse, the computer is going to run out of memory when processing such large amount of record as i pressume it is going to store the records retrieved somewhere in the local computer memory temporarily.

 

Hence, how to get around this problem?

Firstly i consider to create a new jasperPrint object for each different page. Hence, when i start to load the report at first, the jasperPrint will only contain 1 page of data record. If the user clicked next, then the i create another jasperPrint object to retrieve the second page of record and pass it to the jasperviewer to display. And so on. It would seem that i am wasting time creating a new jasperPrint object each time for a new page. However, is there any other ways to get around this problem?

 

Any suggestion and advice is greatly appreciated.

 

Thanks in advance,

Chris

 

 

 

 

By: CleverFool - cleverfool

RE: Performance of large reports

2005-01-11 03:42

Out of memmory error is easlily solved with this patch:

http://sourceforge.net/tracker/index.php?func=detail&aid=1080656&group_id=36382&atid=416705

 

 

 

 

By: Mike Warne - mwarne

RE: Performance of large reports

2005-01-11 12:05

10,000 pages in 21 minutes sounds pretty good to me!

That's like 8 pages per second!, or 480 per minute. It would probably take hours to print it with a laser printer.

 

I understand your concern however. 20 minutes 'feels' like a long time when you are waiting for the output, and I do not doubt that it could be speeded up using creative programming.

 

 

 

 

 

By: chris - christinaku

RE: Performance of large reports

2005-01-11 16:36

A person sure cannot view all the 10000 pages in one go. What if he just want to view a few pages of the report but then the data in the report is way too much. even if he don't want to see all of that, he does need to noe how many pages are there for printing rite? and jasperPrint still need to process so long to let the user see a few pages of the report.

 

 

 

 

By: robbiwan - robbiwan

RE: Performance of large reports

2005-01-12 19:03

I am also experiencing the same dilemma

 

 

 

 

By: Teodor Danciu - teodord

RE: Performance of large reports

2005-01-11 11:47

 

Hi,

 

This issue with large reports will be placed higher on

the TODO list. The generated content should be

streamed out page by page or something like that.

 

However, getting back to the first message on this

thread, I'm wondering, how long should it take for

a reasonable machine to render 10000 pages using

the AWT API?

And how long it should take a person to read all that?

 

Teodor

 

 

 

 

 

By: epowering - epowering

RE: Performance of large reports

2006-01-24 00:11

Hello,

are there one year Later any new technical features to print large Reports without blocking the client machine? My problem isn't the time it takes, but the client can't continue working while JasperReport is generating the report.

What do you think of generating the report on a server?

Any Possibilities?

While generating the Report, the processors capacities are used 100% :o/

 

Thanks a lot for your proposals

 

Josef Wagner (Germany)

 

 

 

 

By: Christiaan - christiaan_se

RE: Performance of large reports

2006-01-24 04:09

Hi,

I am also very much interested in the support for large reports. With a quick test I noticed that 1.1.1 can easily deal with very large reports. I would like to know if it is possible to show the first couple of pages in preview mode while the previewer is calculating the total number of pages in the mean time, instead of waiting till everything has finished.

 

kind regards,

Christiaan

 

 

 

 

By: Teodor Danciu - teodord

RE: Performance of large reports

2006-01-24 08:30

 

Hi,

 

We are now considering this improvement.

 

But even if it is going to be implemented in one

of the future versions, there will still be some

limitations that have to be considered.

 

The goal is to allow users view the first few

pages of a large document before the full document

was generated entirely.

But in case the document relies on the late-fill

capability that allows us to display

"Page 1 of 10000" kind of functionality, this

feature would not work.

Because we cannot know how many pages there are

going to be before finishing the whole document

we cannot start display the first page because

it is not yet complete.

 

This improvement would only work for documents

that do not rely on the mentioned late-fill

capability of the JasperReports engine.

 

Thank you,

Teodor

 

 

 

 

 

By: Alexandre Gomes - alegomes

RE: Performance of large reports

2006-01-24 05:18

With JasperReports 0.6.4 version, I can generate a report in 2 minutes (and I think it´s a lot of time to process only 300 pages). With 1.1.1 version, I´ve already waited for 30 minutes and no report came up.

 

Do you know any issue related to JasperReports version?

 

thanks

Alexandre Gomes

Brasil

 

 

 

 

By: Teodor Danciu - teodord

RE: Performance of large reports

2006-01-24 08:41

 

Hi,

 

There is nothing new in JR since 0.6.4 that

would cause such thing.

Reports could run slow not only because of the

rendering routines in JR, but also because of

a slow data source they are using.

 

What data source are you using with your reports?

You could run some tests in your environment

using a JREmptyDataSource instance with tens of

thounsands or more records inside to see if the

slowlyness is from the JR engine.

 

It would help if you could tell us more about

your system: what OS and what version of Java

are you using.

 

Thank you,

Teodor

 

 

 

 

 

By: Teodor Danciu - teodord

RE: Performance of large reports

2006-01-24 09:06

 

Hi,

 

Another possible reason for reports to run slow

is the amount of memory.

If you do not give the JVM enough memory, then

most of the time will get spent garbage collecting

things.

A clear indication of memory problems is when

the same report takes every time a different

number of seconds to execute. For instance, some

time it takes 3 seconds and the next time, with

the same data it takes 30 seconds.

 

How much memory do you allow the JVM to use?

 

Thank you,

Teodor

Link to comment
Share on other sites

  • 11 years later...
  • Replies 1
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Hi,

I read this thread,
Please could you explain me about the below point,

"In case the document relies on the late-fill 
capability that allows us to display 
"Page 1 of 10000" kind of functionality, this 
feature would not work. "

I am getting the report with footer contains,

<Current_page> of 

<total_Pages> - missing in few pages.

If my report has upto 100 pages, It works fine.

If my report has more than 100 pages, I am getting "<Current_page> of" in few pages.

Is there any limitation in page-count or document-size ?

Please could you help me on this regards.

Thanks,
Mari

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...