I'd set filterCache and queryResultCache to zero (size and autowarm count)
Leave documentCache alone IMO as it's used to store documents on disk as the pass through various query components and doesn't autowarm anyway. I'd think taking it out would skew your results because of multiple decompressions. Best, Erick On Tue, Jun 30, 2015 at 10:29 AM, wwang525 <wwang...@gmail.com> wrote: > Hi, > > I am currently investigating the queries with a much small index size (1M) > to see the grouping, faceting on the performance degradation. This will > allow me to do a lot of tests in a short period of time. > > However, it looks like the query is executed much faster the second time. > This is tested after re-indexing, and not immediately executed again. It > looks like it may be due to auto warming during or after re-indexing? > > I would like to get the response profile (query, faceting etc) for the same > query in two separate requests without any cache or warming so that I get a > good average number and not much fluctuation. What are the settings that I > need to disable (temporarily) just for the purpose of the investigation? In > the solrconfig.xml, I can see filterCache, queryResultCache, documentCache > etc. I am not sure what need to be disabled to facilitate my work. > > I understand that cache and warming setting will be very helpful in load > test later on. However, if I can optimize the query in a single request > scenario, the performance will be in a much better shape with all the cache > and warming setting during a load test scenario. > > Thanks, > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/How-to-do-a-Data-sharding-for-data-in-a-database-table-tp4212765p4214968.html > Sent from the Solr - User mailing list archive at Nabble.com.
