On Thu, Dec 4, 2008 at 2:28 PM, wojtekpia <[EMAIL PROTECTED]> wrote: > I'm seeing some strange behavior with my garbage collector that disappears > when I turn off this optimization.
I just changed the new faceting code to use a solr cache. Look for the "fieldValueCache" on the statistics page now. It just occurred to me that there is a big difference in how memory is used with facet.method=fc. Since we traverse documents and count up terms, we need to allocate an int[nTerms] to accumulate those counts. This can be a big chunk of memory per-request, and is most likely what changed your GC profile (i.e. changing the GC settings may help). -Yonik > I'm running load tests on my deployment. > For the first few minutes, everything is fine (and this patch does make > things faster - I haven't quantified the improvement yet). After that, the > garbage collector stops collecting. Specifically, the new generation part of > the heap is full, but never garbage collected, and the old generation is > emptied, then never gets anything more. This throttles Solr performance > (average response times that used to be ~500ms are now ~25s). > > I described my deployment scenario in an earlier post: > http://www.nabble.com/Throughput-Optimization-td20335132.html > > Does it sound like the new faceting algorithm could be the culprit? > > > wojtekpia wrote: >> >> Definitely, but it'll take me a few days. I'll also report findings on >> SOLR-465. (I've been on holiday for a few weeks) >> >> >> Noble Paul നോബിള് नोब्ळ् wrote: >>> >>> wojtek, you can report back the numbers if possible >>> >>> It would be nice to know how the new impl performs in real-world >>> >>> >>> >> >> > > -- > View this message in context: > http://www.nabble.com/new-faceting-algorithm-tp20674902p20840622.html > Sent from the Solr - User mailing list archive at Nabble.com. > >
