Hey there! We've found the following might help you get unblocked faster:

• 📚 Optimize Usage

• 🧵 Concerned about memory usage when server inactive

• 🧵 Disk Usage Wrongly Counted as Memory

If you find the answer from one of these, please let us know by solving the thread!

I am attaching the Memory metric graph and the enabled Go Garbage collection trace logs for your reference

bumping this up - incase anybody can help here!

I did some research on this and here is what I found:

Based on users report on minio's github repo on memory issues. I found that using GOMEMLIMIT env var can solve your memory issue.
Looking at your graph, your actual usage peaks around 6GB - 7GB. You don't need the full 32GB right now. I recommend setting GOMEMLIMIT to a value just above your normal daily peak. This forces the staircase leak to clean itself up once it hits that ceiling, keeping your bill reasonable.
You can set GOMEMLIMIT to 8192MiB (8GB). This way it gives you a safety buffer for spikes but forces Go to clean up garbage before it grows indefinitely.

You can read this github issue for more info.

Hope this helps.

But does it mean, my MinIO service cannot use more than 8GB when required?

Not exactly. GOMEMLIMIT is a trigger for cleaning, not a brick wall. It tells minio: once you hit 8GB, clean up your trash immediately.
If your service genuinely needs more than 8GB to process a massive request (like uploading a 50GB file), it will struggle or use more CPU to juggle the memory, but it won't instantly crash.

So, GOMEMLIMIT is a threshold for garbage collection (GC). When the used memory approaches this limit, a full GC will be triggered frequently.