Chip Watson wrote:
>
> Nick,
>
> >Thus I seem to have a problem relating to R3.13, and one of the symptoms
> >is likely to be caused by Channel Access messages not being delivered for
> >substantial perods of time.
>
> Are you getting "dropped events" messages on that IOC's console? If
> so, the messages are being lost, most likely due to insufficient CPU
> resources. Channel access is starved first (reference: the "warm"
> discussion of last month on priorities), and events are then discarded.
>
If the IOC is 100% saturated then the system must degrade.
Our design choice was to degrade in a controlled fashion. We
decided that internal activities in a robust distributed system
must take priority over external activities. The channel access
_server_ is starved first. Client activity runs at a higher priority.
Its true that the IOC will discard intermediate CA events (monitors) if
the server does not have enough CPU, the network is down, or
the client does not have enough CPU.
Jeff
--
______________________________________________________________________
Jeffrey O. Hill Internet [email protected]
LANL MS H820 Voice 505 665 1831
Los Alamos, NM 87545 USA FAX 505 665 5107
- References:
- Re: R3.13 Chip Watson
- Navigate by Date:
- Prev:
Re: hanging IOCs Jeff Hill
- Next:
java-cdev Chip 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:
Re: R3.13 Chip Watson
- Next:
Web Pages about PC port Kay-Uwe Kasemir
- 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
|