Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Looking into some streaming expression performance issues when there are many collections with many shards being queried and I found that SolrStream's open method creates a new HttpSolrClient for every replica being queried. For instance, in my test case, I have 10 collections with 100 shards each (rf=1) and I get 1000 HttpSolrClient instances in my SolrClientCache. If I reuse HttpSolrClient's per node hosting a replica (so 10 in my case), the query time for my expression drops by half (not too mention the reduced allocation load on the JVM).