hi John,
that's an interesting proposal. For addressing this problem, I have usually
renewed my critical time interval contexts every minute between interval
endpoints, and having them had a lifetime of 1 minute. This workaround
works nicely with time specifications like '* * * * *' or '* 1-5 * * 0',
since at startup sec will run actions of calendar rules which match the
given moment, doing this all *before* entering the main event processing
loop. Fortunately, the calendar rules are treated separately from other
rules which match regular input events, and the list of these rules is
scanned at most once a second. Thus the number of calendar rules has much
less impact on performance than regular rules which could be evaluated
thousands of times per second.
kind regards,
risto
2013/9/30 John P. Rouillard <[email protected]>
> Hi all:
>
> I had to define an interval today for a SEC ruleset. Since calendar
> rules only fire at an exact time, the calendar rule to define my
> interval had to fire every minute during the interval to make sure
> that the interval context was defined in case sec restarted during the
> interval.
>
> This took three calendar rules and seems to be a waste of cpu
> cycles even with a context of [ ! interval_active ].
>
> Would it be useful to define an optional time2 parameter (and possibly
> action2) for Calendar with the following semantics:
>
> if the calendar rule has not yet been triggered, and the current
> time is between time and time2, execute action.
>
> At time time2, execute action2.
>
> This means at SEC startup, the calendar rule will trigger if the time
> is between the two times. This means that the rule should be triggered
> without the delay between SEC startup and the next minute
> interval. Also this will allow a more compact way to specify two
> actions that should run at an absolute time relative to each other.
>
> --
> -- rouilj
> John Rouillard
> ===========================================================================
> My employers don't acknowledge my existence much less my opinions.
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
> _______________________________________________
> Simple-evcorr-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Simple-evcorr-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
