Hogging the cpu

[chogben]

Why does BO hog the processor when running a query? Shouldn't the server be doing most of the work?
Is there a way to stop this?

The 'spike' goes up to 100% the moment the query is submitted and stays there until the query returns. I would have expected a short spike when sending the query and a medium size spike when the data is returned.

 

[blom0344]

Hello Chogben,

You are describing a-typical BO-behaviour. In all the years I worked on BO reports, it was possible to let a report run in the background, while performing other duties. Performance check on windows 2000 shows no spike at all when submitting a query, and a short spike when data is returned from the server ( in my case about 80% on pentium III , 1gHz)
When formatting and calculating CPU is 100% on BO, but then query has already ended.
This behaviour is the same for Oracle, DB2 UDB 7.1 and AS400 type databases.
You are not mentioning the RDMS you are working on, but It would be interesting to check the activity on the server for a query. The only exception I can think of is when you are refreshing a report with multiple types of data-providers, for instance combining RDMS data with flatfiles or spreadsheets from a local source.

 

[Bilky]

I work on AS/400 and I find that when a query is submitted it hogs the CPU of the PC until finished. I think it is due to the processing of the query being syncrhonous and not asynchronous which allows it to be notified when the result is ready.

 

[JeffersonH]

you can make your .key asynchronous...which is best with webi tmp.Worldwide
Business Objects 5i
Systems Integrator
Pfizer Global Research and Development

 

[skrandel]

Be very careful using asynchronous. I, too prefer asyncrhonous, but BO doesn't support it for ZABO. Steve Krandel
BASE Consulting Group

http://www.baseconsulting.com