In a production environment, having the caches enabled makes a lot of sense. And most definitely we will be enabling them. However, the primary idea of this exercise is to verify if limiting the number of facets will actually improve the performance.
An update on this. I did verify and looks like although I set indexed=false for most of the properties, I have not blocked them from participating in the query. I now enabled only 7 properties for faceting. Now at any given time only a maximum of 7 facets will participate in the query. Performance has now improved from an erstwhile 60 seconds to around 10 seconds. This really helped. Thanks a lot ! Regards Rahul On Fri, Jul 31, 2009 at 6:34 PM, Erik Hatcher <e...@ehatchersolutions.com>wrote: > > On Jul 31, 2009, at 7:17 AM, Rahul R wrote: > > Erik, >> I understand that caching is going to improve performance. Infact we did a >> PSR run with caches enabled and we got awesome results. But these wouldn't >> be really representative because the PSR scripts will be doing the same >> searches again and again. These would be cached and there would be >> virtually >> no evictions. This is not a practical case. >> > > I don't understand how this is not practical. Why wouldn't having the > caches warmed and filled with the facets be practical for your needs? > > Erik > >
