Subject: |
Re: Gateway and EPICS_CA_MAX_ARRAY_BYTES |
From: |
"Kenneth Evans, Jr." <[email protected]> |
To: |
"Tech-Talk" <[email protected]> |
Date: |
Mon, 22 Aug 2005 09:29:53 -0500 |
There is a problem in Channel Access with EPICS_CA_MAX_ARRAY_BYTES that
causes problems in the Gateway. It has to do with one of the sockets not
being set to non-blocking (so it ends up blocking the Gateway). It is
Mantis bug #176. It will be fixed in 3.14.8 but you can contact Jeff for a
patch.
In regard to our experience: We set EPICS_CA_MAX_ARRAY_BYTES to 14000O on a
site-wide basis here and have not noticed problems. Of course, you can
always overload the Gateway by sending enough traffic. There are many ways
to monitor the Gateway and look for users that start processes with abnormal
loads. See the EPICS page at
http://www.aps.anl.gov/epics/extensions/gateway/index.php. (There is also a
paper there on the APS experience with the Gateway and what kind of loads we
handle.) We have had to, for example, encourage users to not monitor
hundreds of BPMs at KHz rates when going through the Gateway (or at least to
not have several people doing that at the same time ;-).
-Ken
- Navigate by Date:
- Prev:
Re: Gateway and EPICS_CA_MAX_ARRAY_BYTES Dirk Zimoch
- Next:
CA loss package on 1 Hz rate Liyu, Andrei
- 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: Gateway and EPICS_CA_MAX_ARRAY_BYTES Dirk Zimoch
- Next:
Table tool in EDM Chithra Karunakaran
- 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
|