Hi Mark, Thanks for your reply!
Op donderdag 31 juli 2014 12:16:36 UTC+2 schreef Mark Walkom: > > A lot of the answers for performance and capacity are "it depends". > Well, I'm currently not that worried about performance, as long as it can keep up with the amount of data we throw at it. It's currently 800 messages/s at peak times, but we expect to grow to about 2000. Beyond that, as long as searches do not time out, I'd be happy. I'm much more worried about stability at the moment, hence my question regarding if I should be worried about the memory usage I'm seeing. > You'll get *much* better performance from Oracle java, 1.7u55 is current > recommended. Given you're "experimenting" with GCG1 (which isn't current > best practise, hence experimenting), you might even want to try Java 1.8. > Ok, will try the Oracle JRE. Regarding G1 being experimental, I assume you mean from ES' POV, right? Because from what I read, it's fully supported in Java 7. I didn't find any other way to solve the 'stop the world' gc the CMS ran into every few hours :S I'm not a Java dev, however, just wanted something that didn't crash once a day. > If you want to drop memory use you can disable bloom filtering. > > Done and that did indeed help a little. -- Kind regards, Tim Stoop -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/df14168b-3615-450e-9a8f-4360c811d7d0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
