On Wed, Nov 10, 2010 at 2:57 AM, Em <mailformailingli...@yahoo.de> wrote:
> > Hi List, > > in one of our application's use-case scenarios we create a response from > different data sources. > In clear words: We combine different responses from different data sources > (SQL, another Webservice and Solr) to one response. > > We would cache this information per request for a couple of minutes or > hours > outside of solr, since the data to cache does not come only from solr > itself. > > However, I am not sure whether it would make sense to disable Solr's > internal cache-mechanisms or at last which cache-mechanisms I can disable, > because I am not sure what are the impacts of each cache in the long run. > > In general, Solr caches are essential for performance and it only caches those objects which were required by one or more of your queries. You can only decrease Solr's performance by turning off its cache. If the reason behind turning off Solr cache is that your custom cache and Solr are running on the same box, then you must monitor performance while reducing the sizes of the caches and then lower the Solr heap based on your peak memory load with the reduced cache sizes. > A query is usually type of dismax and uses some functionQueries. > We do not sort, but we may use some filterQueries. > > Furthermore we retrive just one of up to 10 (stored) fields from our index. > Most of the time it will be the same field (95-98% of the requests). > > I think using the filterCache makes sense, but what about documentCache and > the others? > Since I retrive in 95-98% of all cases the same field from our stored > documents, how can I boost retriving that information? > > The documentCache caches all the stored fields for a document and is not tunable to cache particular fields only. -- Regards, Shalin Shekhar Mangar.
