It’s not a setting I’ve played with at all. I understand the gist of it though, essentially it’ll let you automatically adjust your JVM size relative to whatever you allocated to the cgroup. Unfortunately I’m not a K8s developer (that may change shortly, but atm the case). What you need to a firm handle on yourself is where does the memory for the O/S file cache live, and is that size sufficient for your read/write activity. Bare metal and VM tuning I understand better, so I’ll have to defer to others who may have specific personal experience with the details, but the essence of the issue should remain the same. You want a file cache that functions appropriately or you’ll get excessive stalls happening on either reading from disk or flushing dirty pages to disk.
From: Ben Mills <b...@bitbrew.com> Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org> Date: Monday, November 4, 2019 at 12:14 PM To: "user@cassandra.apache.org" <user@cassandra.apache.org> Subject: Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC CGroup
