Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BO performance

Status
Not open for further replies.

jennyfher

MIS
Oct 8, 2003
23
US
Hola: We are having performance issue with a report, we have worked in the query perfomance and we have been getting good results but when we run this in BO,well it is not good. We can see in the DB logs that the query is performing really good so it is the time BO is taking to fetch and display the records taht is causing the performance issue. Do you have any ideas on how can this be improve. Thanks :)
 
You should distinguish between the fetching phase and the formatting stage of the data to be displayed.

The data manager will show you - approx. - how long it took to fetch the data. This should be roughly the same as the time it takes with a DBA query tool.

The formatting of the report depends on many variables. CPU-speed of the client has a big impact. In the past switching from pentium to pentium II machines improved formatting performance 5-fold (at my comp)

Other variables: number of objects (tables, charts ed), complicated filters, applied ranks.

Slow fetch performance could be related to network conditions

Ties Blom
Information analyst
 
What I am seeing is this, I run my report after 1 minute the rows status bar start counting, at the same moment in the DB the query has finished running; then it take about 10 minutes (the rows stratus bar still counting) to the data to appear (the formatting is done quickly since we dont have a lot of formatting). So the problem is when fetching the data. I know there is a parameter for this data fetch array (number of rows per second) but are there other parameters that could help, does anybody know what is the optimum number for this array parameter? Thanks
 
How much data are you talking about?

What is the database? What is the middleware and version?

This is important for several reasons. For example, if your database is SQL Server and you're using ODBC, the distance from the box is important. ODBC doesn't work well over long distances. OLEDB is much faster.

Steve Krandel
VERITAS Software
 
fetch array is default 50 I think. A larger array fetch size should minimize overhead, but I do not expect very great impact on setting it to other values.
You do not mention which RDBMS you are working with and the number of records that have to be fetched. Perhaps we can come up with some ideas if we know the SQL statement and other details...

Ties Blom
Information analyst
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top