https://community.qlik.com/t5/Talend-Studio/Processing-slowness-and-best-practices/m-p/2243880#M30226 Lookup are just reading while main process is writing in some tables, this should be a reason. <BR />If you use jdts driver, switch to official MS SQL driver which is faster. <BR />At design level, maybe you should store output in memory to limite tDBOutput operations. Sat, 09 May 2020 07:46:09 GMT TRF 2020-05-09T07:46:09Z https://community.qlik.com/t5/Talend-Studio/Processing-slowness-and-best-practices/m-p/2243879#M30225 <P>All, all the lookups load very quickly, but the main process flow is very very slow, moving just a few records at a time. In the example below, UserDomain has 70,0001 records but it's taken several minutes just to get to 2215. Why does it process so slow and is there another design (best practice) which can make faster?</P> <P>&nbsp;</P> <P><SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Capture.PNG" style="width: 678px;"><span class="lia-inline-image-display-wrapper" image-alt="0683p000009Ma2U.png"><img src="https://community.qlik.com/t5/image/serverpage/image-id/147505i97965911B44A32BC/image-size/large?v=v2&amp;px=999" role="button" title="0683p000009Ma2U.png" alt="0683p000009Ma2U.png" /></span></SPAN></P> Sat, 16 Nov 2024 02:29:11 GMT https://community.qlik.com/t5/Talend-Studio/Processing-slowness-and-best-practices/m-p/2243879#M30225 jimbo20814 2024-11-16T02:29:11Z https://community.qlik.com/t5/Talend-Studio/Processing-slowness-and-best-practices/m-p/2243880#M30226 Lookup are just reading while main process is writing in some tables, this should be a reason. <BR />If you use jdts driver, switch to official MS SQL driver which is faster. <BR />At design level, maybe you should store output in memory to limite tDBOutput operations. Sat, 09 May 2020 07:46:09 GMT https://community.qlik.com/t5/Talend-Studio/Processing-slowness-and-best-practices/m-p/2243880#M30226 TRF 2020-05-09T07:46:09Z