# Memory Resources Exhausted raise conditions **URL:** \ **Category:** Open Q&A\ **Tags:** problem-detection, profiling-and-optimization\ **Created:** [August 26, 2021, 11:38am UTC](https://community.dynatrace.com/t/memory-resources-exhausted-raise-conditions/32516 "2021-08-26T11:38:13Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jcamps](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/jcamps/32/6791_2.png) [@jcamps](https://community.dynatrace.com/u/jcamps)\ **Post date:** [August 26, 2021, 11:38am UTC](https://community.dynatrace.com/t/memory-resources-exhausted-raise-conditions/32516/1 "2021-08-26T11:38:13Z")
Hi all, what are the exact conditions when Dynatrace raises the Memory Resources Exhausted problem for a process? Where can I view the conditions for every Dynatrace problem? Regards, Josep Maria ---
**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\ **Post date:** [August 26, 2021, 12:04pm UTC](https://community.dynatrace.com/t/memory-resources-exhausted-raise-conditions/32516/2 "2021-08-26T12:04:25Z")
You can view the resource exhaustion from the problem page or even at that particular hosts page. Memory health Host pages include two memory-related metrics for your hosts,  **Memory used**  and  **Page faults**. Both measurements and other factors, are used to correlate and calculate host high memory incidents. - **Memory used** Percentage of total RAM used by processes. RAM used by system caches and buffers isn’t included in this metric. Dynatrace calculates memory usage as: memory\_used = total\_memory\_size - (free\_memory + active\_memory + inactive\_memory + reclaimamble\_memory) - **Page faults** Number of major page faults per second. Major page faults involve loading a page from disk, thereby adding disk latency to the interrupted program’s execution. Virtualized hosts show additional measurements related to virtual machine memory usage. These metrics, along with other measurements, are used to detect memory saturation incidents. - **Memory compressed** The rate of memory compression or decompression. Virtual machine management platforms use memory compression to reduce memory usage. Memory compression saves memory but requires additional CPU cycles. Content that had been previously compressed must be decompressed before it can be used by a virtual machine. - **Memory swapped** Rate at which memory is swapped from disk into active memory, and vice-versa, from active memory to disk. ---
**Author:** ![jcamps](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/jcamps/32/6791_2.png) [@jcamps](https://community.dynatrace.com/u/jcamps)\ **Post date:** [August 26, 2021, 12:14pm UTC](https://community.dynatrace.com/t/memory-resources-exhausted-raise-conditions/32516/3 "2021-08-26T12:14:12Z")
Hi [@ChadTurner](https://community.dynatrace.com/user/14877) , I think your detailed explanation is related to “ **Memory saturation** ” (host problem) but not to “ **Memory Resources Exhausted** ” (process problem), it’s possible? Regards, Josep Maria ---
**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\ **Post date:** [August 26, 2021, 12:26pm UTC](https://community.dynatrace.com/t/memory-resources-exhausted-raise-conditions/32516/4 "2021-08-26T12:26:10Z")
Exhausted Memory can happen at both levels. if a Host has 50 GB of memory and a process or processes use up all 50 GB then an alert will be raised at the host level stating that Memory is exhausted on Host X. If you have a process say Java that is allocated to use 3 GB of memory, and that processes uses all of the 3 GB it is allowed/allocated to use then yes an exhaustion alert will be raised and more likely even crash which would then be in the collected crash logs. Meanwhile the host is running fine at 10 GB memory consumed with 40 GB still free. Exhaustion can happen at all levels. ---
**Author:** ![jcamps](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/jcamps/32/6791_2.png) [@jcamps](https://community.dynatrace.com/u/jcamps)\ **Post date:** [August 26, 2021, 1:09pm UTC](https://community.dynatrace.com/t/memory-resources-exhausted-raise-conditions/32516/5 "2021-08-26T13:09:31Z")
Thanks! But what are the exact conditions checked by Dynartace in order to trigger the “ **Memory Resources Exhausted** ” problem for a Java process? Regards! Josep Maria ---
**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\ **Post date:** [August 26, 2021, 1:23pm UTC](https://community.dynatrace.com/t/memory-resources-exhausted-raise-conditions/32516/6 "2021-08-26T13:23:47Z")
The check would be basically How much Memory is being used, vs how much is allowed. Much like 6 GB being used - 8 GB allowed = 2 GB remaining. or 6 GB used - 6 GB allowed = Memory Exhausted.