We need to know a LOT more about your site. Number of documents, size of index, 
frequency of updates, length of queries approximate size of server (CPUs, RAM, 
type of disk), version of Solr, version of Java, and features you are using 
(faceting, highlighting, etc.).

After that, we’ll have more questions.

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)


> On Dec 22, 2015, at 4:58 PM, Vincenzo D'Amore <v.dam...@gmail.com> wrote:
> 
> Hi All,
> 
> my website is under pressure, there is a big number of concurrent searches.
> When the connected users are too many, the searches becomes so slow that in
> some cases users have to wait many seconds.
> The queue of searches becomes so long that, in same cases, servers are
> blocked trying to serve all these requests.
> As far as I know because some searches are very expensive, and when many
> expensive searches clog the queue server becomes unresponsive.
> 
> In order to quickly workaround this herd effect, I have added a
> default timeAllowed to 15 seconds, and this seems help a lot.
> 
> But during stress tests but I'm unable to understand when and what requests
> are affected by timeAllowed parameter.
> 
> Just be clear, I have configure timeAllowed parameter in a SolrCloud
> environment, given that partial results may be returned (if there are any),
> how can I know when this happens? When the timeAllowed parameter trigger a
> partial answer?
> 
> Best regards,
> Vincenzo
> 
> 
> 
> -- 
> Vincenzo D'Amore
> email: v.dam...@gmail.com
> skype: free.dev
> mobile: +39 349 8513251

Reply via email to