Hi, On Tue, Jul 23, 2013 at 8:02 AM, Erick Erickson <erickerick...@gmail.com> wrote: > Neil: > > Here's a must-read blog about why allocating more memory > to the JVM than Solr requires is a Bad Thing: > http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html > > It turns out that you actually do yourself harm by allocating more > memory to the JVM than it really needs. Of course the problem is > figuring out how much it "really needs", which if pretty tricky. > > Your long GC pauses _might_ be ameliorated by allocating _less_ > memory to the JVM, counterintuitive as that seems.
....or by using G1 :) See http://blog.sematext.com/2013/06/24/g1-cms-java-garbage-collector/ Otis -- Solr & ElasticSearch Support -- http://sematext.com/ Performance Monitoring -- http://sematext.com/spm > On Mon, Jul 22, 2013 at 5:05 PM, Neil Prosser <neil.pros...@gmail.com> wrote: >> I just have a little python script which I run with cron (luckily that's >> the granularity we have in Graphite). It reads the same JSON the admin UI >> displays and dumps numeric values into Graphite. >> >> I can open source it if you like. I just need to make sure I remove any >> hacks/shortcuts that I've taken because I'm working with our cluster! >> >> >> On 22 July 2013 19:26, Lance Norskog <goks...@gmail.com> wrote: >> >>> Are you feeding Graphite from Solr? If so, how? >>> >>> >>> On 07/19/2013 01:02 AM, Neil Prosser wrote: >>> >>>> That was overnight so I was unable to track exactly what happened (I'm >>>> going off our Graphite graphs here). >>>> >>> >>>
