
Sign up to save your podcasts
Or
Here are the show notes for Episode 21 “Fits and Starts”. The show is called this because we talk about fitness devices, and the Performance topic that had work submitted after a one minute hiatus.
Post-IPL dynamic APF changes are reflected in SMF 90 Subtype 37. A lot of the function is in z/OS V2.2, with these fields in the SMF record:
Performance: An interesting Db2 DDF case
Central to Martin’s DDF work is some analysis code to process SMF 101 DB2 Accounting Trace.
A customer complained their DDF application stopped dead one evening – for 1 minute. It was an application serviced by a 3-way Datasharing group. The customer sent SMF 101 data from all 3 members for 3 hours around the stoppage, and for 3 hours the previous evening for a presumably “good behaviour”.
Martin plotted application statistics at a one second interval level. It showed a 40-second stoppage the evening they hadn’t complained, making the 1 minute threshold interesting as a number.
Martin “zoomed in” to a much shorter time range . When transactions started again they were elongated, and it that was due to the clustered arrivals in clearing the backlog.
The best theory is something external stopped transactions arriving.
Further he thought there could be “near misses” many times, just short of the 1 minute mark. After transactions started coming again there were spikes in transactions arriving every minute. The speculation is this might be the middle tier doing something on a 1 minute basis: Maybe retries of some sort?
You can reach Marna on Twitter as mwalle and by email.
You can reach Martin on Twitter as martinpacker and by email and blogs at blog.
Here are the show notes for Episode 21 “Fits and Starts”. The show is called this because we talk about fitness devices, and the Performance topic that had work submitted after a one minute hiatus.
Post-IPL dynamic APF changes are reflected in SMF 90 Subtype 37. A lot of the function is in z/OS V2.2, with these fields in the SMF record:
Performance: An interesting Db2 DDF case
Central to Martin’s DDF work is some analysis code to process SMF 101 DB2 Accounting Trace.
A customer complained their DDF application stopped dead one evening – for 1 minute. It was an application serviced by a 3-way Datasharing group. The customer sent SMF 101 data from all 3 members for 3 hours around the stoppage, and for 3 hours the previous evening for a presumably “good behaviour”.
Martin plotted application statistics at a one second interval level. It showed a 40-second stoppage the evening they hadn’t complained, making the 1 minute threshold interesting as a number.
Martin “zoomed in” to a much shorter time range . When transactions started again they were elongated, and it that was due to the clustered arrivals in clearing the backlog.
The best theory is something external stopped transactions arriving.
Further he thought there could be “near misses” many times, just short of the 1 minute mark. After transactions started coming again there were spikes in transactions arriving every minute. The speculation is this might be the middle tier doing something on a 1 minute basis: Maybe retries of some sort?
You can reach Marna on Twitter as mwalle and by email.
You can reach Martin on Twitter as martinpacker and by email and blogs at blog.