If I need to retrieve historical data for 500 symbols via the socket lookup. Is it faster to use a thread pool of 50 threads making new connections to the LookupPort for each symbol, or push the 500 requests through on one connection to the LookupPort with a RequestID for each symbol? I think what this boils down to is can I take advantage of concurrent request handling on your server? Or maybe get my requests on your queue sooner? Is there a limit to how many requests I can make on one connection (with unique RequestIDs) at one time? Is there a disadvantage to a large number of requests on one connection?
Thanks

It will definately be more efficient to make multiple socket connections to IQConnect and make simultaneous connections. You will have to do some testing to find out where the breakeven point is in terms of speed vs CPU usage vs available bandwidth for your configuration. Most developers find that between 5 and 10 simultaneous connections is optimal.