As a developer I would like stream device IOCs to use more forward links to initiate processing rather than having separate SCAN loops running on timers. As noted in #6286 lots of separate periodic scan records all trying to access the serial device port does not scale well and can lead to lock timeouts and failed processing. As the serial device port is only single access, it would be more logical to chain (FLNK) records from a single (or small number) of periodically scanning records.
Acceptance Criteria
List of IOC with large number of separately scanning records identified
The original problem was seen with invalid alarms appearing ever few seconds on the mercury itc on EMU and MUSR. Once fixed in the mercury itc driver we should test the changes on EMU.
As a developer I would like stream device IOCs to use more forward links to initiate processing rather than having separate SCAN loops running on timers. As noted in #6286 lots of separate periodic scan records all trying to access the serial device port does not scale well and can lead to lock timeouts and failed processing. As the serial device port is only single access, it would be more logical to chain (FLNK) records from a single (or small number) of periodically scanning records.
Acceptance Criteria