# Automation Professionals' EtherNet/IP Communication Suite V2

**URL:** <https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190>\
**Category:** 3rd Party Modules\
**Tags:** ignition81\
**Created:** [January 3, 2023, 10:16pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190 "2023-01-03T22:16:54Z")\
**Posts on this page:** 1\
**Showing post:** 69

<div class="post-metadata">

**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:** [April 16, 2023, 7:14pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190/69 "2023-04-16T19:14:08Z")

</div>

Good things come in batches, I suppose. My subconscious obviously wasn't done with this....

I moved all of the read infrastructure's `.setValue()` actions into Runnables on the driver's subscription thread pool, instead of leaving them in Netty's receive callchain.

Check out the resulting response time stat:

 ![20230416_145032_L320](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/c/bcd1e913981721b0a1f25875efb3afc4bf39c28a.png)

~~v2.0.4.231061846~~

My module sales page is already updated. 😁

---

_[View the full topic](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190)._