# Ignition performance issues

**URL:** <https://forum.inductiveautomation.com/t/ignition-performance-issues/66887>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [November 24, 2022, 1:36pm UTC](https://forum.inductiveautomation.com/t/ignition-performance-issues/66887 "2022-11-24T13:36:05Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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:** [November 30, 2022, 1:49pm UTC](https://forum.inductiveautomation.com/t/ignition-performance-issues/66887/9 "2022-11-30T13:49:03Z")

</div>

No more simple ideas. Set up Java Flight Recorder to run all of the time, and save on JVM exit. Set up a recurring OS task to run the Windows equivalent of `jcmd $(pgrep java) GC.heap_dump someFileName-$(date +%Y%m%d-%H%M).hprof` fairly often for later perusal with the flight recording.

You might want support to help you set this up.

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-performance-issues/66887)._