# Leased Tag - Need slower OPC UA Subscription Interval when lease is inactive **URL:** \ **Category:** Ignition\ **Tags:** opcua\ **Created:** [November 27, 2024, 3:21pm UTC](https://forum.inductiveautomation.com/t/leased-tag-need-slower-opc-ua-subscription-interval-when-lease-is-inactive/99184 "2024-11-27T15:21:21Z")\ **Posts on this page:** 1\ **Showing post:** 24
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [November 30, 2024, 7:16am UTC](https://forum.inductiveautomation.com/t/leased-tag-need-slower-opc-ua-subscription-interval-when-lease-is-inactive/99184/24 "2024-11-30T07:16:42Z")
To avoid good overload, you can adjust the cpu ressource (50 percent max) dedicated to communications. > [@Historian DB Hammering Tags](https://forum.inductiveautomation.com/t/historian-db-hammering-tags/91699): > > Hi all, I'm having an issue that despite being set to 'On Change' and the value of a tag seeminly not changing, its HAMMERING storing the same value in the database. Multiply this by 70000 tags and Houston, we have a problem! The tag is part of a UDT. There are 3 OPC tags under sources... and these are then read by the Derived tags via jsonGet / jsonSet. The tag we're going to look at is Q\_AH, part of the OUT source. Its a discrete tag that is either true or false. I have set the config as … --- _[View the full topic](https://forum.inductiveautomation.com/t/leased-tag-need-slower-opc-ua-subscription-interval-when-lease-is-inactive/99184)._