Rahul, the IndexSearcher of Solr gets shared with every request within two commits. That means one IndexSearcher + its caches got a lifetime of one commit. After every commit, there will be a new one created.
The cache does not mean, that they are applied automatically. They mean, that a filter from a query will be cached and whenever an user-query requieres the same filtering-criteria, they will use the cached filter instead of creating a new one on the fly. I.e: fq=inStock:true The result of this filtering-criteria gets cached one time. If another user asks again for a query with fq=inStock:true, Solr reuses the already existing filter. Since such filters are cached as byteVectors, they are not large. In this case it does not care for what the user is querying in his q-param. BTW: The IndexSearcher is threadsafe. So there is no problem with concurrent usage. Hope this helps??? Kind regards - Mitch -- View this message in context: http://lucene.472066.n3.nabble.com/IndexSearcher-and-Caches-tp833567p833841.html Sent from the Solr - User mailing list archive at Nabble.com.
