# Gateway module resources

**URL:** <https://forum.inductiveautomation.com/t/gateway-module-resources/113606>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [January 28, 2026, 4:39pm UTC](https://forum.inductiveautomation.com/t/gateway-module-resources/113606 "2026-01-28T16:39:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gregoryh](https://avatars.discourse-cdn.com/v4/letter/g/848f3c/32.png) [@gregoryh](https://forum.inductiveautomation.com/u/gregoryh)\
**Post date:** [January 28, 2026, 4:39pm UTC](https://forum.inductiveautomation.com/t/gateway-module-resources/113606/1 "2026-01-28T16:39:16Z")

</div>

I am curious about the implact on the gateway on a few modules that are in trial mode. From various searches I have come up with that when the 2 hour timer expires, cpu use stops on the module but continues to be loaded in Ram. Is this correct? Can the resources be seen somewhere?

---

<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:** [January 28, 2026, 4:41pm UTC](https://forum.inductiveautomation.com/t/gateway-module-resources/113606/2 "2026-01-28T16:41:29Z")

</div>

> [@gregoryh](#):
>
> cpu use stops on the module

No, reaction to trial mode expiring is entirely up to the module author.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [January 28, 2026, 4:52pm UTC](https://forum.inductiveautomation.com/t/gateway-module-resources/113606/3 "2026-01-28T16:52:10Z")

</div>

The processor and memory usage of an installed module is negligible unless you're on an _extremely_ resource constrained system. The first "thing" you configure that module to do is almost certainly going to have far more impact than the minimal impact of the module itself.

If you're in such a resource constrained system that you can't afford the few megabytes of RAM, you are not going to have a good time deploying Ignition - it is generally memory hungry.