On Tue, Jan 23, 2018 at 10:13 AM, Anton Derbenev <[email protected]> wrote:
>
> It worth mentioning that even though my simulation IOCs are relatively heavy
> on amount of computations they do (lots of chained waveform calculations and
> aSubs), they work very well even on x100 rate without any apparent issues. I
> don't know what is the lowest scan rate achievable with the described method
> though. I guess minimal reasonable value depends on an application.
Technically, the lowest reasonable SCAN rate is limited by the
resolution of the system timer.
(Historically, the VxWorks clock was ticking at 60Hz, so 10Hz was a
reasonable choice.)
If you are able to run an IOC application using a fast rate obviously
depends on the application and the CPU power of the machine the IOC is
running on.
Note for multi-core machines: while running multiple callback threads
(that do 'I/O Intr' processing) in parallel has been available for a
while, there is still one periodic scan thread per SCAN period. Adding
support for parallel SCAN threads is conceptionally possible, but
needs work to be done (or funded).
Cheers,
~Ralph
- References:
- Re: PV Scan - Set values Anton Derbenev
- Navigate by Date:
- Prev:
Re: How to work with motor record position counts larger than 2147483648? Torsten Bögershausen
- Next:
Training Class March 5-9, Long Island NY, Topic: EPICS 7 Application Development in Python Bob Dalesio
- 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: PV Scan - Set values Anton Derbenev
- Next:
Training Class March 5-9, Long Island NY, Topic: EPICS 7 Application Development in Python Bob Dalesio
- 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
|