|
| Re: Speed issues & profiling [message #662408 is a reply to message #662246] |
Wed, 30 March 2011 10:50  |
Jason Weathersby Messages: 9167 Registered: July 2009 |
Senior Member |

|
|
How long a report takes to run depends heavily on the number of rows of
data, but more than that how many nested tables and aggregations are
used. Is this a straight listing report? BTW is you are using the
engine api to run your reports only startup and shutdown the engine
once. Wrap the call to get the engine in a singleton and use it to
create a task for each new report. To see how this is done in a webapp
take a look at this:
http://wiki.eclipse.org/Servlet_Example_%28BIRT%29_2.1
You should be able to modify the code to do it in a standalone app as
well. Make sure to look at the bottom of the wiki page for updated code.
Jason
On 3/29/2011 4:32 PM, azuniga wrote:
> I'd like to know if there are any tools available for profiling my
> report generation code. I'm currently using System.currentTimeMillis()
> to profile the section of code that I'm using for opening the .rptdesign
> file, setting all the options, running the task and closing the task and
> shutting down the platform. For a really large report, more than 500
> lines of records, I time it at around 30 seconds. Is this normal? Are
> there any optimizations I can make? For small reports of course it
> doesn't take this long, but I see closing the task and shutting down the
> platform alone takes about 7 seconds. Thx for any help or advice. Also,
> if you may have any links for me to follow about this that would be cool.
Jason Weathersby
BIRT Exchange
|
|
|
Powered by
FUDForum. Page generated in 0.01519 seconds