OBIEE Performance Tuning Tip – Turn off Query Logging
Though query logging has immeasurable development value, do not use this for regular production users as the runtime logging cost is extremely high. Every log item is flushed to the disk, which in turn hurts query response. Also, note that the query log files are not created on per user or query basis, there is only one query log per OBIEE server and it would have exclusive lock on the log file, which kills concurrent performance.
On the other hand, usage tracking has a very low runtime cost and is preferred to monitor the queries being used.
3 Comments »
Leave a Reply
About Me
I am Kumar Kambam, a BI and DW professional. I have been working with OBIEE (also known as Siebel Analytics yesteryears) and Informatica for a long time now. I am currently working with BI Consulting Group (BICG). This Blog is my attempt to share my knowledge with the world. I will write here as often as I can about whatever I come across in the BI and DW space. Also please visit Oracle BI Blog by BICG where my colleagues often contribute at.
The views expressed here by me are entirely mine and do not necessarily express the views of my Employer or Clients.
Hi
I am having one qustion
I have develope one report in OBIEE when i am runing it it takes more time at same time if i run the log sql in sqldeveloper it takes expected time
why this happens can you help me
Thnak
dhananjay
Comment by dhananjay | February 23, 2009
Hello Every one.
I have one question here. Could you help me out in sharing the issues and solutions you got during your work experience.
Comment by Praveen | June 15, 2009
Hi Kumar, is there a specific document for us to refer to on Performance Tuning for OBIEE?
Comment by LynxLee | July 6, 2009