The subscription page does not list the available amount of memory available for a node. There is also no metrics showing the amount of memory used. This would make it easier to foresee bottlenecks caused by high memory allocation. Also, the documentation could have some info on how the node will act when meeting its memory limit.
This is generally not information we want to expose as these are implementation specific and may change. The other resources like cpu and iops are similarly not exposed. We try to reduce the memory footprint as much as we can.Comment actions
This is mostly a concern when managing microservices. The Sesam system configuration allows custom allocation for memory assigned to the docker container. Without knowing how much memory a node can utilize or how much it is currently using, deployments and operations can be a challenge.
Please sign in to leave a comment.