Community
Participate
Working Groups
Build Identifier: Birt 2.6 After upgrading our reports from Birt 2.3.0 to 2.6 we noticed that most of our reports are running slow after the application was started, but the subsequent runs are faster. I'm not sure if this is some new thing since 2.3 - like caching or configuration. After discussion with Jason on forum (http://www.birt-exchange.org/org/forum/index.php/topic/20400-performance-degradation-when-upgrading-from-birt-2-3-to-2-6/) he suggested the following, "The first time BIRT runs a report it is always slower as the engine has to crank up OSGi. ... you can open a bug entry to possibly prestart the engine." I've seen this issue mostly with reports that are dynamically generated, i.e, the whole table, header generated at run-time using the APIs. Reproducible: Always
It's expected behavior because many resources are loaded lazily when first time a reports get run.