topic Re: Performance Improvement for multiple lookup tables in Talend Studio https://community.qlik.com/t5/Talend-Studio/Performance-Improvement-for-multiple-lookup-tables/m-p/2414802#M140112 <P>Hello,</P> <P>The best things you can do first is to separate this job, if impossible, into many other subjobs.</P> <P>Lookup in Talend means you'll charge the entire result of the query into java ram, so if you have huge amount of data or a lot of lookup the job will crash before launching.</P> <P>If you can't separate this job into many, then you should consider rework the job and create the join in SQL instead of using Talend</P> Mon, 05 Feb 2024 11:03:18 GMT jeoste 2024-02-05T11:03:18Z Performance Improvement for multiple lookup tables https://community.qlik.com/t5/Talend-Studio/Performance-Improvement-for-multiple-lookup-tables/m-p/2357144#M122516 <P>Hi,</P><P></P><P></P><P>I am using the Talend Open Studio Data Integration (TOS_DI) v8.0.1 and have created the job below.</P><P><span class="lia-inline-image-display-wrapper" image-alt="0695b00000nREyPAAW.png"><img src="https://community.qlik.com/t5/image/serverpage/image-id/144057iAE42C23A6AF695EE/image-size/large?v=v2&amp;px=999" role="button" title="0695b00000nREyPAAW.png" alt="0695b00000nREyPAAW.png" /></span></P><P></P><P></P><P>Is there anything that can be done to improve the performance for the job?</P><P></P><P></P><P>Are there any multithreading that can be done on the lookup tables to allow faster data integration?</P><P></P><P></P><P></P><P></P> Tue, 22 Aug 2023 08:08:54 GMT https://community.qlik.com/t5/Talend-Studio/Performance-Improvement-for-multiple-lookup-tables/m-p/2357144#M122516 anonymousmater 2023-08-22T08:08:54Z Re: Performance Improvement for multiple lookup tables https://community.qlik.com/t5/Talend-Studio/Performance-Improvement-for-multiple-lookup-tables/m-p/2414802#M140112 <P>Hello,</P> <P>The best things you can do first is to separate this job, if impossible, into many other subjobs.</P> <P>Lookup in Talend means you'll charge the entire result of the query into java ram, so if you have huge amount of data or a lot of lookup the job will crash before launching.</P> <P>If you can't separate this job into many, then you should consider rework the job and create the join in SQL instead of using Talend</P> Mon, 05 Feb 2024 11:03:18 GMT https://community.qlik.com/t5/Talend-Studio/Performance-Improvement-for-multiple-lookup-tables/m-p/2414802#M140112 jeoste 2024-02-05T11:03:18Z