# Gateway Performance Issues and Tuning

**URL:** <https://forum.inductiveautomation.com/t/gateway-performance-issues-and-tuning/67109>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [November 30, 2022, 8:27pm UTC](https://forum.inductiveautomation.com/t/gateway-performance-issues-and-tuning/67109 "2022-11-30T20:27:05Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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, 8:36pm UTC](https://forum.inductiveautomation.com/t/gateway-performance-issues-and-tuning/67109/2 "2022-11-30T20:36:29Z")

</div>

Bit of an odd memory usage pattern. Typical is a sawtooth. A healthy sawtooth tends to ramp from 40%-ish (or less) to 80%-ish, then GC knocks it back down.

Except. Long time spans for requested graphs, especially in the reporting module, randomly spike memory. A couple or more such requests together could push a server over the edge. Perspective also loads a server much more than Vision, so a bunch of busy clients can do similar.

Consider this similar topic:

> [@Ignition performance issues](https://forum.inductiveautomation.com/t/ignition-performance-issues/66887/9):
>
> 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.

Maybe also set up GC detail logging in ignition.conf. See how long your pauses usually are.

---

_[View the full topic](https://forum.inductiveautomation.com/t/gateway-performance-issues-and-tuning/67109)._