bq: can I turn off the three cache and send a lot of queries to Solr I really think you're missing the easiest way to do that. To not put anything in the filter cache, just don't send any fq clauses.
As far as the doc cache is concerned, by and large I just wouldn't worry about it. With MMapDirectory, it's less valuable than it was when it was created. It's primary usage is that the components in a single query don't have to re-read the docs from disk. As far as the queryResultCache, by not putting fq clauses on the warmup queries you won't hit this cache next time around. Best, Erick On Tue, Aug 18, 2015 at 1:17 PM, wwang525 <wwang...@gmail.com> wrote: > Hi Erick, > > I just tested 10 different queries with or without the faceting search on > the two properties : departure_date, and hotel_code. Under cold cache > scenario, they have pretty much the same response time, and the faceting > took much less time than the query time. Under cold cache scenario, the > "query" (under timing) is still the "bottleneck". > > I understand that the low level cache needs to be warmed up to do a more > realistic test. However, I do not have a good and consistent way to warm up > the low level cache without caching the filter queries at the same time. If > I load test some random queries before I test these 10 individual queries, I > can see a better response time in some cases, but that could also be due to > filter query cache. > > To load up low level lucene cache without creating filtercache/document > cache etc, can I turn off the three cache and send a lot of queries to Solr > before I start to test the performance of each individual queries? > > Thanks > > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Is-it-a-good-query-performance-with-this-data-size-tp4223699p4223758.html > Sent from the Solr - User mailing list archive at Nabble.com.
