Your query and sort criteria sound like they should be fast.
In general if you are cutting off the stream at 10K don't use the /export
handler. Use the /select handler, it will be faster for sure. The reason
for the 30K sliding winding was that it maximized throughput over a long
export (many mill
Thanks for the quick response. We are generally seeing exports from Solr 5
and 7 to be roughly the same, but I’ll check out Solr 8.
Joel - We are generally sorting a on tlong field and criteria can vary from
searching everything (*:*) to searching on a combination of a few tint and
string types.
Can you share the sort criteria and search query? The main strategy for
improving performance of the export handler is adding more shards. This is
different than with typical distributed search, where deep paging issues
get worse as you add more shards. With the export handler if you double the
sha
Justin Sweeney wrote:
[Index: 10 shards, 450M docs]
> We are creating a CloudSolrStream and when we call CloudSolrStream.open()
> we see that call being slower than we had hoped. For some queries, that
> call can take 800 ms. [...]
As far as I can see in the code, CloudSolrStream.open() opens s
Hi,
We are currently working on a project where we are making heavy use of
/export in Solr in order to stream data back. We have an index with about
16 fields that are all docvalues fields and any number of them may be
requested to be streamed in results. Our index has ~450 million documents
sprea
