The field caches are per-segment, which are used for sorting and basic [slower] facets. The result set, document, filter, and multi-value facet caches are [in Solr] per-multi-segment.
Of these, the document, filter, and multi-value facet caches could be converted to be [performant] per-segment, as with some other Apache licensed Lucene based search engines. On Sat, Jul 7, 2012 at 10:42 AM, Yonik Seeley <yo...@lucidimagination.com>wrote: > On Sat, Jul 7, 2012 at 9:59 AM, Jason Rutherglen > <jason.rutherg...@gmail.com> wrote: > > Currently the caches are stored per-multiple-segments, meaning after each > > 'soft' commit, the cache(s) will be purged. > > Depends which caches. Some caches are per-segment, and some caches > are top level. > It's also a trade-off... for some things, per-segment data structures > would indeed turn around quicker on a reopen, but every query would be > slower for it. > > -Yonik > http://lucidimagination.com >
