That's what the "autowarm" number for filterCache is about. It re-executes the last N fq clauses and caches them. Similarly for some of the other autowarm.
But don't go wild here. Measure _then_ fix. Usually autowarming just a few (< 32) is sufficient. And remember that autowarming is done whenever you open a new searcher, so if you have your soft commits configured to be, say, 5 seconds you'll get minimal benefit here. Are you saying you have almost 1,000 differently-named fields in your documents? Or 1,000 _values_ in your category field? In either case, please measure your query performance before assuming you need to autowarm excessively. If you don't autowarm at all and your first few queries are acceptable after you open a new searcher then don't worry about it. Often the biggest win is just filling the lower-level Lucene caches which you can do with a very few queries. Best Erick On Mon, Oct 7, 2013 at 2:49 AM, user 01 <user...@gmail.com> wrote: > Sorry, didn't get you exactly. > > I need to warm up my queries after the newSearcher & firstSearcher are > initialized. I am trying to warm up the filter caches for a category field > but I have almost 1000 categories(& changing with time), which make it > impossible to list them in solrConfig.xml. Is there any way to iterate over > all categories & warm up the query for each ? > > > On Mon, Oct 7, 2013 at 12:10 PM, Furkan KAMACI <furkankam...@gmail.com>wrote: > >> If you are asking to read from a file for warm up and if there is not a >> capability for what you want I can open a Jira issue and send a patch. >> >> >> 2013/10/7 user 01 <user...@gmail.com> >> >> > what's the way to warm up filter queries for a category field with 1000 >> > possible values. Would I need to write 1000 lines manually in the >> > solrconig.xml or what is the format? >> > >>
