Effect of Orphaned Device/Tags on System Performance

I have an entire folder of tags that were connected to a device that is no longer on the network. Of course, I could just delete the entire folder. However, we've taken over this system from another integrator, which makes me a little hesitant to do so.

For now the device is still configured, just not connected.

What are the performance implications, if any, of

  1. Leaving the device configured, even though it will never be connected.
  2. Leaving the tags on the gateway, even though all of them have a configuration error due to the device being disconnected.

Just disable them all?
Or..
If they will never be used, I would just export the tags to xml or json, document where the file is stored and then delete them.

1 Like

If I could quickly disable them at the top-level folder, sure I'd do that.

I also considered exporting them. I think I'll do that and store it with the GWBK.

How do I export just one folder? Just right-click the folder and export from there. (It would be nice if there was some indication of exactly what you were exporting)

Is there a way to export the tags and include any UDTs that would be required to define them when imported?

Just do a full UDT tag folder export as well?
it will be small files, not a big deal.

It will export any tags in the underlying selected folder, if any overrides are on them it will export those, if not overriden it will leave those parameters blank.

I would just disable the device connection. The config errors are pretty static, and very low overhead.

1 Like