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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: When I use an IOC in a container, streamDevice occasionally reports that protocol has been aborted, which causes the records in the IOC to become inaccessible from the host computer. |
From: | "Wang, Andrew via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Mark Rivers <rivers at cars.uchicago.edu>, Zimoch Dirk <dirk.zimoch at psi.ch> |
Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Fri, 12 May 2023 23:27:42 +0000 |
Hi Mark and Dirk, Thank you for your responses. I will do my best to identify if it is a container or EPICS issue by separating out the IOC from the container as soon as possible. It won’t be until later next week unfortunately. From: Mark Rivers <rivers at cars.uchicago.edu> Timeouts in the protocol should be recoverable. From what I understand once this happens all CA access to the IOC is lost. If so, this is a more serious issue. Mark From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Zimoch Dirk via Tech-talk Hi Andy, I suspect your container stalls from time to time, causing timeouts in the protocol. I do not think that containers have been designed with real-time performance in mind. Thus I am not really surprised that it does not behave like a pure host. Maybe you can tune how the host schedules the containers?
Or reduce the number of containers per host? It may simply be overburdened. Do you have any figures on the system load? Dirk
|