Hi all, I know there have been many posts about this already and I have done my best to read through them but one lingering question remains. When doing performance testing on a Solr instance (under normal production like circumstances, not the ones where commits are happening more frequently than necessary), is there any value in performance testing against a server with caches *disabled* with a profiler hooked up to see where queries in the absence of a cache are spending the most time?
The reason I am asking this is to tune things like field types, using tint vs regular int, different precision steps etc. Or maybe sorting is taking a long time and the profiler shows an inordinate amount of time spent there etc. so either we find a different way to solve that particular problem. Perhaps we are faceting on something bad etc. Then we can optimize those to at least not be as slow and then ensure that caching is tuned properly so that cache misses don't yield these expensive spikes. I'm trying to devise a proper performance testing for any new features/config changes and wanted to get some feedback on whether or not this approach makes sense. Of course performance testing against a typical production setup *with* caching will also be done to make sure things behave as expected. Thanks! Amit
