So is it a better approach to query for smaller rows, say 500, and keep
increasing the start parameter? wouldnt that be slower since I have an
increasing start parameter and I will also be sorting by the same field in
each of my queries made to the multiple shards?
Also, does it make sense to have
Don't query for 5000 documents. That is going to be slow no matter how it is
implemented.
wunder
On Nov 5, 2012, at 1:00 PM, Rohit Harchandani wrote:
> Hi,
> So it seems that when I query multiple shards with the sort criteria for
> 5000 documents, it queries all shards and gets a list of docum
Hi,
So it seems that when I query multiple shards with the sort criteria for
5000 documents, it queries all shards and gets a list of document ids and
then adds the document ids to the original query and queries all the shards
again.
This process of doing the join of query results with the unique i
Hi,
The same query is fired always for 500 rows. The only thing different is
the "start" parameter.
The 3 shards are in the same instance on the same server. They all have the
same schema. But the inherent type of the documents is different. Also most
of the apps queries goes to shard "A" which h
Hi,
Maybe you can narrow this down a little further. Are there some
queries that are faster and some slower? Is there a pattern? Can you
share examples of slow queries? Have you tried &debugQuery=true?
These 3 shards is each of them on its own server or? Is the slow
one always the one tha
