|
Problem IC65503
|
Status: Closed |
HIGH CPU USAGE IN A SCENARIO WITH TABLE QUEUE SPILLING |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
The mechanism that is used to flow rows between agents in a DPF
environment is called tablequeues. There exists a flow control
mechanism to regulate the flow of rows called a tablequeue spill
that will decide to defer the sending of data by spilling it
into a temp table.
In a configuration with many database partitions, for example,
over 50 partitions or so, then due to this defect there may be
some logic that does unnecessary work thereby driving up the cpu
usage.
If stacks are collected for an agent that is trying to resend
spilled buffers, the function "StartSpillResends" might be seen
in this scenario as being a large consumer of cpu cycles.
This fix will rework the logic in a way that will remove the
unneeded work and help alleviate the cpu usage. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DPF with large node config (100+) *
****************************************************************
* PROBLEM DESCRIPTION: *
* High cpu usage during tablequeue spilling. *
****************************************************************
* RECOMMENDATION: *
* Install fixpack 6 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
fix is contained in v95FP6 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC65555 IZ68053
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.01.2010
13.05.2010
13.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
