What the performance impact of enabling WebSphere PMI
- by Andrew Whitehouse
I am currently looking at some JProfiler traces from our WebSphere-based application, and am noticing that a significant amount of CPU time is being spent in the class com.ibm.io.async.AsyncLibrary.getCompletionData2.
I am guessing, but I am wondering whether this is PMI-related (and we do have this enabled).
My knowledge of PMI is limited, as this is managed by another team.
Is it expected that PMI can have this sort of impact?
(If so) Is the only option to turn it off completely? Or are there some types of data capture that have a particularly high overhead?