Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us at Qlik Connect 2026 in Orlando, April 13–15: Register Here!

Executing a Job on a JobServer using TAC is slower compared to execution in Studio or as a standalone Job

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
TalendSolutionExpert
Contributor II
Contributor II

Executing a Job on a JobServer using TAC is slower compared to execution in Studio or as a standalone Job

Last Update:

Feb 9, 2024 1:22:49 PM

Updated By:

Jamie_Gregory

Created date:

Apr 1, 2021 6:20:07 AM

Talend Version6.x

Summary

A Job executes slower on a JobServer using TAC compared to execution in Studio or as standalone Job.
Additional Versions 
ProductTalend Data Integration
ComponentJobServer
Problem Description

When executing a Job on a JobServer using TAC or Job Conductor, the execution time is slower compared to the execution time in Studio or as a standalone Job.

Problem root causeUsing a tlogRow component in the Job. tLogRow is a component that should be dedicated to the debugging.
Solution or Workaround

Deactivate or remove the tlogRow component in the Job.

Use tFileOutputDelimited or a similar component to write output.

JIRA ticket number 
Version history
Last update:
‎2024-02-09 01:22 PM
Updated by: