Hi,
We have a somewhat similar experience. We're running the newer version of IIB i.e. ACE on an AIX platform, with about 60 DataFlowEngine processes. The first thing observed was that the broker startup time took double the amount of time when the agent was there, 2 hours instead of 1. Another thing we've investigated is the CPU and memory consumption, which is quite high on those servers. Overall this is challenging to analyze, because 3 things are changing with the ongoing migration: 1. From Linux to AIX 2. From IIB to ACE 3. From having no Dynatrace to having OneAgent. So we're not always sure what is caused by what 🙂
Anyway, there was a recent fix provided by IBM which helped both the broker startup time and the memory consumption per DataFlowEngine. So it's looking better now. On the other hand, it was indeed clear that the agent had a very noticeable impact on that startup time.
We're using the AIX auto-injection, and the suggestion from support was to next test it with the manual injection. We haven't done that yet. Would that make sense also for you?
The deep monitoring itself doesn't seem to have an impact on the CPU/memory usage. I have a PG monitoring rule which disables deep monitoring for exactly half of the processes. There's no difference between having it on vs. off, when it comes to CPU and memory consumption per process.
Another AIX-related observation: on this environment, the AIX osagent takes about 8-9 % CPU on most servers. Not just IIB/ACE, this affects all AIX hosts. We've had support enable a debugUI flag which changes the OS data polling interval from 10 secs to once per minute. This has taken the CPU usage down to about 4 % which is feasible.
