Forum Discussion
SpiroTaleski
4 years agoValued Contributor
Below are some points that you should take about In-Memory Lookup Snap:
- The join operation within the snap will start, when the right input document stream ends. Meaning that, in your case the snap first will wait the aggregation of the data to be completed and then processed by In-Memory Lookup.
- All the right input data is loaded in memory(of the JVM) as a lookup data. So, it is possible for the Snap to cause a poor performances.
Did you have another processes that are running in parallel with this process, that are also using similar snaps(join, snaps for aggregation, group snaps etc.) inside, which have an impact of the memory?
Did you tried the same scenario using JOIN Snap?
Regards,
Spiro Taleski