Hi all, I'm trying to work out the optimum cache settings for our Solr server, I'll begin by outlining our usage.
Number of documents: approximately 25,000 Commit frequency: sometimes we do massive amounts of sequential commits, most of the time its less frequent but still several times an hour We make heavy use of faceting and sorting, and the number of possible facets led to choosing a filterCache size of about 50,000 The problem we have is that the default cache settings resulting in very low hit rates (less than 30% for documents, less than 1% for filterCache), so we upped the cache size up gradually until the hit rates were in the 80s-90s, now we have the issue of commits being very slow (more than 5 seconds for a document), to the point where it causes a timeout elsewhere in our systems. This is made worse by the fact that committing seems to empty the cache, given that it takes about an hour to get the cache to a good state this is obviously very problematic. Is there a way for commits to selectively empty the cache? Any advice regarding the config would be appreciated. The server load is relatively low, ideally we're looking to minimize the response time rather than aim for CPU or memory efficiency. Regards, Andrew Ingram
