>2) Raising the priority of the name resolution task above the scan
> tasks gives me an uneasy feeling. An ioc should always give
> highest priority to local affairs before it pays attention to
> CA clients.
I disagree strongly. If an operator can't bring up a control screen in a
timely fashion, the control system isn't working. If a low priority
record isn't scanned for a few seconds, its no big deal (see LONG email
previously about scan priorities). Again, we have many applications
split among multiple ioc's, so "local" doesn't address the whole problem.
Frankly, there is almost nothing in our EPICS databases which is truly
real time. We do all our hard real time stuff in VxWorks tasks.
We'll try raising the priority of the CA TCP task; that just makes it
much less likely to get into the hung state (which, of course, is good
enough for now). Thanks for this suggestion, I should have thought of
it myself.
>No matter what improvements are made to the CA connection algorithm,
>it will not solve the problem of an IOC having little or no idle time.
There's plenty of time if priorities are properly managed :)
Chip
- Replies:
- Re: flaky IOC problems at Jefferson Lab Marty Kraimer
- References:
- flaky IOC problems at Jefferson Lab Marty Kraimer
- Navigate by Date:
- Prev:
Re: flaky IOC problems at Jefferson Lab Bill Brown
- Next:
Re: flaky IOC problems at Jefferson Lab watson
- 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:
flaky IOC problems at Jefferson Lab Marty Kraimer
- Next:
Re: flaky IOC problems at Jefferson Lab Marty Kraimer
- 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
|