How to Optimize Job FLow with Multiple tMaps

[Anonymous]

Hi All,

I am developing a job in talend. And there are multiple tMaps used in this job like 3 tables's join in a tMap and the output of this tMap will be used further as Source and 3 more tables as Lookup and so on... And the output of this tMap will be used for further join.

this job become very large. i want a solution so that i can improve the design. Please suggest me.

I also thought about child parent job mechanism but all tmap's output is dependent on lookup tables.

Thanks in advance

[Anonymous]

This is the screenshot of jobflow.

Please provide some solution

Untitled.png

[Anonymous]

Are the tables you are querying in the same database? If so, join in the SQL query. That will improve the efficiency of the job and will make it look far less busy.

[Anonymous]

Thanks for your reply !

Actually, There are other services also run on database server. So i can not perform operation on database side. Because these tables have millions of records.