I suggest you just try some things and see. The real problem isn't the SolrJ side, it's whether your Solr instance can handle the load.
But assuming that your Solr instance can keep up, there's no reason setting this to 30-40 would be a problem. You might also think about using something like jMeter to exercise your server to see if #it# will handle the load. Best Erick On Sun, Jun 19, 2011 at 2:05 PM, Ranveer <ranveer.s...@gmail.com> wrote: > thanks.. > however few more query. > How to maintain connections threads (max and min settings)? > What would be ideal setting for max in setMaxConnectionsPerHost method. Will > it be ok for 30 to 40 concurrent user. How thread will be maintain for > > MultiThreadedHttpConnectionManager class. > > > > On Sunday 19 June 2011 02:04 PM, Ahmet Arslan wrote: >>> >>> for heavy use (30 to 40 concurrent >>> user) will it work. >>> How to open and maintain more connection at a time like >>> connection pool. So >>> user cat receive fast response.. >> >> It uses HttpClient under the hood. You can pass httpClient to its >> constructor too. It seems that MultiThreadedHttpConnectionManager has >> setMaxConnectionsPerHost method. >> >> String serverPath = "http://localhost:8983/solr";; >> HttpClient client = new HttpClient(new >> MultiThreadedHttpConnectionManager()); >> URL url = new URL(serverPath); >> CommonsHttpSolrServer solrServer = new CommonsHttpSolrServer(url, client); > >
