# Ignition Memory Usage

**URL:** <https://forum.inductiveautomation.com/t/ignition-memory-usage/64186>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [September 16, 2022, 4:26pm UTC](https://forum.inductiveautomation.com/t/ignition-memory-usage/64186 "2022-09-16T16:26:53Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 29, 2023, 12:20pm UTC](https://forum.inductiveautomation.com/t/ignition-memory-usage/64186/17 "2023-08-29T12:20:19Z")

</div>

The heap memory usage in a JVM is not categorized conveniently, so you need some knowledge of Ignition's architecture to dig around, but heap dumps (via `jmap` or `jcmd`) or heap monitoring (like in VisualVM) are the techniques to use.

There's a great deal of "noise" in a normal sawtooth pattern, so I usually use a multiple heap dumps over time, taken at the bottom of a sawtooth, to try to zero in on what is growing.

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-memory-usage/64186)._