Containerd memory usage in Cost tab about coroot HOT 4 CLOSED

I can't agree with you.
For example, a Postgres server uses 32GB of page cache. While it is true that this memory can be reclaimed when needed, having such a cache is critical for database performance. Without it, query times would increase due to disk access.
In this case, it is better to assume that this process is utilizing this amount of memory. Otherwise, if you don't take this into account when optimizing, it can negatively impact its performance.

from coroot.

Actually, from my perspective, you partly agreed (partly not) with me, so I'll move on with my ideas to improve that page :)

I had another 2 point to support my point of view:

1. On this diagrams we correspond used vs requested. Where K8s don't care about how much memory is cached, OOM can occur only if all memory is used/container used more memory than limit. So how much memory is cached doesn't matter in the context of k8s behavior and distribution of the workload.
2. You give example of Postgresql, when i will deploy Postgresql on k8s. Still on that diagram i will have containerd memory use, not Postgresql container.

But if we still remain in the position that the display of the cached memory is correct, then I suggest:

• Let's not call it containerd / dockerd. Let's call it "cached" and give it some dark gray color or something like beige(#F5F5DC). On the other hand we can change "others" to dark gray, and give "cached" a light gray.

Best regards,

from coroot.

You've convinced me! :)

I really like your suggestion of having a separate element that reflects the size of page cache. This eliminates any potential misconception that this memory is "idle".

We'll fix this soon.

Thank you!

from coroot.

This is fixed in Coroot v0.17.10

from coroot.