[
https://issues.apache.org/jira/browse/SOLR-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202585#comment-14202585
]
Otis Gospodnetic commented on SOLR-4587:
----------------------------------------
bq. I believe that much of the job in luwak also comes from the realization
that the number of documents must be reduced prior to looping
That's correct. In our work with Luwak this is the key. You can have 1M
queries, but if you *really* need to run incoming documents against all 1M
queries expect to have VERY low throughput and VERY HIGH match latencies. We
are working with 1-2M queries and reducing those to a few thousand queries with
Luwak's Presearcher, and still have latencies of a few hundred milliseconds.
> Implement Saved Searches a la ElasticSearch Percolator
> ------------------------------------------------------
>
> Key: SOLR-4587
> URL: https://issues.apache.org/jira/browse/SOLR-4587
> Project: Solr
> Issue Type: New Feature
> Components: SearchComponents - other, SolrCloud
> Reporter: Otis Gospodnetic
> Fix For: Trunk
>
>
> Use Lucene MemoryIndex for this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
