[omniORB] OmniNames Daemon Memory Usage

[Harri Pasanen]

On Wednesday 18 August 2004 06:26, Steven King wrote:
> 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).

Now you are talking about 9Mb, while previously you said 32 Mb.

I have noticed as well that the memory usage of omniNames fluctuates a 
lot.  As a test I started up an empty one, and it hogged something 
like 26Mb after start.

I took a look at another one that has been running for two weeks, and 
the same process has been from 6Mb to 30Mb in the space of 10 
minutes.

This is with OmniOrb 4.

I wonder where all the memory goes, and is it just opportunistic at 
TCP/IP level when it sees that there is memory available...  For what 
its doing I'd expect it to run on Commodore 64-- ;-).

Regards,

Harri


This message, including any attachments, is intended only for the person(s) to whom it is addressed. If you received it in error, please let us know and delete the message from your system. This message may be confidential and may fall under the duty of non-disclosure. Any use by others than the intended addressee is prohibited. Trema shall not be liable for any damage related to the electronic transmission of this message, such as failure or delay of its delivery, interception or manipulation by third parties, or transmission of viruses or other malicious code.