# Tag Limitations

**URL:** <https://forum.inductiveautomation.com/t/tag-limitations/18196>\
**Category:** Ignition\
**Created:** [May 29, 2018, 11:35am UTC](https://forum.inductiveautomation.com/t/tag-limitations/18196 "2018-05-29T11:35:24Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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 29, 2018, 12:02pm UTC](https://forum.inductiveautomation.com/t/tag-limitations/18196/5 "2018-05-29T12:02:40Z")

</div>

And have you customized your `ignition.conf` file for performance? Something like this:

> [@Gateway / Java question 7.7.2](http://forum.inductiveautomation.com/t/gateway-java-question-7-7-2/10402/2):
>
> It is normal for Ignition (and java in general) to cycle between low and high memory usage. In a nutshell, java will defer difficult garbage collection tasks until memory pressure makes it necessary. If there is a great deal of garbage objects when that happens, java will stall briefly while it frees memory. If you have tweaked anything else on your system, you are probably still running what is called the Concurrent-Mark-Sweep garbage collection algorithm (standard for java7). A new garbage…

---

_[View the full topic](https://forum.inductiveautomation.com/t/tag-limitations/18196)._