EPICS Home

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  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: memory and vxWorks based IOCs
From: Tim Mooney <[email protected]>
To: James F Ross <[email protected]>
Cc: EPICS Tech Talk <[email protected]>
Date: Mon, 28 Jan 2013 10:34:04 -0600 (CST)
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" <[email protected]>
To: "EPICS Tech Talk" <[email protected]>
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 James F Ross
References:
memory and vxWorks based IOCs James F Ross

Navigate by Date:
Prev: RE: BOY number representation & display scaling Chen, Xihui
Next: Re: unable to tunnel CA through ssh tunnel Till Straumann
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: memory and vxWorks based IOCs James F Ross
Next: Re: memory and vxWorks based IOCs James F Ross
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024