Massive performance problems in Birt-Designer

Hi!

I create quite large reports (~1.5 MB) with Birt 2.6.0.
In the designer I have to wait quite a long time (i measured 1min 47sec) just for adding a column to a table for example (deleting is faster with about 1 minute waiting time).
The CPU-utilization is 50% (one CPU-core) the whole time I have to wait.

The table has only got 12 rows and 7 columns, so I think this should take less than 5 seconds.

Other performance values:
Creating a 1x1 grid -> 3 sec
adding a column to this grid -> 8.5 sec
saving the report to the file on the HDD -> 1 sec

I have the same problems on other computers.
My current hardware is:
Intel Core 2 Duo T7200 (2 x 2Ghz)
4GB RAM

How can I improve the performance?
Or what am I doing wrong?

Peter

Find more posts tagged with

Comments

johnw

Have you tried upping the memory settings in the eclipse.ini? It starts with an initial size of 40m, I usually set mine to 256, an upper limit of 1024, and a MaxPermGen of 1024.

Peter P.

<blockquote class='ipsBlockquote' data-author="'johnw'" data-cid="70779" data-time="1290802580" data-date="26 November 2010 - 01:16 PM">
Have you tried upping the memory settings in the eclipse.ini? It starts with an initial size of 40m, I usually set mine to 256, an upper limit of 1024, and a MaxPermGen of 1024. </blockquote>
 
As far as I've tested jet, I can say that the memory settings don't effect the performance. 
 
Edit: 
Are there other settings of eclipse where I can influence the performance?

johnw

The Java you are using might play a key factor (32 bit vs 64 bit, or if your on Linux, using the sun Java works much better than the GNU OpenJava). Make sure you are using the correct Java for what architecture you have.

Outside of that, I'm a little stumped. I cant figure out any reason why it would be so slow. Is it slow in other perspectives, like the Java perspective, or in debug?

Peter P.

<blockquote class='ipsBlockquote' data-author="'johnw'" data-cid="70823" data-time="1291068499" data-date="29 November 2010 - 03:08 PM">
The Java you are using might play a key factor (32 bit vs 64 bit, or if your on Linux, using the sun Java works much better than the GNU OpenJava). Make sure you are using the correct Java for what architecture you have. 
 
Outside of that, I'm a little stumped. I cant figure out any reason why it would be so slow. Is it slow in other perspectives, like the Java perspective, or in debug? </blockquote>
 
I'm using Oracle Java 32 bit (on a 32 bit system), so there should be no problem. 
 
Using an other perspective doesn't change anything. 
 
 
It is also annoying that setting the visibility-checkbox takes several seconds if you toggle it on a row. However, if you toggle it on a data-item for example you only have to wait less than a second. 
 
Maybe the report is to large. I've attached one of my reports, so that you can test it yourself.

johnw

Nope, works just fine on my machine. Not sure what the deal is...