The point of filter queries is that they are applied very early in the searching algorithm, and thus cut the amount of work later on. Some complex queries take a lot of time and so this pre-trimming helps a lot.
On Thu, Aug 25, 2011 at 2:37 PM, Yonik Seeley <yo...@lucidimagination.com> wrote: > On Thu, Aug 25, 2011 at 5:19 PM, Michael Ryan <mr...@moreover.com> wrote: >>> 10,000,000 document index >>> Internal Document id is 32 bit unsigned int >>> Max Memory Used by a single cache slot in the filter cache = 32 bits x >>> 10,000,000 docs = 320,000,000 bits or 38 MB >> >> I think it depends on where exactly the result set was generated. I believe >> the result set will usually be represented by a BitDocSet, which requires 1 >> bit per doc in your index (result set size doesn't matter), so in your case >> it would be about 1.2MB. > > Right - and Solr switches between the implementation depending on set > size... so if the number of documents in the set were 100, then it > would only take up 400 bytes. > > -Yonik > http://www.lucidimagination.com > -- Lance Norskog goks...@gmail.com
