# 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:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![BHASKAR](https://avatars.discourse-cdn.com/v4/letter/b/f4b2a3/32.png) [@BHASKAR](https://forum.inductiveautomation.com/u/BHASKAR)\
**Post date:** [May 29, 2018, 11:35am UTC](https://forum.inductiveautomation.com/t/tag-limitations/18196/1 "2018-05-29T11:35:24Z")

</div>

Hi  
Is the response of the Ignition SCADA becomes slower, if I increase the tags eg: 15k to 90k. I am using Ignition latest version with POSTGRESQL on Ubuntu 16.04 server OS???

---

<div class="post-metadata">

**Author:** ![BHASKAR](https://avatars.discourse-cdn.com/v4/letter/b/f4b2a3/32.png) [@BHASKAR](https://forum.inductiveautomation.com/u/BHASKAR)\
**Post date:** [May 29, 2018, 11:36am UTC](https://forum.inductiveautomation.com/t/tag-limitations/18196/2 "2018-05-29T11:36:43Z")

</div>

Especially while updating data in history charts of previous days…

---

<div class="post-metadata">

**Author:** ![BHASKAR](https://avatars.discourse-cdn.com/v4/letter/b/f4b2a3/32.png) [@BHASKAR](https://forum.inductiveautomation.com/u/BHASKAR)\
**Post date:** [May 29, 2018, 11:38am UTC](https://forum.inductiveautomation.com/t/tag-limitations/18196/3 "2018-05-29T11:38:38Z")

</div>

With same SCADA &d atabase if I reduce the tags by disconnecting/disabling devices, I could able to get good response…

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [May 29, 2018, 11:52am UTC](https://forum.inductiveautomation.com/t/tag-limitations/18196/4 "2018-05-29T11:52:56Z")

</div>

For completeness, what are your server specs?

---

<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…