Experimental Physics and Industrial Control System
|
Hi,
in a fast data-acquisiting application that also controls hundreds of
neutron detectors we are using asynPortDriver interface for detector
configuration and status communication which results in many
asynPortDriver params. The communication is fast (less than 1ms for
request/response round trip) but is probably still considered blocking.
Especially because there's approx 500 params per port, many are
written/read in groups and if every request blocks for 1ms it could
block CA thread significantly. Our workaround so far was done in
database but is overly complex. The obvious solution is to use asyn's
blocking mode, but there's up to 500 ports resulting in as many threads.
Ideally there would be an asynPortDriver interface to manage queue
threading, which we could then overload and do custom thread management.
Is there any other approach to keep number of threads low while
providing blocking mode? Would asyn patch that allows asynPortDriver do
queue thread management be of broader interest?
-- Klemen
- Navigate by Date:
- Prev:
Re: [EXTERNAL] Camonitor with client dictated update rate Klemen Vodopivec via Tech-talk
- Next:
Re: support for SBS IP-Stepper and Technalogix TSV-3000 RF amplifier Peterson, Kevin M. via Tech-talk
- 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:
New releases of areaDetector drivers ADSimDetector, ADPerkinElmer, and ADSpinnaker Mark Rivers via Tech-talk
- Next:
FW: How to share asyn's queue thread among ports? Mark Rivers via Tech-talk
- 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, 30 May 2019 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|