Bug 365398 - UI performance is really bad when there are lots of columns in a table
Summary: UI performance is really bad when there are lots of columns in a table
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 3.7.1   Edit
Hardware: PC Windows Vista
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Birt-ReportDesigner CLA
QA Contact: Sissi Zhu CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-02 04:11 EST by Yaytay CLA
Modified: 2012-01-03 07:55 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yaytay CLA 2011-12-02 04:11:28 EST
Build Identifier: 20110916-0149

Trying to use BIRT with a large table is very slow, made worse by the fact that some operations require too many interactions.
The first problem is that simply creating a data set with 500 columns causes the whole UI to slow down unacceptably.
The second is that, for example, changing the data type of 500 columns requires individually opening up a data entry box for each one - it would be much simpler if there was a drag/drop/spreadsheety way to change multiple column definitions in one go.

These issues are independent of the performance problems BIRT has in dealing with that much data, they are UI specific problems.

Reproducible: Always

Steps to Reproduce:
1. Create a CSV with 500 integer columns and 10000 rows.
   Do not make the second row a type specifier.
2. Try to produce a report using that data (be sure that the data is imported as integers).