On 01/14/2016 12:50 PM, Andrew Johnson wrote:
> My discomfort with per-client deadbands like this is that each client
> needs to know how big its deadband should be, and gets no hint at all
> from the record. With the existing IOC deadbands, the database designer
> can set 2 different deadband sizes for regular and archive monitors.
I'll second this. For the archiver appliance, I ask for, and Murali
provided, a means of deadband filtering on the archiver (client) side.
However, this is such a pain to configure that it wasn't get used much*.
* I still have hopes as this does allow for interesting policies like
retroactively applying a deadband to old data. For example, keep full
data for 2 weeks, then decimate w/ deadband.
- References:
- Subscription / first update Ralph Lange
- Re: Subscription / first update Andrew Johnson
- Navigate by Date:
- Prev:
Re: Subscription / first update Andrew Johnson
- Next:
Build failed in Jenkins: epics-base-3.14-sol #12 APS Jenkins
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
- Navigate by Thread:
- Prev:
Re: Subscription / first update Andrew Johnson
- Next:
Re: Subscription / first update Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
|