1. 05 Feb, 2019 4 commits
  2. 04 Feb, 2019 4 commits
  3. 02 Feb, 2019 2 commits
  4. 01 Feb, 2019 10 commits
  5. 31 Jan, 2019 2 commits
  6. 23 Aug, 2018 2 commits
  7. 03 Aug, 2018 3 commits
  8. 18 Jun, 2018 1 commit
  9. 08 May, 2018 3 commits
  10. 07 May, 2018 1 commit
  11. 26 Apr, 2018 4 commits
    • Jameson Rollins's avatar
    • Jameson Rollins's avatar
      update TODO · d0680a94
      Jameson Rollins authored
      d0680a94
    • Jameson Rollins's avatar
      daemon: tweak loop timing diagnostics · d31ed108
      Jameson Rollins authored
      clarify int microseconds.
      d31ed108
    • Jameson Rollins's avatar
      don't update cas driver PV values after every setitem · 0478c9e6
      Jameson Rollins authored
      Here we do batch updating of the driver PVs, rather than after every setitem.
      driver.updatePVs is a heavy operation, proving to be most of the CPU load
      during profiling.  Batch updating reduces the number of updatePVs calls by an order of magnitude, from
      roughly 100 per cycle (when coupled with cas.__setitem__) to roughly 10 in
      the current implementation.
      
      Unfortunately there's some way that updatePVs seems to affect client writes
      that is not yet understood.  We should only have to call updatePVs twice in
      the main loop to push out all updates.  But some weird behavior was observed,
      where client writes didn't seem to take affect.  This needs to be investigated
      more, but in the mean time calling updatePVs around process seems to behave
      ok.
      
      The ordering in the channel updates as seen by the tests changes slightly,
      since all updates happen as a batch rather than individually when they are
      set.
      0478c9e6
  12. 25 Apr, 2018 4 commits