Generation Performance

rbuser

I am evaluating RB 9.03 to see if I want to use it within my application. I
need to make a decision this week as reporting is the last part to go into
this appliation before it's released. So far I've been impressed with the
relative ease that I can define a report. The only thing that troubles me
is the slow performance I'm seeing within a runtime executable.

I've designed a two-column report that prints up to four records per page.
The detail area consists of a graphic box and several lines of text that
come out of a database. I've tried using both an extracted, delimited text
file and a live ADOQuery as data sources and both take about 20 seconds to
render at runtime. (using very small datasets of 2 and 4 records
respectively).

Is this generate speed normal for ReportBuilder, or is this something built
into the Demo version to encourage me to purchase the registered version?
Are there ways to optimize the initial generation process so the user
doesn't see such a big delay? I've used other report tools which seem
faster than this.

Thanks,

Darren

nicocizik

Hi Darren,

Thanks for trying ReportBuilder.

I have not seen this behavior before for RB 9.03. How large are the images
you are trying to load? The Demo version should work with the same
performance as the registered version. As a test, try running one of the
demo reports located in the \RBuilder\Demos\1. Reports\... directory
(specifically one using a TextPipeline) and see if the performance time is
the same. Also, which database are you using? If you create a simple
report connected perhaps to the Northwind database (SQL Server or Access),
do you still get the same performance times?

--
Regards,

Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com

rbuser

Darren,


We generate a lot of reports and there are only really two things which
effect the speed -- the length to generate the database query and the
number of pages. Things like using a TTable against a SQL database,
not indexing fields, etc.

You might look at some of the report properties and ensure that it is set to
single-pass (so it doesn't need to generate the entire report to start
displaying
pages) and that the cache pages option is off.

I haven't run into many reports which take anything like 20 seconds,
baring a 200 page report or problem with the database.

Thanks,

Brett