[omniORB] OmniNames Daemon Memory Usage

Steven King steve at eminence.com.au
Wed Aug 18 15:26:58 BST 2004


Thanks for the reply,

Thomas Lockhart wrote:

>> We are running omniNames on a debian linux (Version 2.3.20) 
>> workstation, when omninames is started up it immediately uses about 
>> 32MB of memory without any CORBA object registering with the naming 
>> service. Is this standard behaviour? This memory usage seems 
>> excessive and are there any options to reduce the memory usage?
>
>
> Seems excessive to me too. Here is a dump of the process info for an 
> instance of omniNames (actually, one of three threads) just after it 
> is started up on my Linux box. Looks like 6MB virtual memory total?
>
> Is "debian 2.3.20" a 2.3.20 Linux kernel? If so, maybe using a 
> development kernel is the problem?? 

We are running a 2.4.20 kernel on two machines with omninames and we are 
experiencing the same problem on both machines. Versions 3.0.4.1-8 of 
omniOrb (debian woody package)

>
>
> hth
>
>                     - Tom
>
> wraith> sudo cat /proc/19430/status
> Name:   omniNames
> State:  S (sleeping)
> Tgid:   19430
> Pid:    19430
> PPid:   19428
> TracerPid:      0
> Uid:    255     255     255     255
> Gid:    255     255     255     255
> FDSize: 32
> Groups: 255
> VmSize:     6476 kB
> VmLck:         0 kB
> VmRSS:      2308 kB
> VmData:     2496 kB
> VmStk:         8 kB
> VmExe:        88 kB
> VmLib:      3780 kB
> SigPnd: 0000000000000000
> SigBlk: 0000000000000000
> SigIgn: 0000000000001006
> SigCgt: 0000000380000000
> CapInh: 0000000000000000
> CapPrm: 0000000000000000
> CapEff: 0000000000000000
> wraith> uname -a
> Linux wraith.fourpalms.org 2.4.21-0.30mdkenterprise #1 SMP Wed Apr 21 
> 20:53:23 MDT 2004 i686 unknown unknown GNU/Linux

Here is a copy of the status of one of the omniName server threads, 
there are 5 threads running, with all memory usage appearing similiar 
(~9MB).

Name:   omniNames
State:  S (sleeping)
Tgid:   11421
Pid:    11421
PPid:   1
TracerPid:      0
Uid:    0       0       0       0
Gid:    0       0       0       0
FDSize: 32
Groups: 0
VmSize:     9524 kB
VmLck:         0 kB
VmRSS:      1904 kB
VmData:     6576 kB
VmStk:        16 kB
VmExe:        64 kB
VmLib:      2524 kB
SigPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 8000000000001000
SigCgt: 0000000380000000
CapInh: 0000000000000000
CapPrm: 00000000fffffeff
CapEff: 00000000fffffeff


I have attached the gmemusage screen shot to show the overall memory 
usage on the system.

Are there any ideas to reduce memory usage of omniNames?  Is it possible 
to reduce the number of threads that it spawns?

Regards,

Steven King
-- 

<http://www.eminence.com.au/> Eminence Technology Pty Ltd
PO Box 118, Moorooka QLD 4105
Web: www.eminence.com.au <http://www.eminence.com.au/>
Ph: +61-7-3277-4100
Fax: +61-7-3277-4577


-------------- next part --------------
A non-text attachment was scrubbed...
Name: gmemusage.png
Type: image/png
Size: 8565 bytes
Desc: not available
Url : http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20040818/1d7324bf/gmemusage-0001.png


More information about the omniORB-list mailing list