[Bug 1861612] Re: callbackRequestDelay not waiting for 1/60 sec on vxWorks

[rivers via Core-talk <core-talk at aps.anl.gov>]

> Well, in both cases (HIGH delays and callbackRequestDelay) we seem to have a threshold 
> for the requested delay with a response switching between a 1 tick delay and a 0 tick delay.

But HIGH delays use callbackRequestDelay just like the scaler record
does.  So why does the scaler record appear to get immediate callbacks
when the delay=1/60., but the bo record HIGH processing does not?  And
why does bo HIGH processing have a change in behavior between delay=0.01
and 0.005?

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1861612

Title:
  callbackRequestDelay not waiting for 1/60 sec on vxWorks

Status in EPICS Base:
  New

Bug description:
  The problem is documented in this tech-talk thread:
  https://epics.anl.gov/tech-talk/2020/msg00308.php

  In 7.0.3.1, but not in 7.0.3, callbackRequestDelay(1/60) results in
  100% CPU time, most of the time in cbHigh.

  This happens on vxWorks 6.9.4.1 and was first seen with the scaler
  record with multiple types of scaler hardware and device support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1861612/+subscriptions