This is part one of my OBIEE Tuning guide. In this post we will look at some of the parameters that should be set at NQSConfig.ini in order to achieve maximum performance First things first to run a valid test I ran the same report each time, after I had applied changes rebooted all database and OBIEE services to find time of completion I used the manage sessions section on the Analytics Console (Administration > Manage Sessions). With regards to what is a good and bad result if its not 10 seconds or more faster then I would say the change hasn’t had an effect on performance.
Note that all SQL should be tuned and it is said that OBIEE should be able to return a report within 1-10 seconds. My instance is not at this stage but you can still see a clear performance increase.
With my performance testing cache has been turned off as this will give invalid results, when performace tweaking caching should only be turned in the final stage.
Below changes were made to the NQSConfig.ini
MAX_SESSION_LIMIT = 5000 MAX_REQUEST_PER_SESSION_LIMIT = 5000 SERVER_THREAD_RANGE = 40-260 DB_GATEWAY_THREAD_RANGE = 40-520 INIT_BLOCK_CACHE_ENTRIES = 5000 # default is 20
The settings were saved, database and all BI services restarted.
The Report I was running contained 4 dashboards they will be listed as 1-4 below.
Original Report Timings Changes to NQSConfig.ini Timings
1. 2m10s 1m54s
2. 3m5s 2m46s
3. 5m16s 5m13s
4. 2m41s 2m34s
As you can see from the above there have been slight improvments in the report but one dashboard still runs in pretty much the same time.
My next post will be on changes made to instanceconfig.xml then finally the changes I made to the database.