[omniORB] High virtual memory shown for omniNames

[Agarwal, Shelendra]

Hi Duncan,

Total number of entries are less than 100.

Also memory is not increasing, the value of 9g is shown at the start of the process itself, i.e. within few minutes of starting of omniNames. Non destroying of iterators by client would have resulted in gradual memory increase, right?


Thanks & Regards,

Shelendra Agarwal
Telco Big Data Analytics
Communications & Media Solutions 
HP-India
+91-9945056319

shelendra.agarwal at hp.com
Absence of evidence is not evidence of absence.

-----Original Message-----
From: Duncan Grisby [mailto:duncan at grisby.org] 
Sent: Friday, June 26, 2015 3:39 PM
To: Agarwal, Shelendra
Cc: omniorb-list at omniorb-support.com
Subject: Re: [omniORB] High virtual memory shown for omniNames

On Fri, 2015-06-26 at 06:35 +0000, Agarwal, Shelendra wrote:

> Recently we have noticed that omniNames shows very high virtual 
> memory. The output of below command shows around 9GB of vss. Though 
> there is no memory leak as over a period of time we don’t see memory 
> to be growing but we are unable to understand why there is such high 
> memory shown for this simple process.

How many entries are you storing in omniNames?  As you say, it is a very simple process. It stores all the names in memory, because the expectation is that the CORBA naming service contains just a small number of entry-point services. If you are storing vast numbers of entries, that would explain why it is big.

The other possible use of memory is in iterator objects. If your clients receive iterators, they are responsible for destroying them.

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --