Thanks, Chris. I will test with vanilla Solr to clarify whether the problem occurs with it, or only in the version where we have made changes.
-Graham > : To tweak our scoring, a custom hit collector in > SolrIndexSearcher creates 1 > : fieldCache and 3 ValueSources from 3 fields: > : - an integer field with many unique values (order 10^4) > : - another integer field with many unique values (order 10^4) > : - an integer field with hundreds of unique values > > so you customized SolrIndexSearcher? ... is it possible you > have a memory leak in that code? > > If you have all of your cache sizes set to zero, you should > be able to start up the server, hit it with a bunch of > queries, then trigger a commit and see your heap usage drop > significantly. ... if you do that over and over again and see > the heap usage grow and grow, there may be something else > going on in those changes of yours.