On Wed, Sep 24, 2014 at 5:27 PM, Tomás Fernández Löbbe <[email protected]> wrote: > I think you are right. I think the name is this because it’s considering a > series of queries paging a result. The first X pages are going to be cached, > but once the limit is reached, no further pages are and the last superset > that fitted remains in cache.
I was confused about the confusion ;-) But your summary seems correct. queryResultWindowSize rounds up to a multiple of the window size for caching purposes. So if you ask for top 10, and the queryResultWindowSize is 20, then the top 20 will be cached (so if a user hits "next" to get to the next 10, it will still result in a cache hit). queryResultMaxDocsCached sets a limit beyond which the resulting docs aren't cached (so if a user asks for docs 10000 through 10010, we skip caching logic). -Yonik http://heliosearch.org - native code faceting, facet functions, sub-facets, off-heap data --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
