Experimental Physics and Industrial Control System
|
I have an EPICS R3.14.12 Linux IOC with about 24000 records, many of which are SCAN=“I/O Intr”. I see occasional messages indicating callback request queue overflow:-- 0:st.screen -- time-stamp -- May/16/17 1:29:02 -- callbackRequest: cbLow ring buffer full -- 0:st.screen -- time-stamp -- May/16/17 1:29:59 -- -- 0:st.screen -- time-stamp -- May/16/17 2:59:02 -- callbackRequest: cbLow ring buffer full -- 0:st.screen -- time-stamp -- May/16/17 2:59:54 -- -- 0:st.screen -- time-stamp -- May/16/17 7:59:02 -- callbackRequest: cbLow ring buffer full callbackRequest: cbLow ring buffer full -- 0:st.screen -- time-stamp -- May/16/17 8:00:02 --
I’ve attempted to increase the queue size, but maybe not enough:
############################################################################### # Override some sizes -- this IOC has *lots* of records callbackSetQueueSize(10000)
Is there any downside to setting the callback queue size to something really large, says 50000 or more? Is there something else I should try?
Thanks
|
- Replies:
- Re: Callback queue overflow Andrew Johnson
- Navigate by Date:
- Prev:
Re: sending pickled python objects of epics channel access Wang Xiaoqiang
- Next:
Re: Callback queue overflow Andrew Johnson
- 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: sending pickled python objects of epics channel access Hartman, Steven M.
- Next:
Re: Callback queue overflow Andrew Johnson
- 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
|
ANJ, 21 Dec 2017 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|