Eugene,
Thanks for the query.
For reducing Detector overhead, the main new feature is Collection Tasks feature described in the doc.
https://docops.ca.com/ca-detector-for-db2-for-z-os/19-0/en/product-information/enhancements#Enhancements-collection_processRedesignedSQLCollectionProcess
While the USEZIIP parm is wanted, you also need the parm USECOLLTASKS=Y
Take a look at the collection stats for each interval so you can see how much zIIP offload you are getting plus the usage of the Collection Task queues.
https://docops.ca.com/ca-detector-for-db2-for-z-os/19-0/en/using/collecting-sql-data/view-collection-status
You can find out if your zIIP processors are being used or if they are too busy and you are getting zIIP on CP values.
For Subsystem Analyzer, depend SSA Volume and Extent = N and Sampling Rate = 25%
https://docops.ca.com/ca-subsystem-analyzer-for-db2-for-z-os/19-0/en/using/collecting-data/reducing-collection-overhead
If your GETPAGE activity for an object is 300,000 or more, then use the 3% parm value. At 25%, you are accurate with object at 30,000 Getpages.
The best way to measure overhead of any monitor is run a workload without the monitoring and run the same workload with the monitor.
Let us know if you have further questions,
Jeff Gross
Product Owner