Hi,
I recently had to tweak the size of the cbLow and scanOnce queues on a
bunch of IOCs hosting a large number of PVs. Due to a lack of
diagnostics this turned out to be more tedious than I think it should
be. I was able to simplify the process by implementing simple IOC shell
functions that print queue usage and overflow information (see [1]). I'm
wondering if this might be useful enough to others to include this in Base.
I'm actually still undecided _where_ this kind of diagnostics should go
- into an IOC shell function or maybe into iocStats so it can be
monitored continuously? Pushing this to iocStats would probably require
a few changes to callback.[ch] to provide read access to some internal
data structures.
Any thoughts?
-Martin
[1]
https://code.launchpad.net/~info-martin-konrad/epics-base/+git/epics-base/+ref/callbackQueueStatus
--
Martin Konrad
High Performance Controls Team Leader
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824-1321, USA
Tel. 517-908-7253
Email: [email protected]
- Replies:
- Re: Monitoring callback queue sizes (really database callback queue size) Michael Davidsaver
- Navigate by Date:
- Prev:
Re: PVA links alpha Michael Davidsaver
- Next:
Re: Monitoring callback queue sizes (really database callback queue size) Michael Davidsaver
- Index:
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: "EPICS 3.16" versus "core/master" Williams Jr., Ernest L.
- Next:
Re: Monitoring callback queue sizes (really database callback queue size) Michael Davidsaver
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
|