Depending on the size of the individual records returned, I'd use a decent size window (to minimize network and marshalling/unmarshalling overhead) of maybe 1000-10000 items sorted by id, and use that in combination with cursorMark. That will be easier on the server side in terms of garbage collection.
Best regards, --Jürgen On 16.09.2014 17:03, Ilya Bernshteyn 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 > -- Mit freundlichen Grüßen/Kind regards/Cordialement vôtre/Atentamente/С уважением *i.A. Jürgen Wagner* Head of Competence Center "Intelligence" & Senior Cloud Consultant Devoteam GmbH, Industriestr. 3, 70565 Stuttgart, Germany Phone: +49 6151 868-8725, Fax: +49 711 13353-53, Mobile: +49 171 864 1543 E-Mail: juergen.wag...@devoteam.com <mailto:juergen.wag...@devoteam.com>, URL: www.devoteam.de <http://www.devoteam.de/> ------------------------------------------------------------------------ Managing Board: Jürgen Hatzipantelis (CEO) Address of Record: 64331 Weiterstadt, Germany; Commercial Register: Amtsgericht Darmstadt HRB 6450; Tax Number: DE 172 993 071
