Table of Contents

Search

  1. Preface
  2. Performance Tuning Overview
  3. Target Optimization
  4. Source Optimization
  5. Transformation Optimization
  6. Mapping Optimization
  7. Partitioned Mapping Optimization
  8. Run-time Optimization
  9. SQL Data Service Optimization
  10. Web Service Optimization
  11. Connections Optimization
  12. Data Transformation Optimization

Performance Tuning Guide

Performance Tuning Guide

Find Data Transformation Bottlenecks through the Command Line Interface

Find Data Transformation Bottlenecks through the Command Line Interface

Use the Data Processor command line interface to generate an output file for a Script, XMap, or Library object, and then analyze the contents of the file to identify bottlenecks that decrease the performance of the object.
For more information about using the command line interface, see the
Data Transformation Engine Developer Guide
.
  1. Open the command line interface on the machine where you run the object:
    • On a Windows machine, open a command window.
    • On a Linux or UNIX machine, open a command line.
  2. Run the following command:
    CM_console <object name> -f<input file name> -o<output file name>
    Where:
    • <object name> is the name of the object to run.
    • <input file name> is the path and file name of the input file on the local file system.
    • <output file name> is the output file name. By default, the CM_console command directs output to the screen.
    For example:
    CM_console MyXMap -fInputFile.txt -oResults.xml
  3. Open another terminal on the same machine and run a command that shows active processes. For example, on a Linux machine, run the
    top
    command. Copy the CM_console Process ID (PID).
  4. From the
    <Informatica installation directory>/tools/debugtools/pmstack
    folder run the
    Pmstack
    command using the following syntax:
    ./pmstack -p <CM_console Process PID>
  5. Repeat the process a few more times at short intervals. For example, run the process three more times at one minute intervals.
  6. Open the output files that the command created and search each file for repetitions of the following string:
    RepeatingGroupMapping::map
    The number of repetitions of this string indicates the instance of the repeating group that creates a bottleneck. For example, if your run the command four times, and the output file contains three instances of
    RepeatingGroupMapping::map
    in the same location each time you run the command, the third repeating group is the bottleneck.

0 COMMENTS

We’d like to hear from you!