Bug 384849 - Report SQl Data set is quick but designer is way too slow
Summary: Report SQl Data set is quick but designer is way too slow
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 3.7.1   Edit
Hardware: Other other
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Birt-ReportDesigner CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-11 13:04 EDT by Eclipse Beginner CLA
Modified: 2012-07-12 04:45 EDT (History)
1 user (show)

See Also:


Attachments
Rpt Design (1.72 MB, application/octet-stream)
2012-07-11 13:10 EDT, Eclipse Beginner CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eclipse Beginner CLA 2012-07-11 13:04:14 EDT
Build Identifier: birt-runtime-3_7_1

Hi, 

I am using BIRT engine to generate report from my design file. I have a couple of data sets but majorly only one is working. when i run the sql in that dataset i see it get completed in less than a second, but when i run report from a unix machine it is taking 25 minutes for just 50K records.
Same is happening for other report designs as well, are there any tips that I can use to improve performance of designs?

there is another one, when i try to generate the pdf using it, it just cuts the data off, i mean ... i expect lots of rows on that page but it just cuts it... on the top of it I am not able to restrict the number of records on the pdf page

I dont know how to attach the design file with bug.



Reproducible: Always

Steps to Reproduce:
1. you need to have birt engine on unix
2. need to have same data
3.run report engine
Comment 1 Eclipse Beginner CLA 2012-07-11 13:10:10 EDT
Created attachment 218585 [details]
Rpt Design
Comment 2 Xiaoying Gu CLA 2012-07-12 04:45:31 EDT
(In reply to comment #1)
> Created attachment 218585 [details]
> Rpt Design

The report you attached is quite complicated and was using a outside database. I can not reproduce the issue without access to db.

Could you try to create a simple report to reproduce this issue? For example, a simple table that contains 50k records?

And could you please attach the output pdf file?