| Caching for performance [message #170972] |
Fri, 16 June 2006 11:11 |
Eclipse User |
|
|
|
Originally posted by: blev.whocares.com
What are the rules governing lifecycle of ReportEngine, ReportDesign and
other objects? In the context of a webapp, can I load all my report
designs once into a cache at app startup and only generate rptdocuments on
demand?
Do I need one ReportEngine instance per ReportDesign instance or can I
share my ReportEngine instance for all ReportDesign instances in a
multithreaded webapp environment?
In the context of caching my ReportEngine and ReportDesign instances, at
what points do I 'destroy' and 'shutdown' my ReportEngine in the lifecycle
of webapp requests?
I apologize if there are docs pertaining to this that I should've read. If
so, could you point me to the relevant documentation? or any white paper
on tuning performance in using BIRT as an embedded solution? As I see it,
the product is feature rich but there's potential for improvement in
performance.
Thanks in advance.
- Brian
|
|
|
Powered by
FUDForum. Page generated in 0.08602 seconds
Home