# Heavy CPU and RAM Usage

**URL:** <https://forum.inductiveautomation.com/t/heavy-cpu-and-ram-usage/16202>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [December 4, 2017, 8:43am UTC](https://forum.inductiveautomation.com/t/heavy-cpu-and-ram-usage/16202 "2017-12-04T08:43:57Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [December 7, 2017, 1:35pm UTC](https://forum.inductiveautomation.com/t/heavy-cpu-and-ram-usage/16202/6 "2017-12-07T13:35:34Z")

</div>

Also make sure that everything that can run on the gateway is set up with memory limits so the total is less than the physical memory. If you a running a little gateway with 4G of ram, and you give Ignition 2G, you can’t allow anything else to use more than about ~1G (like any client), or you’ll push the gateway into swap, which will then thrash.  
Also consider configuring your gateway with the G1GC garbage collector, as [described here](http://forum.inductiveautomation.com/t/gateway-java-question-7-7-2/10402/3). In my experience, not only does latency improve, but the gateway’s average memory utilization drops.

---

_[View the full topic](https://forum.inductiveautomation.com/t/heavy-cpu-and-ram-usage/16202)._