# Zulu process consuming too much CPU

**URL:** <https://forum.inductiveautomation.com/t/zulu-process-consuming-too-much-cpu/90087>\
**Category:** Ignition\
**Created:** [May 8, 2024, 10:33am UTC](https://forum.inductiveautomation.com/t/zulu-process-consuming-too-much-cpu/90087 "2024-05-08T10:33:48Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [May 8, 2024, 1:05pm UTC](https://forum.inductiveautomation.com/t/zulu-process-consuming-too-much-cpu/90087/3 "2024-05-08T13:05:36Z")

</div>

A "healthy" quantity of RAM for Ignition yields a sawtooth pattern on the gateway's memory trend (gateway status =\> Performance) where the regular drop-offs end up somewhat below 50% and the GC event at each peak, typically around 90%, doesn't create a "Clock Drift" warning.

If your trend already looks like this, or better, then more RAM will **not** help your CPU utilization. If your memory trend is not dropping below 50% after the large peaks, then you **might** be helped by more RAM.

Show a screenshot of your Performance page.

Also, if your gateway is running anything other than Ignition (like your DB), you should migrate those services to other hardware.

---

_[View the full topic](https://forum.inductiveautomation.com/t/zulu-process-consuming-too-much-cpu/90087)._