nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Report opens very slow

dragosss24

I have a report. When I try to preview it, takes more then normal time. I tried the report debug. Here is what I get: 
 
Oct 04, 2012 10:39:56 AM org.eclipse.birt.report.debug.internal.core.vm.ReportVMServer start 
<pre class='_prettyXprint _lang-auto _linenums:0'>INFO: [Server] client accepted
Oct 04, 2012 10:39:56 AM org.eclipse.birt.report.debug.internal.core.vm.ReportVMServer$1 run
INFO: [Server] enter request dispatching
Oct 04, 2012 10:39:56 AM org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher configEngine
INFO: User class path received:
>>>> Compiled Source:
new Date()
>>>> end compilation.
>>>> Compiled Source: unnamed script
params["Ship"]
>>>> end compilation.
Oct 04, 2012 10:39:57 AM org.eclipse.birt.report.data.oda.jdbc.Connection open
WARNING: JDBC connection: net.sourceforge.jtds.jdbc.ConnectionJDBC3@6e48cd is opened
>>>> Compiled Source: unnamed script
params["Ship"]
>>>> end compilation.
>>>> Compiled Source: unnamed script
params["Begin time"]
>>>> end compilation.
>>>> Compiled Source: unnamed script
params["End time"]
>>>> end compilation.
>>>> Compiled Source:
row.__rownum % 2
>>>> end compilation.
>>>> Compiled Source:
0
>>>> end compilation.
>>>> Compiled Source:
null
>>>> end compilation.
Oct 04, 2012 10:40:44 AM org.eclipse.birt.report.data.oda.jdbc.Connection close
WARNING: JDBC connection: net.sourceforge.jtds.jdbc.ConnectionJDBC3@6e48cd is closed
Oct 04, 2012 10:40:44 AM org.eclipse.birt.report.debug.internal.core.vm.ReportVMServer$1 run
WARNING: [Server] client disconnected</pre>
 
I have 3 parameters. 
 
Can you please help me with this?

Find more posts tagged with

Comments

dragosss24

mwilliams

You're previewing from the designer? Is it a large report? What version of BIRT are you using?

dragosss24

<blockquote class='ipsBlockquote' data-author="'mwilliams'" data-cid="110156" data-time="1349378838" data-date="04 October 2012 - 12:27 PM">
You're previewing from the designer? Is it a large report? What version of BIRT are you using? </blockquote>
 
Yes, from the designer, not a very large report, version 2.6.1

mwilliams

Using jndi?

dragosss24

<blockquote class='ipsBlockquote' data-author="'mwilliams'" data-cid="110197" data-time="1349492402" data-date="05 October 2012 - 08:00 PM">
Using jndi? </blockquote>
 
Yes Williams, we are using JNDI URL: java:comp/env/jdbc/OurDatasource

johnw

If all things are normal with your BIRT report, 2 main things will affect report execution performance.

1. Data Set Optimization
2. Report Design Complexity

With item 1, you will need to run some sort of query profiler to make sure your query is hitting all of its indexes, make sure your database is optimized and that its cost base optimizer is working correctly, etc. If you can run the same query with the same values in a straight database and not have performance issues, than you can start to look at the report design.

2. Lots of different things can cause this. Normally this tends to happen when you do lots of changes to the design, start nesting tables, grids, adding styles, then removing them, and just generally playing around with the design. What ends up happening is there are lots of artifacts that get left behind. To determine if this is a problem, try taking the query and creating a new report design, with no styles or layouts, and running with just a straight table. If it runs fast, then it may be an issue with the report engine. If not, then its a problem with the original design.

if it is a problem with the original design, if you can't just dump the original design and recreate it, try to isolate if it is a problem with the run portion or the render portion. Add a logging statement to the beforeFactory, afterFactory, beforeRender, afterRender statements in the report bodies scripting tabs. You will want to log the execution times to determin if it is a problem with rendering the look and feel, or generating the data. You can get more information here: http://birtworld.blogspot.com/2010/01/quick-and-dirty-logging.html

Start with those steps, and let us know the results.

mwilliams

I found out why you're getting the "WARNING". It was a bug in 2.6.1: https://bugs.eclipse.org/bugs/show_bug.cgi?id=326616