# Status \> Connections \> Devices \> Overload 500% **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [September 26, 2023, 10:00am UTC](https://forum.inductiveautomation.com/t/status-connections-devices-overload-500/79631 "2023-09-26T10:00:15Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Miguel\_Cimildoro](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@Miguel\_Cimildoro](https://forum.inductiveautomation.com/u/Miguel_Cimildoro)\ **Post date:** [September 26, 2023, 10:00am UTC](https://forum.inductiveautomation.com/t/status-connections-devices-overload-500/79631/1 "2023-09-26T10:00:15Z")
I have a situation where an opc ua devices is overloaded with 500%. the configuration is a Modbus TCP with a Communication Timeout of 120000 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/b/2b0bd951afec5f256a9dc003eaffc50c8e1f6e2b.png) every time the overload reaches 600%++ (2-3min) I get a bad\_failure on some tags (not all) I find it strange that it is only on some of them that's why I have this question... why only on those? . also have you checked that there are no scripts associated with those tags. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/5/85f4aead68b760c9bb9f6e76862c020f917386c9.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/8/0866d91c26cb393b36c93ca8aa36848934fc326d.png) Do you know what causes this behavior? regards. ---
**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:** [September 26, 2023, 3:10pm UTC](https://forum.inductiveautomation.com/t/status-connections-devices-overload-500/79631/2 "2023-09-26T15:10:54Z")
Look at your mean response time. That is typical when a true serial modbus link is behind your target device and is running at 9600 baud or 19200. You simply cannot read that much data at the desired pace. Prune your data. ---
**Author:** ![Miguel\_Cimildoro](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@Miguel\_Cimildoro](https://forum.inductiveautomation.com/u/Miguel_Cimildoro)\ **Post date:** [September 26, 2023, 3:38pm UTC](https://forum.inductiveautomation.com/t/status-connections-devices-overload-500/79631/3 "2023-09-26T15:38:38Z")
hi Phil, did you mean lowering the response time a bit? ---
**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:** [September 26, 2023, 3:43pm UTC](https://forum.inductiveautomation.com/t/status-connections-devices-overload-500/79631/4 "2023-09-26T15:43:23Z")
No, I meant choosing what data you can live with **not having** in Ignition. You are using a protocol, that, when actually running on serial circuits, is **extremely** low bandwidth. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [September 26, 2023, 4:20pm UTC](https://forum.inductiveautomation.com/t/status-connections-devices-overload-500/79631/5 "2023-09-26T16:20:39Z")
He's saying it's Modbus TCP (At least hopefully that's the case and that the device named MRTU means Modbus Roof Top Unit since it's HVAC and not Modbus RTU). Either way, it's definitely something that needs more optimization. I just had to do some similar cleanup on an Allen Bradley project where everything was being polled all the time when most of the data wasn't used except on faceplate. Once I changed those over to leased tags with 0 for the normal "rate", it stopped polling tags it really didn't need and went from 400-500% overloaded to 0-1%. ---
**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:** [September 26, 2023, 8:20pm UTC](https://forum.inductiveautomation.com/t/status-connections-devices-overload-500/79631/6 "2023-09-26T20:20:42Z")
> [@michael.flagler](#): > > He's saying it's Modbus TCP Yes, but many Modbus TCP devices are really just front ends tacked onto an older Modbus RTU interface. And therefore run at RTU speeds (1ms per byte or two). Just like the OP's response times. ---
**Author:** ![Miguel\_Cimildoro](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@Miguel\_Cimildoro](https://forum.inductiveautomation.com/u/Miguel_Cimildoro)\ **Post date:** [September 27, 2023, 7:34am UTC](https://forum.inductiveautomation.com/t/status-connections-devices-overload-500/79631/7 "2023-09-27T07:34:52Z")
> [@michael.flagler](#): > > I just had to do some similar cleanup on an Allen Bradley project where everything was being polled all the time when most of the data wasn't used except on faceplate. Once I changed those over to leased tags with 0 for the normal "rate", it stopped polling tags it really didn't need and went from 400-500% overloaded to 0-1%. it might make some sense with what I am trying to solve because most of the tags are associated to a tag group (with the configuration I will show in the next image) where clearly they will not be used unless the user interacts with them, while they will be on standby which I think is the point you are referring to with no data wasn't used except on faceplate. in this case, what you are proposing is to switch the Direct mode to Leased? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/5/45e74f6ecfbf3fcc520487cd90df19d7d469f2be.png) ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [September 27, 2023, 1:48pm UTC](https://forum.inductiveautomation.com/t/status-connections-devices-overload-500/79631/8 "2023-09-27T13:48:24Z")
I dropped mine down to leased with a 0 Rate so they're not polled at all normally, but with an appropriate rate for when the values are displayed/leased (this is up to your use case).