Re: Autosave -- debug output when field is updated

["Mooney, Tim M." <mooney@aps.anl.gov>]

What Mark said.  But also, we had a situation recently in which several PVs were being posted at hundreds of HZ, and just having monitors on those PVs used a surprising amount of CPU.  (We had a calcout record with CP links to the rapidly posted PVs.  When we prevented the calcout record from processing, CPU went down, of course, but only to around 30%.  When we deleted the links, the CPU went down to a normal range.)  (Autosave monitors the PVs it saves, though I don't know if its monitor processing is comparable to an input link's monitor processing.)

Tim Mooney (mooney@aps.anl.gov) (630)252-5417
Beamline Controls Group (www.aps.anl.gov)
Advanced Photon Source, Argonne National Lab

---

From: tech-talk-bounces@aps.anl.gov <tech-talk-bounces@aps.anl.gov> on behalf of Mark Rivers <rivers@cars.uchicago.edu>
Sent: Tuesday, February 13, 2018 1:32:27 PM
To: 'Daykin, Evan'; tech-talk@aps.anl.gov
Subject: RE: Autosave -- debug output when field is updated

 

Hi Evan,

 

Note that the rate at which the PV updates and the rate at which the autosave file is written are quite different things.  I don’t think it would use a lot of CPU for the PV to update rapidly when the file is only being written every 30 seconds or so.  But perhaps I am wrong?

 

Mark

 

 

From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Daykin, Evan
Sent: Tuesday, February 13, 2018 12:50 PM
To: tech-talk@aps.anl.gov
Subject: Autosave -- debug output when field is updated

 

Hello,

 

Apologies in advance if this is in the documentation somewhere, I was unable to find it.

We have an IOC which uses quite a lot of CPU when autosave is turned on. This is most likely the result of some inadvertently autosaved fields being updated at 100Hz. Is there a straightforward way, such as an IOC shell command, to print some debug output whenever an autosaved field is written?

 

Best,

Evan