Table of Contents

Search

  1. Abstract
  2. Supported Versions
  3. Tuning and Sizing Guidelines for Data Engineering Integration (10.4.x)

Tuning and Sizing Guidelines for Data Engineering Integration (10.4.x)

Tuning and Sizing Guidelines for Data Engineering Integration (10.4.x)

Case Study: Java String Port Conversion Overhead

Case Study: Java String Port Conversion Overhead

The following case study compares performance between string ports and numeric ports and evaluates the UTF conversion overhead for port processing.

Test Setup

The study compares one operation on 25 string ports to one operation on 25 numeric ports. The operation is performed in the Java transformation. For additional comparison, the same operation is performed in the Expression transformation.

Environment

Chipset
Intel® Xeon® CPU E5-2650 v4 @ 2.20GHz
Cores
12 cores
Memory
256 GB
Operating system
Red Hat Enterprise Linux 7.2
Hadoop cluster
12 nodes
String ports
7 ports
Data volume
~ 750 GB

Performance Chart

The following performance chart compares the time taken for the operation to process the string and numeric ports in the Java transformation and the Expression transformation:
This image shows a performance chart on the performance of string ports and numeric ports that are processed by the Java transformation and the Expression transformation. The graph on the left shows performance for string ports. The graph on the right shows performance for numeric ports. In the graph on the left, the blue bar depicts performance of string ports in the Expression transformation. The orange bar depicts performance of string ports in the Java transformation. The blue bar is shorter than the orange bar. On the right, the blue bar and the orange bar have more similar heights.

Conclusions

Based on the case study, the Java transformation experiences an overhead cost of around 10% for numeric ports. For string ports, the same overhead cost is around 40%.

0 COMMENTS

We’d like to hear from you!