JVM heap tuning for percolators

I've read in the docs that one shouldn't set the JVM's heap size over 50% of the physical memory, as ES needs to leave enough memory for filesystem caches and other things.

But, given percolators don't index data into files, but they do mainly in-memory manipulations, should we still respect this 50% limit?

The question arises as we're using machines with 32GB of RAM, of which we're leaving 16GB to the OS but I've seen that 13GB are usually listed as available (with only 2GB being used for buff/cache).

So, I wonder if I can use a part of that available memory for the percolator, as we're running into memory bottlenecks with some heavy percolator queries and high volumes of data.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.