# High CPU usage on 1756-ENBT **URL:** \ **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:** 3\ **Page:** 2
**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:** [August 27, 2021, 2:27am UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/21 "2021-08-27T02:27:04Z")
> [@Kevin.Herron](#): > > @pturmel how does this line up with your real world experience? Meh. I don't trust that 100% stat in the ENBT. Flaky junk. I have to admit that I jerk them out at first opportunity. The EN2T is much better. Things to try in the meantime: - Run your concurrency up on your drivers. You have ~128 CIP connections to work with. Consider 12-ish for each of the seven CPUs. - Split UDTs out of your AOIs as described in the linked topic, if practical. - Anything else in the AOIs that is display-only or configuration or tuning, move to a leased group or scan class. ---
**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:** [August 27, 2021, 2:31am UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/22 "2021-08-27T02:31:02Z")
And I would be remiss if I failed to mention the option to use class one connections–I/O or producer/consumer–via my module: [https://inductiveautomation.com/moduleshowcase/module/automation-professionals-llc-ethernetip-class-1-communications](https://inductiveautomation.com/moduleshowcase/module/automation-professionals-llc-ethernetip-class-1-communications) Class one CIP connections seem to be a much lighter load on the PLC and comm cards even with blistering RPI settings. ---
**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\ **Post date:** [August 27, 2021, 3:15am UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363/23 "2021-08-27T03:15:22Z")
Only reason I went looking into this is because the citect driver that was also looking at the same PLC kept crashing. AFAIK this hasn’t occurred on the live system, but I am cautious of it. Thanks for your suggestions on how to improve things. Modifying the polling to be a bit smarter is probably the most practical option moving forward. [Previous page](https://forum.inductiveautomation.com/t/high-cpu-usage-on-1756-enbt/50363.md?page=1)