It seems possible to cache the results of facet queries on a per segment basis, providing the caching you're describing.
On Fri, Aug 21, 2009 at 8:42 AM, Fuad Efendi<f...@efendi.ca> wrote: >>actually a hybrid that goes back to DocSet intersections when it's more > efficient > > I noticed that too when I played with it, for large query results DocSet > intersections are de-facto standard; but when "faceting" started CNET had > only 400,000 documents :) > Nowadays even 2-3 seconds response time is bad... may be storing all users' > queries and executing some tasks on background (storing "facets" in a > database similar to heavy warehouse, predicting facet counts depending on > query terms and domain analysis, and etc)? > > > On Fri, Aug 21, 2009 at 11:25 AM, Fuad Efendi<f...@efendi.ca> wrote: >> I was joking [off-topic]; "faceting" as a DocSet intersections' replaced > by >> trivial term count calcs which is extremely faster in some (if not all) > use >> cases, including possibly even NON-tokenized (with standard faceting we > can >> use FilterCache)... > > One size does not fit all. The enum method is not outdated or > deprecated, and still works better in some scenarios. The new > faceting code is actually a hybrid that goes back to DocSet > intersections when it's more efficient. > > -Yonik > http://www.lucidimagination.com > > >
