|
View previous topic :: View next topic
|
| Author |
Message |
John Poulakos
Active User
Joined: 13 Jun 2012
Posts: 178
Location: United States
|
|
|
|
I'm seeing serious APA overhead for an intense DB2 application and I don't know if this is normal, or if there is anything that can be done to reduce it. Here's a sample:
| Code: |
Name Description Percent of CPU Time * 10.00%
*....1....2....3....4....5
DSNIDM Data Manager 27.93 **************
CAZ00681 APA DB2 Services 20.71 **********
DSNXGRDS Relational Data 8.50 ****
System
1BCFDxxx Unresolved 5.34 ***
Address
Application 4.65 **
Program
CAZ00670 APA DB2 Services 4.19 **
DSNGD001 Data Manager 3.99 **
1B736xxx Unresolved 3.96 **
|
CAZ00681 and CAZ00670 are the APA modules. There were 1m opens, 2m fetches and 1m closes done in this sample. |
|
| Back to top |
|
 |
AlanMac
New User
Joined: 04 Dec 2018
Posts: 1
Location: UK
|
|
|
|
| Switch off the plus collectors, and I suspect your overhead is also in the unresolved locations too should you delve in to your CSA |
|
| Back to top |
|
|
vasanthz
Global Moderator
Joined: 28 Aug 2007
Posts: 1742
Location: Tirupur, India
|
|
|
|
Turning off the plus collectors should be the heavy hitter, Also I think we should pay attention to the "Measurement Significance" value in S01 report which says how good of a measurement it is based on the sampling rate and time.
Also the "S01: Measurement profile" has the APAs overhead CPU time in seconds. With that we could determine if overhead is large or a very small value whose % value is exaggerated in comparison.
Also this thread is over 4 years old :-) |
|
| Back to top |
|
|
|
|
