Almost everyone who has some experience with Solr would have noticed one thing—right after startup or searcher reopening (such as a soft autocommit), Solr doesn't have such query performance as after running for a while. This is happening because Solr doesn't have any information stored in caches, the I/O is not optimized, and so on. Can we do something about it? Of course we can, and this recipe will show you how to do it.
First of all, we need to identify the most common and the heaviest queries that we send to Solr. I have two ways of doing this: first, I analyze the logs that Solr produces and see how queries are behaving. I tend to choose those queries that are run often and those that run slowly. The second way of choosing the right queries is analyzing the applications that use Solr and see what queries they produce, what queries will be the most crucial, and so on. Based on my experience, the log...