So I read this: http://wiki.apache.org/solr/SolrCaching#filterCache
and specifically
The filter cache stores the results of any filter queries ("fq" parameters) that Solr is explicitly asked to execute. (Each filter is executed and cached separately. When it's time to use them to limit the number of results returned by a query, this is done using set intersections.)
So my question is this. Lets say my app filters on a set of different formatsIDs. If the format ids are numeric say 1,2,3,4,5. And there are many permutations of those being sent in queries as fq parameters.
if I wrote a warming query like this...
...
<str name="fq">format:(1)+OR+format:(2)+OR+format:(3)+OR+format:(4)+OR+format:(5)</str>
...
Would that warm things up and help all my queries trying to filter by various permutations of those formats OR... only folks searching for that permutation?
Should I instead create 5 separate warming queries (1 for each format) to take advantage of "set intersection"?
Or will that query create the sets for each format?
Example queries
...fq=format:(1)+OR+format:(2)...
...fq=format:(1)+OR+format:(3)...
...fq=format:(2)+OR+format:(3)...
...fq=format:(2)+OR+format:(5)...
etc...
so none of those I believe will use the filter cache created by the warming query listed above.