I have a ‘quite’ complicated report that I’ve built in web intellingence xi, it takes ages for BO to calculate the results of each individual report which is v annoying. I’m fully aware that if what I’d done wasn’t so complex it’d be quicker & if I’d reduce the amount of information returned again it’d be quicker.
My question is when webi hangs like this and takes ages to do the requested action, is it my machine that is struggling or is it the server BO sits on?
Thanks - but as mentioned, the FAQ’s nothing I’m not already aware of. I’ve speeded up my query & variables as much as possible already to still retain accurate results. What I’d like to understand is where the processing of preparing the report data on screen is done because I seem to have hit a issue on that front now that I need to address.
From report performance tuning perspective, I would suggest following:
Take the report query as is.
Run it with sqlplus if its oracle or Enterprise manager for SQL Server
Get the query plan.
Check out the table statistics are upto date if not schedule a job to collect the table stats.
Check the query plan whether its using the existing indexes properly or if there is any tablescans against large tables.
Create necessary indexes on those large table if any tablescans.
Rerun the query and get the timings
Findout how many concurrent sessions in the database back-end side …if its too many, you may expect slowness depends on server load.
Repeat the tables/indexes tuneup until you get satisfied query performance.
Engage DBA to check out from Server configuration / memory allocation perpective also.
Engage Windows admin to check out # CPU’s, memory usage on the BOE Server.
If there are many concurrent BOE users who are running many reports …then need to perform capacity planning/ analysis.
I don’t think Steve has a problem with the query performance from what he’s saying. He has concerns about how his setup of WebI is performing once the data has been returned.
Specifically, he wants to know whether the client or server does the data munching and where the bottleneck is occurring in the processing of the data into the report display.
Steve,
How many rows are you bringing back, how many variables, etc.?
Just thought people would want to know to say whether the volumes that you are dealing with are excessive, indicating a general issue with WebI or a specific issue in your environment.
Yes … As a DBA, Universe designer and Report Developer, when I encounter this situation of performance issue on the report side,
I will try process the data as much as possible in the backend instead of doing the calculations in front end (WebI) so we can have all the load on the backend and use the UNIX or Windows database engine power.
(BOB member since 2009-11-02)
(BOB member since 2008-05-12)