---
title: "Discussion on \"MinIO memory usage high on Kubernetes but never OOMKilled? Why the working set sits at 95% of the limit\" | Hashnode"
description: "Discussion on \"MinIO memory usage high on Kubernetes but never OOMKilled? Why the working set sits at 95% of the limit\". MinIO memory usage high on Kubernetes but never OOMKilled: MinIO sizes itself from 90% of the cgroup limit. How to check yours, and what 768Mi changed."
url: "https://hashnode.com/posts/minio-memory-usage-high-on-kubernetes-but-never-oomkilled-why-the-working-set-sits-at-95-of-the-limit/6af9d74c8ec34f077deeac84"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [MinIO memory usage high on Kubernetes but never OOMKilled? Why the working set sits at 95% of the limit](https://kkhdevs.hashnode.dev/minio-memory-usage-high-on-kubernetes-but-never-oomkilled-why-the-working-set-sits-at-95-of-the-limit?utm_source=hashnode&utm_medium=feed)

MinIO memory usage high on Kubernetes but never OOMKilled: MinIO sizes itself from 90% of the cgroup limit. How to check yours, and what 768Mi changed.

2d ago · 21 min read · kkhdevs.hashnode.dev  
Read the article

-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#memory](https://hashnode.com/tag/memory)
-   [#minio](https://hashnode.com/tag/minio)
-   [#sre](https://hashnode.com/tag/sre)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[KIM KYUNGHWAN](https://hashnode.com/@kkhdevs)

@kkhdevs

  
[View profile](https://hashnode.com/@kkhdevs)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
