It totally depends on how often you open a new searcher. If you have an index that updates once a day, running extensive autowarming queries can help. If you index frequently, it’s a balance between how much time you spend autowarming and how much time a user might have to wait.
In extreme cases, i.e. autoSoftCommits every second or hard-commit-with-opensearcher=true, it can be best to disable autowarming entirely. And pretty often, I find just autowarming the queryResultCache and filterCache with relatively low numbers (< 20) works quite well. I’ll also say that in the bad old days before docValues, autowarming had more of an impact if you faceted or sorted, as uninverting the structures on the heap could get very expensive. DocValues fields are much quicker to load, although they can still take a noticeable amount if time especially if there are lots… FWIW, Erick > On Aug 8, 2020, at 9:48 AM, Dave <hastings.recurs...@gmail.com> wrote: > > Ah. Glad you found it. Yeah warming queries are much better substituted with > home made scripts if you need them. I like to use the previous days logs and > run the last couple hundred or so on a cron in the morning. > >> On Aug 8, 2020, at 9:39 AM, Schwartz, Tony <tony.schwa...@cinbell.com> wrote: >> >> I did not have a suggester set up. I disabled the spell checker component, >> but that wasn't the problem. I found my issue... it was related to a >> warming query i was running for each newly opened searcher. Early on I >> enabled that, but I completely forgot about it. And i don't believe it's >> needed. I was hoping it would help with performance related to time >> filtering and sorting. But, now it seems to be performing quite well >> without it. >> >> Tony >> >> >> >> From: Schwartz, Tony >> Sent: Friday, August 7, 2020 6:27 PM >> To: solr-user@lucene.apache.org >> Subject: RE: solr startup >> >> suggester? what do i need to look for in the configs? >> >> Tony >> >> >> >> Sent from my Verizon, Samsung Galaxy smartphone >> >> >> >> -------- Original message -------- >> From: Dave >> <hastings.recurs...@gmail.com<mailto:hastings.recurs...@gmail.com>> >> Date: 8/7/20 18:23 (GMT-05:00) >> To: solr-user@lucene.apache.org<mailto:solr-user@lucene.apache.org> >> Subject: Re: solr startup >> >> It sounds like you have suggester indexes being built on startup. Without >> them they just come up in a second or so >> >>> On Aug 7, 2020, at 6:03 PM, Schwartz, Tony >>> <tony.schwa...@cinbell.com<mailto:tony.schwa...@cinbell.com>> wrote: >>> >>> I have many collections. When I start solr, it takes 30 - 45 minutes to >>> start up and load all the collections. My collections are named per day. >>> During startup, solr loads the collections in alpha-numeric name order. I >>> would like solr to load the collections in the descending order. So the >>> most recent collections are loaded first and are available for searching >>> while the older collections are not as important. Is this possible? >>> >>>
