We are working on optimizing query performance. My concern was to ensure
some stable QoS. Given our API and UI layout, user may generate an
expensive query. Given the nature of the service, user may want to
"hack" it. Currently, our Search API is a good point to try to inflict
DoS on our server
The first thing I'd do is run your query with &debguQuery=on and look
at the "timings" section. That'll tell you what component is taking all
the time and should help you figure out where the problem is
But worst-case you could implement a custom component to stop
processing after some set num
Hi, we are running Solr 3.6.1 and see an issue in our load tests. Some
of the queries our load test script produces result in huge number of
hits. It may go as high as 90% of all documents we have (2.5M). Those
are all range queries. I see in the log that those queries take much
more time to ex
