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: | "Manoussakis, Adamandios via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Zimoch Dirk <dirk.zimoch at psi.ch>, "Wang, Andrew" <wang126 at llnl.gov> |
Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Fri, 12 May 2023 21:04:37 +0000 |
Hi Dirk, I will try to look into the possibility the containers are interfering/stalling, but we only seem to have issue with this one containerized IOC. We have multiple containerized IOCs that speak with hardware and do not crash (which is odd
trying to find out why we have this happening). Also we have a few versions back system containerized IOCs that does not have these partial crashes we currently are seeing (might be a change we made in the IOC). I doubt the system is overburdened either
as its an enterprise server (2.8GHz 64 core 128gb ram) that everything is running on, we barely are touching the resources (1-3%) at the moment. Thanks for looking at this! Adam 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
|