How to estimate memory usage for the 64-bit TMTM services for Windows

This section describes how to estimate memory usage based on the previously recorded low resolution historic data from the TMTM database for the 64-bit services for Windows before installing Fix Pack D.

TMTM has a builtin function for automatically collecting OS process level high resolution historic data on TMTM services and generating low resolution historic data from the high resolution data. All historic data gets stored in the database. Using a "memory usage estimator" SQL script, as described in the procedure below, we can calculate the maximum of "WindowsPeakPagefileUsage" for each TMTM service, calculate the sum of such maximum values across all TMTM services, and then return the resulting number in gigabytes.

  1. Copy the Server Fix Pack ZIP file into a new directory. 

  2. Use the cd command to go to the new directory, and run one of the following commands (according to your database type, see below) in order to extract the "memory usage estimator" SQL scripts. 

    DB2

    unzip FixPack8100.425D_bPost_x64_Server FixPack8100.425D_bPost_x64_Server/windows/SQL/db2.64bit_mem_usage.sql

    MS SQL

    unzip FixPack8100.425D_bPost_x64_Server FixPack8100.425D_bPost_x64_Server/windows/SQL/mssql.64bit_mem_usage.sql

    Oracle

    unzip FixPack8100.425D_bPost_x64_Server FixPack8100.425D_bPost_x64_Server/windows/SQL/ora.64bit_mem_usage.sql


  3. Access FixPack8100.425D_bPost_x64_Server/windows/SQL from the new directory where the "memory usage estimator" SQL scripts were extracted to. Have your TMTM database credentials handy, and run one of the SQL scripts (see below) according to your database type.

    1. DB2

      1. Connect your DB2 command line processor to your database using the TMTM DB2 credentials:

        db2cmd
        db2 connect to <database_alias> user <user_name> using <password>

      2. Run the SQL script: db2 -stvf db2.64bit_mem_usage.sql
      3. Sample output:

        TOTAL_64BIT_SIZE_IN_GB
        ------------------------
        +6.33500976562500E+000
    2. MS SQL
      1. Run the SQL script: sqlcmd -S <sql_server_host_name> -U <user_id> -P <password> -d <database_name> -i mssql.64bit_mem_usage.sql
        Note that SQL Server Management Studio can be used instead of the sqlcmd command line utility. The content of the mssql.64bit_mem_usage.sql script needs to be copied and pasted into an SQL Server Management Studio's query window, and then executed.

      2. Sample output:

        total_64bit_size_in_gb
        ------------------------
        6.485919189453126
    1. Oracle
      1. Run the SQL script: sqlplus <user>/<password>@<TNS_name> @ora.64bit_mem_usage.sql
      2. Sample output:

        TOTAL_64BIT_SIZE_IN_GB
        ----------------------
        6.29614258

Note

The TOTAL_64BIT_SIZE_IN_GB value from the memory estimator SQL script is the estimated peak RAM usage expected for the upgraded 64-bit TMTM service processes (in gigabytes).

Make sure that your TMTM service machine has at least the amount of memory specified for the TMTM service processes plus any RAM usage for other processes (such as DB, TMTM agent installation, MainView Middleware Administrator, etc.) including any overhead for the operating system. If the amount of available memory on the machine is smaller, the available memory needs to be extended: in the case of a physical box by adding new memory to the box, in the case of a VM by re-configuring it to allow it to use more VRAM.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*