Performance Tuning Guide

10.4.0
- 10.5.6
- 10.5

Back Next

Example

When you run a session, the session log lists run information and thread statistics similar to the following text:

***** RUN INFO FOR TGT LOAD ORDER GROUP [1], CONCURRENT SET [1] *****
Thread [READER_1_1_1] created for [the read stage] of partition point [SQ_two_gig_file_32B_rows] has completed.
        Total Run Time = [505.871140] secs
        Total Idle Time = [457.038313] secs
        Busy Percentage = [9.653215]
Thread [TRANSF_1_1_1] created for [the transformation stage] of partition point [SQ_two_gig_file_32B_rows] has completed.
        Total Run Time = [506.230461] secs
        Total Idle Time = [1.390318] secs
        Busy Percentage = [99.725359]
        Thread work time breakdown:
                LKP_ADDRESS: 25.000000 percent
                SRT_ADDRESS: 21.551724 percent
                RTR_ZIP_CODE: 53.448276 percent
Thread [WRITER_1_*_1] created for [the write stage] of partition point [scratch_out_32B] has completed.
        Total Run Time = [507.027212] secs
        Total Idle Time = [384.632435] secs
        Busy Percentage = [24.139686]

In this session log, the total run time for the transformation thread is 506 seconds and the busy percentage is 99.7%. This means the transformation thread was never idle for the 506 seconds. The reader and writer busy percentages were significantly smaller, about 9.6% and 24%. In this session, the transformation thread is the bottleneck in the mapping.

To determine which transformation in the transformation thread is the bottleneck, view the busy percentage of each transformation in the thread work time breakdown. In this session log, the transformation RTR_ZIP_CODE had a busy percentage of 53%.

Rename Saved Search

Table of Contents

Performance Tuning Guide

Performance Tuning Guide

Example

Example