<p>I'm checking on a scaling issue and we are suspecting it has something to do with the memory, but after running a load testing on local machine it doesn't seems to have memory leak.
We are hosting the .net core application in Kubernetes, with resources setting 800mi request memory without limit.
And as per describe from this <a href="https://www.c-sharpcorner.com/article/garbage-collection-in-dot-net/#:%7E:text=The%20trigger%20for%20Garbage%20collection,GC." rel="nofollow noreferrer">Article</a></p>
<blockquote>
<p>The trigger for Garbage collection occurs when, The system has low
physical memory and gets notification from OS.</p>
</blockquote>
<p>So does that mean GC is unlikely to kick in until my nodes are low on memory if we did not setup memory limit, and it will eventually occupied most of memory in node?</p>

<p>Yes that's exactly what can happen, both with .NET and other pods.</p>
<p>Always set memory and CPU limits as this may have impact on other pods or  <a href="https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/" rel="nofollow noreferrer">Configure Default Memory Requests and Limits for a Namespace</a></p>
