OBIEE 11g performance Settings
Oracle BI Presentation Services Component Tuning Guide
To achieve better performance with Presentation Services (OBIPS) component, the following parameters can be tuned instanceconfig.xml file
Waiting time for results |
Controls how long the server waits for results after the initial request before returning the Searching page to the browser. It may be useful to set this value higher (such as 10 seconds) to avoid page refreshes if the majority of queries are not returning in 1 second. If running performance tests some test implementations behave properly only if this setting is set very high (such as 1000 seconds).
<Cursors>
<NewCursorWaitSeconds>10</NewCursorWaitSeconds>
</Cursors>
</ServerInstance>
Catalog related tunable parameters |
There are several OBIPS web catalog related parameters available like Soft limit on when a lock is warned of being stale, Hard limit on when a lock is removed as stale, How many characters to use to hash usernames into sub directories etc
<ServerInstance> <Catalog> <LockStaleSecsSoft>14400</LockStaleSecsSoft> <LockStaleSecsHard>14400</LockStaleSecsHard> <HashUserHomeDirectories>3</HashUserHomeDirectories> </Catalog> <BIEEHomeLists> <Enabled>false</Enabled> <CatalogSynhronizationFrequencyMinutes>30</CatalogSynhronizationFrequencyMinutes> </BIEEHomeLists> </ServerInstance> |
Caching related tunable parameters |
There are several OBIPS cache related parameters for number of cache entries, expiry time, and algorithm to clean up the cache etc.
<Cache>
<CatalogXml> <!-- Remove from the cache everything older than N minutes --> <MaxAgeMinutes>240</MaxAgeMinutes>
<MaxLastAccessedSeconds>14400</MaxLastAccessedSeconds>
</CatalogXml>
<Query>
<MaxEntries>10000</MaxEntries> <!-- AbsoluteMaxEntries is the enforced maximum number of entries. When this maximum is reached -->
<!-- subsequent queries will fail until the maximum is no longer exceeded. --> <AbsoluteMaxEntries>20000</AbsoluteMaxEntries> <!-- CruiseEntries is amount of entries the OracleBI Presentation server tries to maintain in its cache. --> <CruiseEntries>3000</CruiseEntries> <!-- Forces the cache to attempt to remove an old entry when MaxEntries is exceeded. --> <ForceLRU>true</ForceLRU>
</Query>
<Accounts> <!-- Cleanup this cache every N minutes. --> <CleanupFrequencyMinutes>14400</CleanupFrequencyMinutes>
</Accounts>
<AccountIndex> <!-- Cleanup this cache every N minutes. --> <CleanupFrequencyMinutes>14400</CleanupFrequencyMinutes>
Charting thread related tunable parameters |
Number of charting threads and maximum number of jobs allowed in the queue can be tuned for performance when the dashboards have several charts:
<ThreadPoolDefaults>
<ChartThreadPool>
<MaxQueue>2048</MaxQueue>
<MaxThreads>32</MaxThreads>
</ChartThreadPool>
</ThreadPoolDefaults>
</ServerInstance>
1 comments:
Write commentsOut of the several data warehouse service provider , I found your company to be the topmost, which helped me optimizing the system through the capacity analysis as well as the effective performance.
ReplyNote: only a member of this blog may post a comment.