Experimental Physics and Industrial Control System
Hi James,
My suggestion is not a right one to identify your memory issue, but
you should try this if your experiment or test is running now and time
is critical for you, this IOC is important for your task.
* Limit GUI instances
* Tell People not to execute GUI, and provide them a screenshot of
GUI on a web site
* Identify how to access PVs in GUI.
if GUI simply uses 'caget', please use 'timeout' according to PVs'
priority or requirement
* Setup 'CA gateway' so GUI cannot access PVs connected to the IOC
directly
JH
On 01/29/2013 01:18 AM, James F Ross wrote:
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
--
Jeong Han Lee, Dr.rer.nat.
---------------------------
Accelerator Division
Rare Isotope Science Project
Institute for Basic Science
70, Yuseong-daero 1689-gil, Yusung-gu,
Daejeon 305-811, South Korea
---------------------------
cell : +82-10-7363-2083
tel : +82-42-878-8733
fax : +82-42-878-8799
- Navigate by Date:
- Prev:
Re: copying archived data from 32-bit to 64-bit machine Pierrick Hanlet
- Next:
scan thread suspended Martin Konrad
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: memory and vxWorks based IOCs John Dobbins
- Next:
scan thread suspended Martin Konrad
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024