On Wed, Apr 15, 2020 at 10:09:59AM +0100, Colvin Cowie wrote: > Hi, I can't answer the question as to what the optimal size of rows per > request is. I would expect it to depend on the number of stored fields > being marshaled, and their type, and your hardware.
It was a somewhat naive question, but I wasn't sure how to ask a better one. Having thought a bit more, I expect that the eventual solution to my problem will include a number of different changes, including larger pages, tuning several caches, providing a progress indicator to the user, and (as you point out below) re-thinking how I ask Solr for so many documents. > But using start + rows is a *bad thing* for deep paging. You need to use > cursorMark, which looks like it was added in 4.7 originally > https://issues.apache.org/jira/browse/SOLR-5463 > There's a description on the newer reference guide > https://lucene.apache.org/solr/guide/6_6/pagination-of-results.html#fetching-a-large-number-of-sorted-results-cursors > and in the 4.10 PDF on page 305 > https://archive.apache.org/dist/lucene/solr/ref-guide/apache-solr-ref-guide-4.10.pdf > > http://yonik.com/solr/paging-and-deep-paging/ Thank you for the links. I think these will be very helpful. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu
signature.asc
Description: PGP signature
