You are on page 1of 13

Guideline

TM1 Server Administration
Product(s): TM1 v.9.1 and prior Area of Interest: Performance

com This document is maintained by the Best Practices. suggestions. Cognos ULC is an IBM Company. or translated into another language without the prior written consent of Cognos. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained in this document.TM1 Server Administration 2 Copyright Copyright © 2008 Cognos ULC (formerly Cognos Incorporated).com .cognos. IBM and the IBM logo are trademarks of International Business Machines Corporation in the United States. While every attempt has been made to ensure that the information in this document is accurate and complete. You can send comments. reproduced. stored in a retrieval system. IBM Cognos Proprietary Information . or both. All rights are reserved. Information about Cognos products can be found at www. some typographical errors or technical inaccuracies may exist. No part of this document may be copied. All other names are trademarks or registered trademarks of their respective companies. or other countries. photocopied. and additions to cscogpp@ca.ibm. The information contained in this document is subject to change without notice. transmitted in any form or by any means. Cognos and the Cognos logo are trademarks of Cognos ULC (formerly Cognos Incorporated) in the United States and/or other countries. This document contains proprietary information of Cognos. Any improvements or changes to the information contained in this document will be documented in subsequent editions. Product and Technology team. This document shows the publication date.

..........................................2................................................................................................................................................................ 12 CREATING THE BATCH FILES ................ 11 SERVER LEVEL MEMORY STATISTICS ......................................................................... 12 STARTING AND STOPPING THE TM1 SERVICE USING NETSVC.................. 12 PREREQUISITE...........................1 1..........4 EXCLUSIONS AND EXCEPTIONS ......................................................................................................2.........2...............................................................9 TM1 SERVER CAPACITY PLANNING GUIDELINES ............................................. 12 Creating stop_tm1.........4 USING SIZING METRICS TO DETERMINE AN OPTIMUM TM1 CONFIGURATION .........................................................................3 6 6.............. 10 SAVING THE DATABASE .................. 4 PURPOSE ................................ 4 USING THE TM1 SIZING GRID TO DETERMINE AN OPTIMUM TM1 CONFIGURATION.....................................................1 5..............................1 2.............2...3 2 2.........................2....2 6................. 11 MEMORY CONSUMPTION FOR OTHER OBJECTS .......1 4...4 3 4 4.............bat....... 12 SCHEDULING BATCH FILE EXECUTION IN TASK SCHEDULER ........................3 INTRODUCTION .............. 10 RECYCLING THE TM1 SERVER .............................4 APPLICABILITY ........................................................1 2.......3 2....................................2 1.................................6 Estimating Model Size .................................................. 11 CUBE MEMORY STATISTICS ...........................................................................................................2 5......................2 2........ 10 MONITORING MEMORY USAGE ......................................X ............1 6..................................................9 General Server Hard Drive Guidelines..1 6.2 5 5.............................................4 SERVER SIZING GUIDELINES – TM1 9................................................ 12 Creating start_tm1........................................ 10 TM1 SERVER UPTIME/RESTARTING GUIDELINES ......................2 2..bat ............................................................................................2...7 Defining Topology ...................................2 6..................6 Defining Users............................... 13 IBM Cognos Proprietary Information ...............................................................................TM1 Server Administration 3 Contents 1 1...............

you can review known TM1 and system metrics to more accurately determine an optimum configuration. and sizing of the TM1 server hardware.3 2 Server Sizing Guidelines – TM1 9. 1.2 1. Alternatively.1 Using the TM1 Sizing Grid to Determine an Optimum TM1 Configuration Consult the TM1 Sizing Grid grid below to quickly identify common configurations for TM1.1 and prior releases Exclusions and Exceptions No exclusions have been identified at this time. Applicability IBM Cognos TM1 version 9.x The purpose of this section is to provide a sizing guide for TM1 installations. Due to the inherent differences between one TM1 installation and the next. IBM Cognos Proprietary Information . 2.1 Purpose This collection of articles focuses on the administration.TM1 Server Administration 4 1 Introduction 1. You can use the TM1 Sizing Grid to determine a typical minimum configuration solution. planning. this guide is really just that – a guide.

your implementation most closely resembles the Heavy Reporting user community. To use the grid. IBM Cognos Proprietary Information . often Web-based.TM1 Server Administration 5 Admin = Admin/Power User. your implementation most closely resembles the Model < 3GB model size. If your TM1 model is smaller than 3 GB. locate the recommended configuration at the intersection of the user community and model size that most closely correspond to your implementation. You will find your recommended configuration at the intersection of the Heavy Reporting user community and the Model < 3GB model size. For example. as shown below. RO=Read Only or Reporting user. but larger than 1 GB. and the vast majority of those users are readonly users. RW = Read/Write user. if you have roughly 100 users.

update models and objects. The basic process is as follows: Each step in the process is described in the sections that follow.2.2.2.2.2 Read/Write users (RW) Read/Write users update data in the model on a regular basis.1. feeders.1. Define the planned number of concurrent users based on the definitions below. Each concurrent user will require 20 MB RAM on the TM1 server when connected so knowing the total concurrent user community is important. Calculate concurrency as 33% of total Read/Write users (or 3:1). Calculate concurrency as 10% of total Read Only users (or 10:1) 2. User Type Total Number 2 10 Concurrency Factor 100% or 1:1 33% or 3:1 Concurrent Users 2 4 (rounded up) Power User Read/Write User IBM Cognos Proprietary Information . 2. They also create/view complex reports and views. hierarchies and rule calculations.2. Calculate concurrency as 100% of total Power Users (or 1:1).2 Using Sizing Metrics to Determine an Optimum TM1 Configuration The size of a TM1 model can be estimated from known data (a POC using a subset of real data.4 Estimating RAM Requirements Based on User Types The following table illustrates how defining users helps you determine the amount of RAM required for your TM1 implementation. and create complex reports and views. and a twin CPU Reporting Server with 8GB RAM for Read-Only users (95).If you require a TM1 Web server.TM1 Server Administration The recommended configuration suggests that you should use a twin CPU 64-bit TM1 server with 6GB RAM for the Read/Write users (5). known dimensionality.3 Read Only/Reporting users (RO) Read Only users do not generally enter any data. They load data. it should have a single processor and 2 GB RAM to support 100 users.1. 6 2.1 Power Users (Admin) Power users are logged into TM1 for the majority of the day.1. 2. They use pre-defined reports in Excel or TM1 Web and require fast access to data.1 Defining Users Sizing recommendations are based on the assumption of peak concurrent user counts as defined below. 2. or known data to be loaded) but there will always be unknown factors such as the space required for view storage. 2.

provision a minimum of 2GB of RAM. virtual memory paging severely degrades server performance). Will the Read-Only/Reporting users require fast access to static reports while data is still being uploaded/changed? If so.1. ODBO).TM1 Server Administration 7 Read-Only User 100 10% or 10:1 10 Total Concurrent Users = 16 RAM Required= 16 * 20MB =320MB 2. both the HP-UX and Solaris platforms are supported. • • • Will the majority of users be primarily TM1 Web users? If so.1. and ease of maintenance and administration. If there is a requirement for large amounts of data (over 3GB).2. given its high degree of compatibility with Win32. a Reporting Server is recommended. IBM preference is Windows64 over UNIX.2. support for all Microsoft interface technologies (ODBC.2 Estimating Model Size An accurate estimate of TM1 model size can only be calculated from a real-world model built on actual data (such as a POC model using a proportion of the actual model’s data). a TM1 server can handle 25 Read/Write users per CPU and up to 100 Read-Only users per CPU. consider a Reporting Server topology.2.7 Provisioning RAM in the Absence of Application Metrics In the absence of any information about the application. If a real-world model is not available then use either an estimate based on data to be loaded into the model or choose one of the reference systems given in the Sizing Grid above. it is good practice to fully populate Win32 servers with 4GB. Will the Read-Only users request reports simultaneously. The answers to these questions should be used to alter the server specification as necessary. adding CPUs to a TM1 server will benefit Readers more than it will benefit TurboIntegrator users or Writers (as these two will lock the whole server for periods). IBM Cognos Proprietary Information . so more CPUs will allow more concurrent Read requests. As TM1 is sensitive to the server reaching its physical RAM limit (e. consider a Reporting Server and/or multiple processors. In situations where the Writers might lock the server to the detriment of the Readers.2.g. 2. and makes the hardware platform future-proof until a migration to 64-bit is necessitated. For more information. Each Read request will occupy 100% of a CPU.5 Further User Considerations There are a number of questions to consider after defining a user community based on the definitions above. 2. see the Principles of TM1 Multi-Process and Multi-Threaded Usage chapter in Optimizing TM1 Performance. a 64-bit solution is mandatory.1.6 Multiple CPU Guidelines as Related to Number of Users As a rule of thumb. 2. and is reporting performance important? If so. consider a separate TM1 Web Server. In general. In a green-field situation. as it typically only adds a small percentage to the overall purchase price. However.

• • Data Each data item loaded into TM1 will occupy.2.1 The Effects on RAM of 64-bit Technology 64-bit technology expands the RAM available in Windows and UNIX to levels now limited only by the hardware available.g. IBM Cognos Proprietary Information . 3D gaming extensions). As noted in the 64-bit Considerations chapter of Optimizing TM1 Performance. Operating System TM1 Version Max RAM in OS 4 GB Max RAM for TM1 3 GB Windows 2000 or 2003 32-bit Windows 2003 64-bit TM1 32-bit TM1 32-bit TM1 9 64-bit Unlimited* Unlimited* Unlimited* 4 GB Unlimited* Unlimited* UNIX (Sun. Treat these as two processors for sizing purposes. Each calculated member will proportionally increase the data.TM1 Server Administration 8 Estimation using known data volumes is a fairly simple process and is useful for getting a feel for the order of magnitude of the data. 14 bytes of RAM. Also available are ‘dual core’ processors that provide Symmetrical Multi-Processing (SMP) capability in a single chip package (Intel Core Duo. They support both Windows 32-bit and Windows 64-bit.2. AMD 64).000. etc). on average. EM64T-capable processors (64-bit .000.1GB Users Total Model Size 2.2 General CPU Guidelines TM1 performs better on Xeon chips than Pentium 4s. as Xeons have fewer consumer-oriented features (e.000 * 14 bytes = 160MB Model for 5 years of data = 801MB Calculations Calculated Forecast is one year of extra calculations = 160MB 10 Users =10 * 12 MB = 120MB 801+160+120 = 1. HP) TM1 9 64-bit *limited only by hardware 2. 1.2. a 64-bit TM1 installation on a 64-bit operating system requires between 30% and 100% more RAM due to the larger memory pointers required.2. allow for RAM growth beyond the 32-bit 3 GB limit to theoretically limitless quantities.Intel Xeon 64. It is recommended now to buy EM64T processors if possible for future growth potential.000 rows with 12 data items in each row= 12.

2. IBM Cognos Proprietary Information . however. After SMP processor count. 2. The general rule of thumb for sizing a TM1 Web server is up to 250 concurrent users per CPU. There is a case. 2. TM1 Web should always run on a separate server if possible. to sometimes introduce a Reporting Server into the topology to increase the performance of reporting users.TM1 Server Administration 9 For all but the simplest applications the host machine should be SMP capable. The Reporting Server is used to service all the reporting users so that their requests to not affect. 2.2. as detailed in the following table.2. Procure the fastest processor speed. but a 10-user system with sufficient free resources on the server could get away with running both the TM1 and Web servers on a single server.3 TM1 Web Servers In general. As a rule of thumb.3.3. Read/Write activity on the main server. and cannot be upgraded at a later date. a Reporting Server is recommended when the Read-Only community outweighs the Read/Write community by a factor of five and there is constant Read/Write activity on the main server. Number of TM1 Web Users Number of Processors Recommended on TM1 Web Server 1 Processor 2 Processors 4 Processors 8 Processors 1-100 101-500 501-1000 1001-2000 It is also possible to use multiple TM1 Web servers if you have a significant number of TM1 Web users.2. 2. in most cases the TM1 server stands alone with perhaps a TM1 Web server providing Web access to the applications.2.3 Defining Topology TM1 Topology is fairly simple.2. these three factors have the biggest impact on TM1 performance.2 TM1 Web Servers A separate TM1 Web server is always recommended. and are not affected by. largest processor cache size and fastest Front Side Bus speed your budget will allow.1 Reporting Servers A Reporting Server is generally a Read-Only replicated and synchronized TM1 server that is refreshed at a set frequency from the ‘live’ server (once per day is typical).4 General Server Hard Drive Guidelines The host machine’s disk subsystem can be almost ignored – procure the smallest local disk available (anything over 72 GB should be sufficient).3. This is a binary procurement decision – a given server is or is not SMP-capable.

The TM1 database can be saved automatically by: IBM Cognos Proprietary Information . 4.TM1 Server Administration 10 Unfortunately. most server-class machines come with fault-tolerant disk subsystem (e.g. allot one CPU per 100 users (any mode) Assume a requirement of 16 bytes per non-null cell to estimate total server RAM requirements Keep 25% of physical RAM in reserve (e. Similarly. hotpluggable SATA RAID). allot one CPU per 25 read/write users or 100 read-only users For TM1 Web.25 GB of usable RAM) TM1 server operating in 32-bit mode on X64 can expand to 4GB of usable RAM PAE/AWE does not extend the usable RAM of a TM1 server instance (but. this prevents log files from getting unmanageably long and reduces the recovery time in case of hardware or software failure.2 Saving the Database A database save writes all changed cubes to disk storage and restarts the transaction log.g. 3 GB of physical RAM yields 2. Alternatively. Two exceptions to this rule: • • If you plan on staging/storing very large ASCII files for ETL purposes on the local disk of the TM1 Server host machine.1 Recycling the TM1 Server Even though TM1’s memory management is very stable and some users run the TM1 server uninterruptedly for weeks or months. which is expensive yet all but wasted on TM1’s RAM-resident database. Such periodic recycling ensures a more compact and efficient storage scheme. the TM1 server can be stopped and restarted using an external scheduler.cfg parameter Downtime. as BLOBs are stored directly on disk. the server may be stopped automatically by setting the Tm1s. you will require a sufficient amount of disk storage. 4. The TM1 database should be saved nightly. 3 TM1 Server Capacity Planning Guidelines Use the following guidelines to plan a TM1 server implementation: • • • • • • • For the TM1 Server. mutiple instances can run on a single host machine) Allot 20 MB of server RAM for each active client session 4 TM1 Server Uptime/Restarting Guidelines This article describes recommended practices for recycling the TM1 server and saving the TM1 database. plan accordingly. if you plan on storing many large Binary Large Objects (BLOBs ) in TM1 Applications. IBM recommends recycling the server on a weekly basis or after loading a large amount of new data. If the TM1 server is running as an application.

When processing data through TurboIntegrator. when it frees memory. but puts it in a garbage list which it then reuses as needed. 5. IBM recommends using the TM1 Performance Monitor.TM1 Server Administration • Setting the Tm1s. a database save should be performed immediately after the data load is complete. the operating system performance monitor will not give you an accurate measure of the current consumption of memory of the TM1 server. 5. TM1 allocates memory as it needs it from the operating system. this can be accomplished by calling the SaveDataAll function in the Epilog of the TurboIntegrator process. 5 Monitoring Memory Usage There are three sources of information on memory consumption by a TM1 server: • • • The operating system performance monitor or task manager.1 Server Level Memory Statistics The TM1 Performance Monitor keeps the following memory statistics for the server as a whole: • Memory Used • Memory In Garbage The sum of the two quantities should correspond to the memory consumption reported by the operating system performance monitor. The TM1 client. However. it does not return it to the operating system. Instead. as described in the TM1 Administrator's Guide. The TM1 Performance Monitor. Accordingly.2 Cube Memory Statistics The TM1 Performance Monitor keeps the following memory-related statistics for each cube in the server: • Total Memory Used • Memory Used for Input Data • Memory Used for Feeders • Memory Used for Calculations • Number of Fed Cells • Number of Populated Numeric Cells • Number of Populated String Cells • Number of Stored Calculated Cells • Number of Stored Views • Memory Used for Views IBM Cognos Proprietary Information .cfg parameter SaveTime • Scheduling a TurboIntegrator process to execute the SaveDataAll function 11 If you process data through TurboIntegrator or processing worksheets with cube logging turned off.

SData" on a computer named CorpData. Enter the following line in the text file: netsvc /start \\computer_name "service_name" IBM Cognos Proprietary Information .bat The start_tm1.bat The stop_tm1. 6. 6. 1.2. 1. 2.1 Prerequisite The netsvc command is part of the Windows 200 Resource Kit.2 Creating the Batch Files You must create two batch files.TM1 Server Administration Full details of all performance monitoring cubes and dimensions can be found in the TM1 Administrator's Guide. 3. if your TM1 server is running as a service named "TM1 Server . allowing you to automatically recycle your TM1 server at regular intervals as recommended by IBM.bat file contains a single command to stop the TM1 server. 6 Starting and Stopping the TM1 Service Using netsvc The following procedure describes how to use the netsvc command in batch files to start and stop a TM1 server installed as a service on Windows 2000. Before you create these files.bat file contains a single command to start the TM1 server.1 Creating stop_tm1. which must be installed before you can successfully complete the procedure described below. Start Notepad or your preferred text editor.SData".2. (The netsvc command is not available on Windows XP.3 Memory Consumption for Other Objects The memory consumed by dimensions.) The batch files can be scheduled for execution through the Windows Task Scheduler. The memory used to store the values associated with the view will appear in the “Memory Used for Views” item produced by the performance monitor associated with the cube to which the view belongs. Save the text file as stop_tm1. 12 5. Enter the following line in the text file: netsvc /stop \\computer_name "service_name" For example. 6. Start Notepad or your preferred text editor. you would enter the line netsvc /stop \\CorpData "TM1 Server .bat. subsets and other objects appears in the properties window of the TM1 Server Explorer.2 Creating start_tm1. make sure you know the name of the computer on which the TM1 server is installed (computer_name) and the name of the service assigned to the TM1 server (service_name). Note that the memory displayed for views is only the memory required to store the definition of the view. 6. one to stop the TM1 server and one to start the TM1 server. 2.

allow sufficient time for the TM1 server to completely shut down. Double-click Add Scheduled Task. You should set up your schedule so that tm1_stop. if you schedule tm1_stop.bat is executed first. For example. Follow the prompts in the Scheduled Task Wizard. Save the text file as start_tm1. IBM Cognos Proprietary Information .bat and tm1_start.bat to run at 11:10 PM. 6. 1.bat to run at 11:00 PM. From the Windows taskbar. Control Panel Scheduled Tasks. if your TM1 server is running as a service named "TM1 Server . When creating the schedule.3 Scheduling Batch File Execution in Task Scheduler To schedule a time to stop and start the TM1 server.SData". you would enter the line netsvc /start \\CorpData "TM1 Server .bat.TM1 Server Administration 13 For example. click Start 2. 3.bat. schedule tm1_start. complete the following steps for both tm1_stop.bat. followed by tm1_start.SData" on a computer named CorpData. 3.