Yeah, I sent a note to the web folks there about the images..... I'll leave the rest to people who really _understand_ all that stuff....
On Thu, Sep 20, 2012 at 8:31 AM, Bernd Fehling <bernd.fehl...@uni-bielefeld.de> wrote: > Hi Erik, > > thanks for the link. > Now if we could see the images in that article that would be great :-) > > > By the way, one cause for the memory jumps was located as "killer search" > from a user. > The interesting part is that the verbose gc.log showed a "hiccup" in the GC. > Which means that during a GC run right after CMS-concurrent-sweep-start but > before > CMS-concurrent-sweep there is a new GC launched which interferes with the > running one. > Any switches for this to serialize GC? > > > Regards > Bernd > > > Am 20.09.2012 13:51, schrieb Erick Erickson: >> Here's a wonderful writeup about GC and memory in Solr/Lucene: >> >> http://searchhub.org/dev/2011/03/27/garbage-collection-bootcamp-1-0/ >> >> Best >> Erick >> >> On Thu, Sep 20, 2012 at 5:49 AM, Robert Muir <rcm...@gmail.com> wrote: >>> On Thu, Sep 20, 2012 at 3:09 AM, Bernd Fehling >>> <bernd.fehl...@uni-bielefeld.de> wrote: >>> >>>> By the way while looking for upgrading to JDK7, the release notes say >>>> under section >>>> "known issues" about the "PorterStemmer" bug: >>>> "...The recommended workaround is to specify -XX:-UseLoopPredicate on the >>>> command line." >>>> Is this still not fixed, or won't fix? >>> >>> How in the world can we fix it? >>> >>> Oracle released a broken java version: there's nothing we can do about >>> that. Go take it up with them. >>> >>> -- >>> lucidworks.com
