On Jul 16, 10:13=A0pm, "Ian Boyd" <ian.msnews...@[EMAIL PROTECTED]
> wrote:
> Customer is running a load test against a websphere application that
uses
> DB2. =A0While the load test is running the memory usage of DB2 climbs
fro=
m x
> up to y. When the load test ends, the memory usage of DB2 returns to x.
>
> However, sometimes after running the load test the memory usage does not
> drop down to x right away; sometimes it takes a few hours. This
"problem"
> exists with their current live version of the software, and the version
w=
e
> want to install. Customer will not install update until this "problem"
is
> resolved.
>
> Customer is a government organization, in which the DB2 admin, the DB2
> server admin, the server memory usage admin have collectivly as much
> knowledge as a sack of door knobs.
>
> Besides, "Go f*ck yourself.", what can we tell the customer?
I assume that the "load test" refers to an application load test
rather than a data load using the db2 load utility. Normally most DB2
memory usage is static i.e. the memory required by the database and
table space buffer pools is allocated at database startup and does not
change. However in versions 8 and 9 IBM introduced automatic memory
management which means that DB2 will dynamically expand and contract
it's memory pools depending on load. I always switch this off because
I like to have control over memory usage. It may be that in your case
DB2 gradually releases memory as the load drops off.
Check the database parameters.
db2 connect to "yourDatabase" user xxxxx
db2 get db config for "yourDatabase"
Look at:
Self tuning memory (SELF_TUNING_MEM) =3D OFF
|
