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 jMe
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
> 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 MultiThreadedHttpConnectio
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..
regards
On Fri, Jun 17, 2011 at 12:50 PM, Ahmet Arslan wrote:
> > SolrServer server = new CommonsHttpSolrServer(URL);
> >
> > t
> SolrServer server = new CommonsHttpSolrServer(URL);
>
> through out the class. How can I improve the connection, in
> my case: should I need to close the server after fetching
> the result or CommonsHttpSolrServer(URL); will maintain at
> their end. There is other way: I can make this as static
