g+
g+ Communities
Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014 
<== Date ==> <== Thread ==>

Subject: Re: memory and vxWorks based IOCs
From: James F Ross <james.falconer.ross@gmail.com>
To: Tim Mooney <mooney@aps.anl.gov>
Cc: EPICS Tech Talk <Tech-talk@aps.anl.gov>
Date: Mon, 28 Jan 2013 12:23:33 -0500
I don't believe that I am running devIocStats.  It is running a very old version of epics: 3.13.10.  Do you happen to know if this is compatible with devIocStats?  If so, and I install it, would it require changes to the source code or just to the db files to include a memory PV?
Thanks!
James

On Mon, Jan 28, 2013 at 11:34 AM, Tim Mooney <mooney@aps.anl.gov> wrote:
Hi James,

Are you running devIocStats?
http://www.slac.stanford.edu/grp/cd/soft/epics/site/devIocStats/

If so, memory is available as a PV whose value you could record in any number of ways.

Tim

From: "James F Ross" <james.falconer.ross@gmail.com>
To: "EPICS Tech Talk" <Tech-talk@aps.anl.gov>
Sent: Monday, January 28, 2013 10:18:52 AM
Subject: memory and vxWorks based IOCs


Hello everyone,
I suppose this is more a vxWorks question than an epics question, but here is the issue.
I've got a VME based IOC running here at STAR that is having memory problems.  Basically we noticed this issue as every 24-48 hours the IOC would lose communication and all GUIs associated with it would go blank.  The solution is to re-start the IOC by rebooting the VME, but doing this every day is not a good solution. 

The epics is running on vxWorks, so I can use the memShow command to show the memory usage at a given time.  I can see that as I open more and more GUIs, the memory fills up.  At least part of the cause of the loss of communication has to do with too many people opening GUIs relating to this IOC at the same time.  However, I am not certain that this is the only problem. 

What I would like is to track the memory usage over time to see if there is a time component as well as just too many GUIs being opened.  Does anyone know how to do this in vxWorks?  Get it to print its memory usage every minute or so to a log file or something similar? 
Thanks
James





Replies:
Re: memory and vxWorks based IOCs Paul Sichta
References:
memory and vxWorks based IOCs James F Ross
Re: memory and vxWorks based IOCs Tim Mooney

Navigate by Date:
Prev: Re: unable to tunnel CA through ssh tunnel Till Straumann
Next: Re: memory and vxWorks based IOCs Paul Sichta
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014 
Navigate by Thread:
Prev: Re: memory and vxWorks based IOCs Tim Mooney
Next: Re: memory and vxWorks based IOCs Paul Sichta
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICSv4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·