https://community.qlik.com/t5/Talend-Studio/resolved-Optimize-look-up-in-Talend/m-p/2318176#M88545 <P>Hi All,<BR />I need to lookup a table (using tMap) in one of my Talend jobs. However, this table need to be looked up three times based on different join conditions and has around 800k rows.<BR />Please suggest any ways to optimize the performance of the Job given the constraints.<BR />Thanks in advance.</P> Mon, 07 Dec 2015 07:42:26 GMT Anonymous 2015-12-07T07:42:26Z https://community.qlik.com/t5/Talend-Studio/resolved-Optimize-look-up-in-Talend/m-p/2318176#M88545 <P>Hi All,<BR />I need to lookup a table (using tMap) in one of my Talend jobs. However, this table need to be looked up three times based on different join conditions and has around 800k rows.<BR />Please suggest any ways to optimize the performance of the Job given the constraints.<BR />Thanks in advance.</P> Mon, 07 Dec 2015 07:42:26 GMT https://community.qlik.com/t5/Talend-Studio/resolved-Optimize-look-up-in-Talend/m-p/2318176#M88545 Anonymous 2015-12-07T07:42:26Z https://community.qlik.com/t5/Talend-Studio/resolved-Optimize-look-up-in-Talend/m-p/2318177#M88546 Take a look here ( <A href="https://help.talend.com/search/all?query=tMap+lookup+models" rel="nofollow noopener noreferrer">https://help.talend.com/search/all?query=tMap+lookup+models</A>). You should use the "Load Once" option. This will load your lookup data into memory at the beginning of the job which makes the lookup significantly faster than loading it 800k times. You can make this quicker by loading the data into a tHashOutput component in a subjob before the subjob with the lookup and then use tHashInputs (connected to the tHashOutput above) as many times as you need them. This will mean that only one query will be fired against your database and the data will be reused for as many lookups as you need. Mon, 07 Dec 2015 09:17:29 GMT https://community.qlik.com/t5/Talend-Studio/resolved-Optimize-look-up-in-Talend/m-p/2318177#M88546 Anonymous 2015-12-07T09:17:29Z