# Automation Professionals' EtherNet/IP Communication Suite V2 **URL:** \ **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:** 205
**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:** [March 27, 2026, 4:42pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190/205 "2026-03-27T16:42:22Z")
> [@konstantinetg](#): > > If I keep the lower-level (nested) structures within ~1800 bytes, would that help improve performance? Yes, that will suffice. Minor hit for the extra path segment in the request, but probably not noticeable. > [@konstantinetg](#): > > load factor measurements There is a great deal of ambiguity (and bugs) in the various flavors of load measurement. This is what I recommend: > [@Siemens Enhanced driver, slow browsing and slow update rate](https://forum.inductiveautomation.com/t/siemens-enhanced-driver-slow-browsing-and-slow-update-rate/114287/6): > > A technique I find helpful when comms performance varies is to use a fast-changing tag in the PLC (I tend to use a GSV to retrieve WallClock currentValue, a microsecond clock) and subscribe to it in Ignition. The ladder that updates the tag should run faster than the fastest poll rate you are attempting to achieve. This yields a valueChange for every poll cycle. Adjacent to the Ignition tag, add a memory tag of type Int8 and use a valueChange script on the OPC tag that looks something like th… --- _[View the full topic](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190)._