# Performance issues with Tag Change Script + DB Insert + Many Threads Waiting

**URL:** <https://forum.inductiveautomation.com/t/performance-issues-with-tag-change-script-db-insert-many-threads-waiting/109778>\
**Category:** Ignition\
**Created:** [August 14, 2025, 4:20pm UTC](https://forum.inductiveautomation.com/t/performance-issues-with-tag-change-script-db-insert-many-threads-waiting/109778 "2025-08-14T16:20:01Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\
**Post date:** [August 14, 2025, 6:09pm UTC](https://forum.inductiveautomation.com/t/performance-issues-with-tag-change-script-db-insert-many-threads-waiting/109778/15 "2025-08-14T18:09:14Z")

</div>

Since this is in a UDT, sometimes Gateway Tag Change Sripts aren’t easily resused.

Consider this thread and the queue @pturmel has: [Java concurrent queue for tag change scripts](https://forum.inductiveautomation.com/t/java-concurrent-queue-for-tag-change-scripts/82044)

Basically you still have the tag change script in the UDT. It would stash a tag path or such into the queue, and then you have a timer script running that drains the queue, doing something with the previous data you stashed.

---

_[View the full topic](https://forum.inductiveautomation.com/t/performance-issues-with-tag-change-script-db-insert-many-threads-waiting/109778)._