TCR - Cognos Peformance Tuning

8/11/2019 TCR - Cognos Peformance Tuning

1/11

Tivoli Common Reporting

Cognos Tuning Parameters

Kalarith Sisowath

IT Architect - Lab ServicesBusiness Analytics

Tel: +33-1-5875-5016E-mail: [email protected]


2/11

Document Control

Revision Date Author Summary of Changes

1 02/04/14 Kalarith Sisowath First Version

Reviewers

Name Title

Andrew Bruckshaw IT Specialist, Cloud and Smarter Infrastructure


3/11

Introduction

This document outlines the changes that should made to the default Cognos parameters thathave an impact on performance. The default settings are not suitable for a productionenvironment. In this example case each server is to host the Gateway, Application Tier andContent Manager components and have been sized to support approximately 120 concurrent

users running interactive and batch type queries of 'intermediate' complexity. The hardwareplatform is assumed to be IBM System P with Power7 processors running AIX. Each server isallocated 23 CPU cores and 55 GB RAM.

Thanks to Kalarith Sisowath, IT Architect - Lab Services, Business Analytics for providing theinformation.

Cognos Parameter Settings

The following section details the recommended Cognos parameter settings based on theabove assumptions for sizing.

Open IBM Cognos Configuration:

Change initial heap size to 1150 (this is for Cognos BI 8.4.27.78 32bit)

In folder /configuration, save and edit files :

CQEConfig.xml:


4/11

LocalCacheOutputSize 50SessionCacheSize 30VirtualMemoryDiagnostics 2

Add manually this entry :

BurstThreadPoolSize

50

In folder /tomcat4.1.7/conf, save and edit file :

server.xml :


5/11

redirectPort="9443"acceptCount="1000"debug="0"connectionTimeout="60000"disableUploadTimeout="true"maxHttpHeaderSize="32768"/>

In folder /webapps/p2pd/WEB-INF/, save and edit file:

p2pd_deploy_defaults.properties :

# Content Manager Connection Pool sizedispatcher.cm_poolsize=80# Size of the request cache of the report server (default = 10)wp_cache_size=80

In folder /webapps/p2pd/WEB-INF/, save and edit files:

batchreportservice.xml and reportservice.xml:

max_process 6

Go to the administration Cognos portal, then modify setting to increase number of process for theBatchReportService and the ReportService :


6/11

Advanced settings :Go to IBM Cognos Administration tab :

Then in Settings and Advanced settings > Edit


7/11


8/11


9/11

INT_MAX or 2147483647 (10 digits, take care!). CM temp files are cleanedautomatically after 15 minutes of non-use and at shutdown, so the size of CM tempfiles wont grow infinitely large.

CM.MAXPATHLOCK

When doing move/copy/paste operations on Portal folders, CM maintain a lock onsource folders for the duration of the move operationDefault: 1000, Changed to 100000Effect: increasing that value has an effect that no locks are maintain during theduration of fetching objects by blocks, thus allowing a very short locking time.

CM.DbConnectPoolIdleTime Minimum time in milliseconds that a connection stays idle in the Content Managerpool.Default: 300000 (5 minutes), Changed to 30000 ( 30 seconds)Effect: reducing to 30sec the duration of idle connection before cleaning them, afterthe 15mn of inactivity timeout has occurred.

CM.DbConnectPoolCleanUpPeriod

Time in milliseconds between invocations of a cleanup thread that closes idleconnections in the Content Manager pool that exceed the setting ofDbConnectPoolIdleTime.Default: 300000 (5 minutes), Changed to 30000 ( 30 seconds)Effect: each 30sec, the cleanup thread will be activated in order to delete the idleconnection, reducing to a maximum of 59sec the time a idle connection stays alivebefore deletion

RSVP.PROMPT.RECONCILIATION

COMPLETE or 0

All queries are sent at once. This is the slowest, most accurate form of reconciliation.This is the default setting.GROUPED or 1Queries are sent by priority group. This setting works best for reports that have manyunfiltered queries and few filtered queries. It provides medium speed and highreconciliation accuracy.CHUNKED GROUPED or 2Queries are sent by priority group with a maximum number per request. The queriesdo not span groups. This setting works best on reports that have many queries withsimilar filter expressions. It provides maximum speed and low reconciliation accuracy.CHUNKED or 3Queries are sent by priority group with a maximum number per request. The queriescan span groups.

RSVP.CONCURRENTQUERY.NUM

HELPERSPERPROCESS

Enables concurrent query execution and sets the maximum number of query

execution helpers for each report service or batch report service process.Each query execution helper results in an additional data source connection. Forexample, a report service has four processes with two high affinity connections andtwo low affinity connections.If the maximum number of query execution helpers is set to 0 (disabled), themaximum number of data source connections created by the report service is 16 (twolow affinity connections plus two high affinity connections plus zero query executionhelpers times four processes).If the maximum number of query execution helpers is set to 2, the maximum numberof data source connections created by the report service is 24 (two low affinityconnections plus two high affinity connections plus two query execution helpers timesfour processes).The calculated maximum number of data source connections applies to each reportservice or batch report service process.Default: 0 (concurrent query execution disabled)

RSVP.CONCURRENTQUERY.ENABLEDFORINTERACTIVEOUTPUT

Enables concurrent query execution when the report service is producing interactiveoutput.For interactive reports, if concurrent query execution is enabled, some queries maybe unnecessarily executed because the results are not used. For example, all thequeries for a multi-page report may execute with at least one query on each page, butthe user may view only the first page. If you do not want to use resources for resultsthat are not used in interactive reports, disable this parameter.Authored prompt pages are not interactive output and are not affected by this setting.Default: false (disabled)

RSVP.VPICACHE.ENABLED

optimize the management of the virtual memory by enabling a internal cache forobjects manipulated by the Report Server.


10/11

RSVP.VIRTUAL.MAPPINGMODE

optimize the mapping mode of the virtual memory allowed to the Report Server.

Peak period and non peak period:We can play with 2 periods to spread more processor to Report or Batch report service for a specific period.


11/11

Max processes and JVM memory variations depending on systemspecification

The information below indicates how the values for MaxProcessess and JVM heap sizeshould be set to make best use of different machine specifications.

Documents

TCR - Cognos Peformance Tuning