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 Developer Tool

Find Data Transformation Bottlenecks Through the Developer Tool

Use the Developer tool to configure a Script, XMap, or Library object to generate a profile file that reveals the content and structure of data of the object, then run the object and analyze the profile to identify bottlenecks that decrease the performance of the object.
  1. If the object isn't associated with a Data Processor transformation, add it to a Data Processor transformation in the Developer tool.
  2. On the Object Explorer, double-click the Data Processor transformation that contains the object.
  3. At the bottom of the editor, select the
    Script
    tab.
  4. For each code anchor that you want to check, add the remark "DO PROFILER".
    Add the remark to repeating groups, as repeating groups tend to create bottlenecks.
    When you run the object, the Developer tool generates a profile file that reveals the content and structure of data of the anchors you added the remark to.
    The following image shows a sample Data Processor transformation with a "DO PROFILER" remark for a repeating group in a Script object:
    The Script tab of the Developer tool editor shows a tree of the anchors and elements of a Script object. The top anchor in the tree is Parser. The Parser contains one RepearingGroup anchor. In the RepearingGroup anchor, the value of remark is "DO PROFILER".
  5. At the bottom of the editor, select the
    Settings
    tab.
  6. Expand
    Output Control
    . In the
    Run-time events
    area, under
    Log run-time events
    , select
    Never
    .
    Event logging is disabled. Re-enable event logging after you complete the analyses.
  7. Save the transformation.
  8. If you added the object to the transformation, export the object from the transformation.
  9. Run the object or the transformation that contains the object.
    The Developer tool creates the following file in the workspace directory on your local machine where it writes temporary files:
    AppData\Local\Temp\<workspace>\<object name>\Results\profiler-output\profiler-output.txt
    For example:
    AppData\Local\Temp\DTProjectsWorkspace\dp_1788\Results\profiler-output\profiler-output.txt
  10. Examine the file to identify bottlenecks.

0 COMMENTS

We’d like to hear from you!