db2ckpwd uses a lot of memory
in [DB2]
|
From: Richard on 4 Aug 2008 10:48 On Aug 4, 5:33 am, danfa...(a)hotmail.com wrote: > Hi! > > I'm on Linux RHEL 64-bit db2 version 9.5.0.1 using four partitions on > a single server. > The db2ckpwd 4*3 =12 processes each uses 959220 k of memory which > totals +10GB. > Also the four db2wdog processes each uses +1GB > Are these figures normal? > Can they be configured? > /dg I experienced same thing in V8.2 The resolution was db2set DB2_NUM_CKPW_DAEMONS=0 and bounce instance.
From: Dan van Ginhoven on 4 Aug 2008 14:04 "Richard" <RSL101(a)gmail.com> wrote in message news:9f3ce90f-c16e-47da-bcb8-da7648930d12(a)p25g2000hsf.googlegroups.com... On Aug 4, 5:33 am, danfa...(a)hotmail.com wrote: > Hi! > > I'm on Linux RHEL 64-bit db2 version 9.5.0.1 using four partitions on > a single server. > The db2ckpwd 4*3 =12 processes each uses 959220 k of memory which > totals +10GB. > Also the four db2wdog processes each uses +1GB > Are these figures normal? > Can they be configured? > /dg > I experienced same thing in V8.2 The resolution was db2set > DB2_NUM_CKPW_DAEMONS=0 > and bounce instance. That would mean that a ckpw process must be spawned for each logon try. What perfromance issues did you get? /dg
From: danfan46 on 5 Aug 2008 01:25 On Aug 4, 10:26 pm, Darin McBride <dmcbr...(a)naboo.to.org.no.spam.for.me> wrote: > danfa...(a)hotmail.com wrote: > > Hi! > > > I'm on Linux RHEL 64-bit db2 version 9.5.0.1 using four partitions on > > a single server. > > The db2ckpwd 4*3 =12 processes each uses 959220 k of memory which > > totals +10GB. > > Also the four db2wdog processes each uses +1GB > > Are these figures normal? > > Where are you getting that information from? From what I can tell, each of > my db2ckpwd processes are actually using under 30MB. Perhaps you're > confusing VmSize and VmRSS? The VmSize is a virtual size - it just tells > you how many pages are available to the process. That doesn't mean there is > any real memory (either physical RAM or virtual through your swap > partition(s)) behind it. The VmRSS tells you how much actual memory is > allocated to the process (not swapped). > > Stolen fromhttp://www.linuxforums.org/forum/linux-kernel/49438-proc-pid-status.html: > > VmSize: The size of the virtual memory allocated to the process > VmLck: The amount of locked memory > VmRSS: The amount of memory mapped in RAM ( instead of swapped out ) > VmData: The size of the Data segment > VmStk: The stack size > VmExe: The size of the executable segment > VmLib: The size of the library code > VmPTE: Size of the Page Table entry > > I believe that shared memory gets counted in here. For example, the library > code is unlikely to be duplicated from process to process - if you already > have libdb2.so.1 loaded in one db2ckpwd process, it's unlikely to be copied > to the other two. Instead, each process gets read-access to the same pages > of memory, and thus it's only loaded once. Same goes for the data segment - > much of it is likely shared in copy-on-write fashion (and most of it is > unlikely to be written to). Some of it may be shared memory that is shared > with db2syscr (the root-based system controller), so it's allocated either > way anyway. > > > Can they be configured? > > You can try the disabling trick - but you should check your memory usage (I > use conky for this) before and after to see if you're really seeing a memory > savings. My bet is that you won't even notice. Thanks. Always learning more..... /dg
|
Pages: 1 Prev: db2ckpwd uses a lot of memory Next: Large number of reads on sysibm.sysuserauth. |