Address the points I brought up or don't reply with funny name calling. Below are two key points reiterated and re-articulated is an easy to answer way:
* Multi-select faceting is per-segment (true or false) * Filters are cached per-segment (true or false) On Tue, Jan 3, 2012 at 2:16 PM, Yonik Seeley <yo...@lucidimagination.com> wrote: > On Tue, Jan 3, 2012 at 5:03 PM, Jason Rutherglen > <jason.rutherg...@gmail.com> wrote: >> Yikes. I'd love to see a test showing that un-inverted field cache >> (which is for ALL segments as a single unit) can be used efficiently >> with NRT / soft commit. > > Please stop being a troll. > Solr as multiple faceting methods - only one uses un-inverted field cache. > > Oh, and for the record, Solr does have a faceting method in trunk that > caches per-segment. > There are always tradeoffs though - string faceting per-segment will > always be slower than string faceting over the complete index (due to > the cost of merging per-segment counts). > > Anyway, disabling any of those caches won't make anything any > faster... the data structures will still be built, they just won't be > reused. > Seems like you realized your original statement was erroneous and have > just reverted to troll state, trying to find something to pick at. > > -Yonik > http://www.lucidimagination.com
