Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 314185 - Improve time to run & render reports
Summary: Improve time to run & render reports
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Birt-ReportEngine-inbox@eclipse.org CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-24 22:19 EDT by Carsten Lund CLA
Modified: 2010-05-25 04:52 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carsten Lund CLA 2010-05-24 22:19:09 EDT
Build Identifier: 2.5.0

Current the run and render report seems mostly sequential. 
It seems that there are some fairly easy ways that running multiple threads could improve performance.
- run data set in parallel. If a report design has multiple data set; retrieve them in parallel.
- generate charts in parallel.

It is likely that this is not always semantically the same as the current implementation, and thus not backward compatible. But create a property that determine the maximum number of parallel threads used and have the default be 1.



Reproducible: Always
Comment 1 Wei Yan CLA 2010-05-25 04:52:00 EDT
Actually the user can parallel the run task and the render task in current implementation.

The run task accepts a IPageHandler event call back, the user can register a handler to receive the events and start to render the report once the page has been created.