Hello,
Looking for some general knowledge about naming, I read through this feed and I didn’t see my concern.
Looking at length of tag names and folder structure. Can having long names put a heavy load on the system and potentially lead to issues. (I have seen in the past where a script somewhere doesn’t fire or doesn’t execute properly, then it does; and I was wondering if it was too much going on by design of actions triggering other actions, in multiple layers)
Specific Example:
Such as, I added an expression to an alarm pipeline binding and during testing I noticed it took a few seconds to enter the pipeline vs with no expression binding it was immediate.
The example:
Alarm tag path:
GasWellSites/Gaia/Wells/1M/GPU2000/Alarms/MVT-2X50 Pressure/Alarm_Status
This Alarm_Status tag has 4 alarms that reference other tags in the UDT with long names like “Alarm_HiHi_Enabled” and “Alarm_HiHi_Notify_Enabled” for the alarms enabled bit and the Notification Pipeline binding:
Expression Binding:
if({[.]Alarm_HiHi_Notify_Enabled} = 1, “Alarm_Notification”, “”)
This system is relatively small, I think about 20k tags but this comes to mind as the size continuously grows.
My main question is, if I changed things to shorter names/tagpaths would it make a substantial difference in the end.
Ex: Sites/Gaia/W/1M/G2000/MV2X5P/AS
AHHE = Alarm_HiHi_Enabled
AHHNE = Alarm_HiHi_Notify_Enabled
AN = Alarm_Notification (Pipeline)
Expression:
if({[.]AHHNE} = 1, “AN”, “”)
