Hi Marco,
Please note also that what you're showing is testing a whole chain: python - CA client - network - CA server - IOC database - stream device - asyn - loopback driver. Lots of parts and lots of failure modes.
If you want to check only the PV processing time (i.e., from the database down), I would add a database on the same IOC that sets the values. Think calc records as counters, seq records for small sequences of things, etc. That would leave out the Channel Access and python client layers and maybe allow locating issues easier.
Cheers, ~Ralph
- References:
- Exploring EPICS performance/processing limits Marco A. Barra Montevechi Filho via Tech-talk
- Navigate by Date:
- Prev:
EPICS driver / support for "USS" Device: Leybold Turbovac iX William Kirstaedter via Tech-talk
- Next:
RE: Exploring EPICS performance/processing limits 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
2025
- Navigate by Thread:
- Prev:
Re: Exploring EPICS performance/processing limits Marco A. Barra Montevechi Filho via Tech-talk
- Next:
EPICS Base 3.14.12.8 build error on CentOS 9 Chiang, Liang-Chih [江良志] 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
2025
|