# 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:** 1\
**Showing post:** 17

<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).

---

_[View the full topic](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363)._