Utilizing db2mtrk..

[cbielins]

We are about to 'stress test' our DB2 environment. I've played with
db2mtrk off and on, trying to figure out how it's mapping the memory
to its components.

If I have the following output:

Memory for instance

fcmbp monh other
16.7M 176.0K 5.7M

Memory for database: <DB2_NAME>

utilh pckcacheh catcacheh bph bph bph bph
32.0K 1.7M 896.0K 4.2M 31.5M 314.5M 31.5M

bph bph bph bph bph shsorth lockh
4.2M 640.0K 384.0K 256.0K 192.0K 160.0K 480.0K

dbh other appctlh appctlh appctlh appctlh appctlh
12.1M 32.0K 16.0K 16.0K 16.0K 16.0K 32.0K

appctlh appctlh appctlh appctlh appctlh appctlh appctlh
32.0K 32.0K 16.0K 32.0K 32.0K 32.0K 32.0K

appctlh appctlh appctlh appctlh appctlh appctlh appctlh
32.0K 32.0K 48.0K 32.0K 16.0K 32.0K 16.0K

appctlh appctlh appctlh appctlh appctlh appctlh appctlh
32.0K 32.0K 144.0K 32.0K 16.0K 32.0K 32.0K

appctlh appctlh appctlh appctlh appctlh appctlh appctlh
32.0K 32.0K 32.0K 32.0K 16.0K 32.0K 32.0K

appctlh appctlh appctlh appctlh appctlh appctlh appctlh
32.0K 32.0K 32.0K 32.0K 32.0K 32.0K 16.0K

appctlh appctlh appctlh agsh
32.0K 32.0K 80.0K 94.0M

I can see that there is memory allocated for bufferpools, app ctl
heaps, locks, etc etc.

This snapshot was taken with 2 active connections both crunching a
query. In our stress test, we plan on having upwards of around 40
connections at once 'going to town',

My question is (finally), with that many connections, and with the
output above, how will I be able to see what's going on? Will I be
able to tell if there really is a memory leak? How will I be able to
deduce this information?

Thanks, Chris