# High CPU usage on 1756-ENBT

**URL:** <https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363>\
**Category:** Ignition\
**Created:** [August 26, 2021, 10:51pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363 "2021-08-26T22:51:00Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\
**Post date:** [August 26, 2021, 10:51pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/1 "2021-08-26T22:51:00Z")

</div>

Has anyone experienced an issue with ignition and the 1756 ENBT having 100% CPU usage? I have a system with 50,000 tags polling once per second for everything, and the ENBT is at 100%. I tried changing the poll rate to 10,000 ms and still have the same result. A test with wireshark between the card and ignition produced about 1000 packets per second.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 26, 2021, 10:52pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/2 "2021-08-26T22:52:52Z")

</div>

What version of Ignition are you using? Can you share a screenshot of the diagnostics page for that device?

---

<div class="post-metadata">

**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\
**Post date:** [August 26, 2021, 10:54pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/3 "2021-08-26T22:54:21Z")

</div>

8.1.9. I will try to get a screenshot but it has some trouble loading with the usage.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 26, 2021, 10:55pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/4 "2021-08-26T22:55:04Z")

</div>

Okay, I meant the one in Ignition under Status \> Connections \> Devices, but actually one from the ENBT itself would also be good.

Also - what driver are you using and what firmware version is the PLC?

---

<div class="post-metadata">

**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\
**Post date:** [August 26, 2021, 11:01pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/5 "2021-08-26T23:01:50Z")

</div>

Allen Bradley Logix 21+. Processor is an L72 running firmware version 32.011.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/3/e39eaa68a631bded7404f1c3d980cd6df1b54bcc.png)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 26, 2021, 11:03pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/6 "2021-08-26T23:03:53Z")

</div>

That’s not 50,000 tags… right PLC, wrong system, or what?

---

<div class="post-metadata">

**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\
**Post date:** [August 26, 2021, 11:07pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/7 "2021-08-26T23:07:04Z")

</div>

This is a test system, we only have 2 of the 7 total PLCs connected. The rest of the device connections are disabled.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 26, 2021, 11:07pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/8 "2021-08-26T23:07:31Z")

</div>

So did your original post mean 50,000 tags across 7 devices all going through the same ENBT?

---

<div class="post-metadata">

**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\
**Post date:** [August 26, 2021, 11:10pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/9 "2021-08-26T23:10:54Z")

</div>

They are all separate ethernet cards on the live system. The number of tags is still considerable though for the currently connected test PLC.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 26, 2021, 11:13pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/10 "2021-08-26T23:13:06Z")

</div>

So do all the ENBTs on the live system have 100% cpu? Does this test ENBT have 100% cpu?

---

<div class="post-metadata">

**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\
**Post date:** [August 26, 2021, 11:14pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/11 "2021-08-26T23:14:25Z")

</div>

Yes, both the live system and test are at 100% CPU.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/a/6a249696fa1d8a8849a8e0dc4328fe2dd56e789c.png)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 26, 2021, 11:16pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/12 "2021-08-26T23:16:07Z")

</div>

Well, the at least for the test system, the Ignition-side diagnostics are as good as it gets. Your 5000 tags are updating totally on time.

Those stats say you have 2 TCP connections and 4 MSG connections - what else is connected besides Ignition? Or do you have 2 device connections going through it?

---

<div class="post-metadata">

**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\
**Post date:** [August 26, 2021, 11:18pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/13 "2021-08-26T23:18:45Z")

</div>

yes there is 2 device connections through it. I have already tried disabling the other connection but the result is the same. For context, this is an upgrade to a citect system which had about 8000 tags total, except it made heavy use of bit addressing to save on the point count, so my system is at 50000 as it is referencing the booleans directly.

---

<div class="post-metadata">

**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\
**Post date:** [August 26, 2021, 11:19pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/14 "2021-08-26T23:19:30Z")

</div>

Sorry, I forgot to attach the other device screenshot

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/f/1f721945a5f14f29cdef6a87d22bcb236396d58c.png)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 26, 2021, 11:22pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/15 "2021-08-26T23:22:14Z")

</div>

Well, that’s a total of 112+415 = 527 requests/ at the surface, not counting “compound” requests that don’t show up in the status, but happen any time the data being read is larger than ~500 bytes (so… a lot, if you’re reading structures or arrays).

The docs I can find for the ENBT say it’s only rated for 900 HMI/MSG/s, so… I’d say this is about what you can expect without getting a better comm module.

@pturmel how does this line up with your real world experience?

---

<div class="post-metadata">

**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\
**Post date:** [August 26, 2021, 11:26pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/16 "2021-08-26T23:26:33Z")

</div>

Pretty much everything in that 20000 monitored item device is in AOIs, but reading the individual items. Would it be beneficial to switch my tag group to leased 5000/1000? That should reduce the request rate correct?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 26, 2021, 11:27pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/17 "2021-08-26T23:27:41Z")

</div>

Ooph, it will help a little, yes, but AOIs are worst-case scenario for driver performance because they don’t actually get read as a whole, even if you _have_ made all the members externally accessible.

There’s some info about why we can’t access AOIs efficiently in [this thread](https://forum.inductiveautomation.com/t/cip-connection-size-parameter/14681/36).

---

<div class="post-metadata">

**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\
**Post date:** [August 26, 2021, 11:30pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/18 "2021-08-26T23:30:34Z")

</div>

It seems that has improved things drastically. 12% CPU on the ENBT now.  
Thanks for looking into it, much appreciated.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/e/6ee23a3a8ba8100242a3db4d2a08de08dc6d10c8.png)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 26, 2021, 11:40pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/19 "2021-08-26T23:40:26Z")

</div>

Leased tag groups can have a little bit of a disruptive effect that you should watch out for. Basically, any time the leases change, the subscriptions change, and the driver ends up having to re-optimize based on the new set of tags/rates. This causes a minor disruption in communications. Depending on how many tags and how good your communication stats are you have you may or may not notice this delay on your tags that belong to a direct tag group.

If it becomes a problem one thing you can do is make 2 separate device connections to the PLC and use one for direct tags and the other for leased tags.

---

<div class="post-metadata">

**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\
**Post date:** [August 26, 2021, 11:43pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/20 "2021-08-26T23:43:14Z")

</div>

Thanks, I’ll keep an eye out for those issues.

[Next page](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363.md?page=2)
