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; } } }

Performance issue

tintinhoking

I am new to BIRT. I create a test report by polling data from MySQL table which has 88,0000 rows.
(in mysql command line by doing select * from tbl; it takes 2.5 min to complete)
It is a simple select query with no where clause, no grouping...
The report engine is tune up (-Xms128M -Xmx1G) so that it run w/o "out of memory error"
But the report take 6 hours to complete.
Some thing really WRONG here. I include my rptdesign

Find more posts tagged with

Comments

kclark

BIRT shouldn't be timing out on you unless the default has been changed, have you checked your setting with MySQL yet?

tintinhoking

<blockquote class='ipsBlockquote' data-author="'kclark'" data-cid="111323" data-time="1352325493" data-date="07 November 2012 - 02:58 PM">
BIRT shouldn't be timing out on you unless the default has been changed, have you checked your setting with MySQL yet? </blockquote>
 
Thanks for your response kclark. 
 
I use BIRT v4.21 "out of the box" with all default setting. The only thing I add is the parameters to dynamically change the conection string. The problem is consistance (slow) in both IDE & runtime engine. 
 
I am not sure what MySQL setting you refer to - please specify. 
I create the same report (against same MySQL db... same setting) using Jasper. It takes <5 min to complete. 
 
The point is: there got to be something WORNG with the setup, that BIRT take >6 hrs to complete a report; which should take only ~5 min.

kclark

If you run the following in mysql 
 
<pre class='_prettyXprint _lang-auto _linenums:0'>
SHOW VARIABLES LIKE 'connect_timeout';
</pre>
 
That should print out what the default timeout it. Here's the output of mine 
 
<pre class='_prettyXprint _lang-auto _linenums:0'>
mysql> SHOW VARIABLES LIKE 'connect_timeout';
+

+
| Variable_name | Value |
+

+
| connect_timeout | 10 |
+

+
1 row in set (0.05 sec)
</pre>
 
If you wanted to change that to 60 seconds you would use 
 
<pre class='_prettyXprint _lang-auto _linenums:0'>
SET GLOBAL connect_timeout=60;
</pre>
 
It looks like the rptdesign in your first post didn't attach can you reattach that?

tintinhoking

<blockquote class='ipsBlockquote' data-author="'kclark'" data-cid="111352" data-time="1352390254" data-date="08 November 2012 - 08:57 AM">
If you run the following in mysql 
 
<pre class='_prettyXprint _lang-auto _linenums:0'>
SHOW VARIABLES LIKE 'connect_timeout';
</pre>
 
That should print out what the default timeout it. Here's the output of mine 
 
<pre class='_prettyXprint _lang-auto _linenums:0'>
mysql> SHOW VARIABLES LIKE 'connect_timeout';
+

+
| Variable_name | Value |
+

+
| connect_timeout | 10 |
+

+ 
| connect_timeout | 5 | 
+

+ 
1 row in set (0.00 sec) 
 
I will set as suggested & rerun

tintinhoking

<blockquote class='ipsBlockquote' data-author="'tintinhoking'" data-cid="111355" data-time="1352392916" data-date="08 November 2012 - 09:41 AM">
File is re-attached 
 
My setting is : 
+

+ 
| connect_timeout | 5 | 
+

+ 
1 row in set (0.00 sec) 
 
I will set as suggested & rerun </blockquote>
 
I set time out as suggested 
SET GLOBAL connect_timeout=60; 
+

+ 
| connect_timeout | 60 | 
+

+ 
1 row in set (0.00 sec) 
The report has been running for 2 hrs.... Doesn't sound like we hit the right spot. 
Any idea?