I'm coming in late on this thread, but I want to recommend the YourKit Profiler product. It helped me track a performance problem similar to what you describe. I had been futzing with GC logging etc. for days before YourKit pinpointed the issue within minutes.
http://www.yourkit.com/ (My problem turned out to be silly. Straight Lucene, not Solr; the index was opened and closed on every request. It worked OK for a few hours, then a giant full GC kicked in, which froze the VM for minutes. Doh!) Anyway, it may help you identify how much memory is used per request, etc. and tune GC accordingly. Good luck! --Renaud -----Original Message----- From: Feak, Todd [mailto:todd.f...@smss.sony.com] Sent: Friday, January 23, 2009 8:13 AM To: solr-user@lucene.apache.org Subject: RE: Performance "dead-zone" due to garbage collection Can you share your experience with the IBM JDK once you've evaluated it? You are working with a heavy load, I think many would benefit from the feedback. -Todd Feak -----Original Message----- From: wojtekpia [mailto:wojte...@hotmail.com] Sent: Thursday, January 22, 2009 3:46 PM To: solr-user@lucene.apache.org Subject: Re: Performance "dead-zone" due to garbage collection I'm not sure if you suggested it, but I'd like to try the IBM JVM. Aside from setting my JRE paths, is there anything else I need to do run inside the IBM JVM? (e.g. re-compiling?) Walter Underwood wrote: > > What JVM and garbage collector setting? We are using the IBM JVM with > their concurrent generational collector. I would strongly recommend > trying a similar collector on your JVM. Hint: how much memory is in > use after a full GC? That is a good approximation to the working set. > > -- View this message in context: http://www.nabble.com/Performance-%22dead-zone%22-due-to-garbage-collect ion-tp21588427p21616078.html Sent from the Solr - User mailing list archive at Nabble.com.
