title: Expected behavior when Private Memory Limit in IIS exceeds machine RAM
body: <p>So I have a couple of questions re: Private Memory Limit in IIS using a C# web app.</p>
  <p>When we set the Private Memory Limit to 0, per the docs <a href="https://technet.microsoft.com/en-us/library/cc745955.aspx" rel="nofollow noreferrer">here</a> it should have no limit.  However we saw behavior that the app would trigger an IIS reset when reaching approximately 60% of the machine RAM which seems counter intuitive.  Does this grok?</p>
  <p>The second issue is expected behavior when the Private Memory Limit is set to a value that exceeds the amount of RAM available on the machine.  A co-worker solved the above problem by setting the Private Memory Limit above the system memory and it did perform well.  However this seems like it could have ramifications about proper GC times.</p>
  <p>For example if the system RAM is 32 GB and the memory limit is set to 35, will it not trigger Gargbage Collection when it gets close to 32 because it THINKS it can get to 35?  Or are we guaranteed a garbage collection will happen before then?</p>
  <p>Additionally this requires a config change if you ever change the size of the machine (we are an AWS shop so this can happen at a relatively high frequency).</p>