Hi, 5GB heap sounds quite big, let along the 8 GB heap. I would try simple stuff like jmap to see what's eating the memory, and if that doesn't work I'd try using a profiler.
Turn off norms if you don't need them, and either use trie-based fields for date if you have them and sort by them, or round those dates up. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: CameronL <cameron.develo...@gmail.com> > To: solr-user@lucene.apache.org > Sent: Wednesday, July 1, 2009 4:43:11 PM > Subject: Re: Plugin Performance Issues > > > Our max heap was configured to use 5GB. It has been running fine until we > tried to deploy a new queryConverter for our SpellcheckComponent. After > which, we upped our heap to 8GB and still had issues. > > Solr is the only webapp running on Tomcat. > > We are using sorting and faceting, but again, hadn't had problems until > deploying this plugin. Also, seeing as how it's only spellchecking related > (and we have a separate RequestHandler that only handles spellchecking, > while leaving the SpellcheckComponent out of our standard RequestHandler), > I'm not entirely convinced that it's related to our code, but it could be. > Just trying to get a sense if other plugins have had similar problems, just > by the nature of using Solr's resource loading from the /lib directory. > > > Otis Gospodnetic wrote: > > > > > > Hi, > > > > Could it simply be the case that you really do need all that memory that > > the JVM start consuming with time? How large of a heap are you using, is > > Solr the only webapp in your TOmcat, and are you using sorting or > > faceting? > > > > Otis > > -- > > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch > > > > > > > > ----- Original Message ---- > >> From: CameronL > >> To: solr-user@lucene.apache.org > >> Sent: Wednesday, July 1, 2009 2:37:40 PM > >> Subject: Plugin Performance Issues > >> > >> > >> We recently created a custom class for our spellchecking implementation > >> in > >> Solr. We decided to include the class in a custom jar and deployed it to > >> the /lib directory in solr_home to use it as a plugin. > >> > >> After a while (about 12 hours), the heap usage for Solr slowly starts to > >> rise, and we eventually run into swap issues which ends up killing our > >> performance. We've tried several different things to try to solve the > >> problem, originally thinking it was our code, but on one of our servers, > >> the > >> new code in the plugin wasn't even being used. > >> > >> Has anyone else experienced? I'm wondering if this is perhaps a > >> side-effect > >> of using plugins in general, perhaps something going on with the custom > >> class loading of Solr. > >> > >> We're using Tomcat 6 and Solr 1.3 by the way. > >> -- > >> View this message in context: > >> http://www.nabble.com/Plugin-Performance-Issues-tp24295010p24295010.html > >> Sent from the Solr - User mailing list archive at Nabble.com. > > > > > > > > -- > View this message in context: > http://www.nabble.com/Plugin-Performance-Issues-tp24295010p24296828.html > Sent from the Solr - User mailing list archive at Nabble.com.
