Professional Documents
Culture Documents
Copyright
Copyright © 2008 Cognos ULC (formerly Cognos Incorporated). Cognos ULC
is an IBM Company. While every attempt has been made to ensure that the
information in this document is accurate and complete, some typographical
errors or technical inaccuracies may exist. Cognos does not accept
responsibility for any kind of loss resulting from the use of information
contained in this document. This document shows the publication date. The
information contained in this document is subject to change without notice.
Any improvements or changes to the information contained in this document
will be documented in subsequent editions. This document contains
proprietary information of Cognos. All rights are reserved. No part of this
document may be copied, photocopied, reproduced, stored in a retrieval
system, transmitted in any form or by any means, or translated into another
language without the prior written consent of Cognos. Cognos and the
Cognos logo are trademarks of Cognos ULC (formerly Cognos Incorporated)
in the United States and/or other countries. IBM and the IBM logo are
trademarks of International Business Machines Corporation in the United
States, or other countries, or both. All other names are trademarks or
registered trademarks of their respective companies. Information about
Cognos products can be found at www.cognos.com
This document is maintained by the Best Practices, Product and Technology
team. You can send comments, suggestions, and additions to
cscogpp@ca.ibm.com .
Contents
1. IBM COGNOS 8 PERFORMANCE TUNING CHEAT SHEET ............................... 4
IBM Cognos 8 Processing Capacity 1.0 For each server: This setting dictates the
Dispatcher number of BI requests that will
Appropriate value be handled by a particular a
is a function of server in the IBM Cognos 8
the number of topology.
CPUs, CPU clock
rate, memory, etc By default, requests will be
in relation to distributed so that each server
other servers in is expected to handle an
the topology. equivalent number of requests.
Must be considered in
combination with Batch Report
service settings. Overlap in
interactive and scheduled
activity may warrant a lowering
of this threshold to
accommodate both processing
activities.
Number of high affinity 1 For each BIBus This setting indicates the
connections for the process: 1 number of threads available
Interactive report service per interactive report server
(BIBus process) to handle high
affinity requests.
Queue timeout limit for 240 300 seconds This setting is used to
the report service seconds determine the length of time in
(seconds) seconds in which a request will
be queued in a ReportNet
dispatcher before being
terminated. If the queue
timeout limit is exceeded, an
error will be returned indicating
that a process “… was not
available within the configured
time limit”
Must be considered in
conjunction with Report service
settings. Overlap in interactive
and scheduled activity may
warrant a lowering of this
threshold to accommodate
both processing activities.
The number of high 1 For each BIBus This setting is not applicable to
affinity connections for process: 1 (just scheduled activity processing.
the batch report service leave the default) Current scheduling functionality
does not possess any high
affinity requests
The number of low affinity 2 For each BIBus This setting indicates the
connections for the batch process: 2 number of threads available
report service per batch report server (BIBus
process) to handle low affinity
requests.