Logic/Calculations - Delay Execution

[tfranklin]

Hey all,

I'm running into a situation right now where a user has a a calculation tag that has multiple inputs.  The program is set to "on input processed".  You can probably see where this is going.  It's almost like the program is doing what it's designed to do.

These three inputs change within a few MS of each-other once a minute.  When they update, the calculation point will fire off 3 times and log 3 historical values.  This seems like a huge wasted effort on the processing side of CS. I believe the bigger issue here is more of a design issue on the implementation side, but I feel like it's resolvable by preventing multiple executions on a program that occur within x MS/Seconds.  Where this becomes an issue is in their situation, the calculations are pretty widespread.  This has lead to a large amount of history being generated that isn't really useful.  I know we can prevent history from being written by using the minimum interval, but I'd assume that the calculations still get processed which seems like wasted effort.  Frequent calculations can easily grow a granule larger than 2MB which then starts to impede server sync.  It's all a cumulative thing.

I was thinking an option to Delay Execution or possibly something like Group Queued Requests would be beneficial here.  The idea would be if multiple executions are received within a configured time frame, the program will only execute once at the end of the delay period with the values at the time of execution.  I can see this being beneficial on calculation tags, ST Logic, FBDs, etc. 

[sbeadle]

Thank you

[CDaniels_cvx]

Would also echo this request.

Only work around I found was having an ST Program with a short timer to trigger the method on a calculation point to prevent the multiple values with the same time stamp.