You are building a complex Job and want to explore different options for optimizing execution times using parallelism. How can you identify execution…

To identify execution times to verify the effectiveness of your changes, you can use one of these

methods:

Reading the time stamps from the execution console in the Run view. This method allows you to see

the start and end time of each subjob and component in your job, as well as the total execution time

of the job. You can also see the number of rows processed by each component and the status of the

job (success or failure).

Observing the execution times that annotate the flows in the Designer. This method allows you to

see the execution time of each flow (main, lookup, reject, etc.) between components in your job. You

can also see the number of rows processed by each flow and the throughput (rows per second) of

each flow.

You cannot use these methods to identify execution times:

Observing the execution time in the Code view. This method does not show you the execution time

of your job or its components, but only the generated code of your job in Java or Perl. The Code view

is useful for debugging or customizing your code, but not for measuring performance.

Comparing time stamps in Trace Debug mode. This method does not show you the execution time of

your job or its components, but only the values of each column for each row processed by your job.

The Trace Debug mode is useful for tracing data quality or transformation issues, but not for

measuring performance. Reference: Talend Open Studio: Open-source ETL and Free Data Integration

| Talend, [Run view - 7.3], [Designer - 7.3], [Code view - 7.3], [Trace Debug mode - 7.3]