Question

Scheduled event execution

0

Currently I have built a scheduled event that does processes a big amount of import entities within my application. Concurrent execution is enabled on the microflow and the scheduled event is set to go of every 15 minutes (starting exactly on the hour, on HH:15, HH:30 and HH:45). However, when I look at the log entities it seems like a scheduled event started 2 minutes later than the intended time, precisely after the previous scheduled event stopped. From this I can only conclude that Mendix processes scheduled events one after the other instead of being able to process them concurrently. Can I safely assume this?

asked 2013-07-22

Ferry van der Toorn

2 answers

Ronald Catersels · Answer 1 · 2013-07-22

I think it is a bit more complicated but may be somebody from Mendix could explain it better. I know for a fact that when a scheduled event does not finish correctly the whole scheduled event could stop (so no new event is triggered because the old one is still busy).

I do think you could have a problem if you schedule heavy imports this way because you probably have already one processor on a 100 procent load. This is asking for performance problems on your application.

Regards,

Ronald

Bart Tolen · Answer 2 · 2013-07-22

I have seen scheduled events right after each other if the first takes more than the period.

So when scheduling every 15 minutes and processing one takes more than 15 minutes the next one is started immediatly. This can even buildup a queue, so when scheduling every 5 seconds and taking a minute just once to complete then many scheduled events get fired in a row.