Thank you!
That seems to be the case, I tried to execute queries without sorting
and only one document in the response and I got execution time in the
same range as before.
-- Aleksey
On 12-11-21 04:07 PM, Jack Krupansky wrote:
It could be that the time to get set up to return even the first result is
high and then each additional document is a minimal increment in time.
Do a query with &rows=1 (or even 0) and see what the minimum query time is
for your query, index, and environment.
-- Jack Krupansky
-----Original Message-----
From: Aleksey Vorona
Sent: Wednesday, November 21, 2012 6:04 PM
To: solr-user@lucene.apache.org
Subject: Partial results with not enough hits
In all of my queries I have timeAllowed parameter. My application is
ready for partial results. However, whenever Solr returns partial result
it is a very bad result.
For example, I have a test query and here its execution log with the
strict time allowed:
WARNING: Query: <omitted>; Elapsed time: 120Exceeded allowed search
time: 100 ms.
INFO: [] webapp=/solr path=/select
params={<omitted>&timeAllowed=100} hits=189 status=0 QTime=119
Here it is without such a strict limitation:
INFO: [] webapp=/solr path=/select
params={<omitted>&timeAllowed=10000} hits=582 status=0 QTime=124
The total execution time is different by mere 5 ms, but the partial
result has only about 1/3 of the full result.
Is it the expected behaviour? Does that mean I can never rely on the
partial results?
I added timeAllowed to protect from too expensive wide queries, but I
still want to return something relevant to the user. This query returned
30% of the full result, but I have other queries in the log where
partial result is just empty. Am I doing something wrong?
P.S. I am using Solr 3.6.1, index size is 3Gb and easily fits in memory.
Load Average on the Solr box is very low.
-- Aleksey
