[omniORB] Memory requirements for omniORB on WinNT

Mon, 1 Mar 1999 16:54:04 -0600

Hi,

(1) Yes, the pulses are between 45-70MB.  I was quite surprised with that also.

(2) I've seen similar spikes when using IONA's ORB and Orbix daemon, but
    it tends to only occur once every 5 seconds.  If my persistent omniORB
    server is not talking with a client, there are no such 1Hz pulsings.

I should also point out that I only see this spiking on the client side.  If the
server is in a different address space, it is not affected.  If the server and
client are colocated, the spiking occurs.

--- Becki

shaastri@yahoo.com at Internet on 03/01/99 12:04:00

To:   r.sanford@gd-is.com at Internet@CCMAILEXCHANGE
cc:    (bcc: Rebecca A Sanford/GDIS/GDYN)
Subject:

Some questions:

1. Are you sure the amount of memory pulsing is 70 MB (megabytes)?
This seems abnormally high.

2. Does this happen only when running OmniORB programs?
Have you monitored memory usage without running these programs?

Recommendation(s):

1. You might want to keep an eye on the Handles, Threads, Processes numbers. If
they too fluctuate then perhaps these resources are being systematically created
and destroyed.

2. Also keep an eye on the Processes tab. See whether a process gets
started and destroyed (if a thread is causing the fluctuation it won't
show up in this view). You can compile and build the Pview (or Process
Viewer) program from the MS SDK samples. This is available prebuilt as
part of the 4.0 resource kit. It is a nicer tool to monitor processes,
threads, and other system resources. It only shows a static view -
unless you keep pressing the Refresh button. I think you can even kill
a process or thread from this tool. You might be able to certainly
hack the source code to suit your needs (which I did to automatically refresh
the state at x-sec intervals).

Good luck,

/rvs
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com