[foxboro] swap space/memory usage
- From: stan <stanb@xxxxxxxxx>
- To: Foxboro List <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 15 Dec 2008 10:34:10 -0500
I have run into an issue here that has caused me to start looking at the
issue of memory/swap space usage on my Foxboro Solaris 8 machines a bit more
carefully.
If you run "/usr/ucb/ps -aux" it will give you some statistics relative to
memory usage per process. What we have discovered is that a task called
windu_registry, which is (I believe) the license manager for windu s growing
to use enough memory to become a problem,Windu BTW is the Windows emulator
that things like FoxView, Foxdraw, and AIM use to allow them to run on
the UNIX boxes.
What was going on in our case was that we had installed a trail version of
Foxray on 4 AW's. We had inadvertently put the FoxRay script that checks
for historian changes in the fast collection script. which runs very
frequently. hen this script runs it calls /opt/aim/bin/histcsave, which
access AIM. So we were making hundreds of calls to windu_registry, and it
was using up all f our memory and swap space. You can easily confirm that
this behavior exists on your systems by running /usr/ucb/ps -aux and noting
the size of windu_registry, then running the histcsave, and rerunning the ps
command. You should see thta the windu registry daemon is nor larger.
In looking around while doing this I also believe that I found out why is
crashing on some of our machines. We had several AW's where X was using in
the range of 40% of the available system memory! These were the machines
that we had observed X crash on in the past.
All of these machines are AW's that we use for active development, which
involves opening Foxdraw, and the ICC, etc on a regular basis. My working
theory here is that X is failing to free memory for allocated for something
when these processes are started and stopped.
I would be interested in earing others experience with these memory usage
issues.
Thanks,
--
One of the main causes of the fall of the roman empire was that, lacking
zero, they had no way to indicate successful termination of their C
programs.
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: http://www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
- » [foxboro] swap space/memory usage - stan