"Jean-Marc Blaise" <blaisedeltadb.spam.no.com> wrote in message
news:bk4q4b$3gg$1news-reader5.wanadoo.fr...idle> Hi there,
> The agent private memory depends upon various parameters, which are mostly
> deallocated when agent has terminated his job. However, I noticed manySome per-agent memory allocations are never released until the agent is> agents keep consuming quite a big amount of memory, as shown by the output
> below (up to 40 Mb, and I even noticed once up to 100 Mb).
> Is that normal ? I would have imagined an idle agent released most of its
> private memory, so that we can get some kind of 2 to 3 Mbs per agent, as
> noticed when starting the instance and activating the DB.
terminated. This is beneficial in many cases because a) you don't have a
continuous overead of allocating and deallocating memory on-demand (which
increases memory fragmentation and hurts performance), and b) by keeping
some allocations around, including the data that was resident, can improve
performance on subsequent requests. (The application workspace comes to
DB2 OLTP Performance
IBM Toronto Lab