On Tue, Apr 15, 2014 at 2:00 PM, [email protected] < [email protected]> wrote:
> This is not Elasticsearch related. If you use a 40g heap of such extreme > size, you must expect that garbage collection must run for minutes, on > every JVM I know. > > Right, but it is actually advised to give elastic a lot of heap, right? The whole index is around 140G, so I would have thought that all frequently used parts should get loaded in memory, but it still starts running slow after a while. Any ideas? -- Wouter -- 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/CACXi6Xe_Q3xy8xZNo5QDqPpsJot8AknCYXfo5N9Vw2AyOfbVZA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
