Performance would be better getting them all at the same time, but the behavior would kind of stink (long pause before a response, big results stuck in memory, etc).
If you're using a relatively up-to-date version of Solr, you should check out the "cursormark" feature: https://wiki.apache.org/solr/CommonQueryParameters#Deep_paging_with_cursorMark That's the magic knock that will get you what you want. Michael Della Bitta Applications Developer o: +1 646 532 3062 appinions inc. “The Science of Influence Marketing” 18 East 41st Street New York, NY 10017 t: @appinions <https://twitter.com/Appinions> | g+: plus.google.com/appinions <https://plus.google.com/u/0/b/112002776285509593336/112002776285509593336/posts> w: appinions.com <http://www.appinions.com/> On Tue, Sep 16, 2014 at 11:03 AM, Ilya Bernshteyn <ily...@gmail.com> wrote: > If I query for IDs and I do not care about order, should I still expect > better performance paging the results? (e.g. rows=1000 or rows=10000) The > use case is that I need to get all of the IDs regardless (there will be > thousands, maybe 10s of thousands, but not millions) > > Example query: > > > http://domain/solr/select?q=ACCT_ID%3A1153&fq=SOME_FIELD%3SomeKeyword%2C+SOME_FIELD_2%3ASomeKeyword&rows=10000&fl=ID&wt=json > > With this kind of query, I notice that rows=10 returns in 5ms, while > rows=10000 (producing about 7000 results) returns in about 500ms. > > Another way to word my question, if I have 100k not ordered IDs to > retrieve, is performance better getting 1k at a time or all 100k at the > same time? > > Thanks, > > Ilya >
