Re: Status of "event-driven" scheduling

2018-09-13 Thread Joe Percivall
Mike/Mark, Thanks for the responses! Given the background and current state, I'd vote to mark as deprecated too. If in agreement, I'll create the ticket for further discussion/planning. Mike, that's a great point around IO vs CPU driven tasking buckets. With some of the modern reactive

Re: Status of "event-driven" scheduling

2018-09-13 Thread Mark Payne
Joe, Mike is right in that it was intended to be a more efficient scheduling strategy. With Timer-Driven, the processors used to constantly be checking if they had work to do and if not would switch contexts and check again. And again. This was pretty expensive, so we added the Event-Driven

Re: Status of "event-driven" scheduling

2018-09-12 Thread Michael Moser
Hi Joe, I'm guessing here, but I think the Event Driven scheduling was intended to be more efficient than Timer Driven scheduling, in the way that push notifications should be more efficient than polling. In practice, I'm not sure anyone has measured the difference. I have seen folks use Event

Status of "event-driven" scheduling

2018-09-06 Thread Joe Percivall
Hey everyone, The dataflow I'm running has one main flow and a couple other disjoint process groups. Within that main flow, there are sections which aren't used very often. In trying to optimize things, I looked into the guidance we have on the "event-driven" scheduling type. There doesn't appear