Have you tried the integration without the hash table? It’s logical that preloading the data would make the integration faster but I’ve been burned more than once with such assumptions. It may be that the database and the adapter may be able to keep up just fine with your integration, and the bottleneck may exist elsewhere–if at all. Pre-optimizing without testing (perhaps you have) is a crap shoot–you never know what you’ll get.
Case in point–the current “optimization” reduces integration throughput to zero since it doesn’t work
Chewing up the adapter’s memory with a hash table may adversely affect its performance. Measure, measure, measure.
#Integration-Server-and-ESB#Universal-Messaging-Broker#webMethods