This isn't a question that can be answered, really. We can tell you how much memory a particular version of ganesha uses on a particular machine under no load at startup, but the majority of memory used by Ganesha is used under load, so the amount of memory used depends entirely on the workload being run. You'll have to work that one out for each workload you care about. Daniel On 7/6/22 13:55, michael.mattsson@gmail.com wrote:
Hi, I have a use case where we need to run multiple instances of Ganesha on Kubernetes. To better understand our performance envelope and boundaries to plan the deployment better, I need to understand the lowest amount of memory Ganesha requires in theory to operate sufficiently without being reaped by the oom killer. Setting the limit extremely low, like in the hundred of megabytes, almost instantly kills Ganesha when applying pressure.
I'd appreciate any pointers or configuration options to consider.
Regards Michael _______________________________________________ Support mailing list -- support@lists.nfs-ganesha.org To unsubscribe send an email to support-leave@lists.nfs-ganesha.org