Hi Michael,
Thank you very much for your reply!
Does it mean that when timeAllowed is used only search is interrupted and
document retrieval is not?
In order to check the total time of the query I run curl with linux time to
measure the total time including retrieving of documents. If I understo
And think about distributed search, you are going through a 'proxy'
which, as well as forwarding your docs, must also merge any docs from
different shards into a single result set. That is likely to take some
time on 30,000 docs, and isn't a job that is needed on non-distributed
search.
Upayavira
If you are going to request 30,000 rows, you can give up on getting good
performance. It is not going to happen.
Even without all the disk accesses, think about how much is sent over the
network, then parsed by the client. The client cannot even start working with
the data until it is all recei
(This is based on my knowledge of 3.6 - not sure if this has changed in 4.0)
You are using rows=3, which requires retrieving 3 documents from disk.
In a non-distributed search, the QTime will not include the time it takes to
retrieve these documents, but in a distributed search, it will.
