setting :frequency > 1s mean the scheduler may not fire cron style jobs

[jmettraux]

setting :frequency > 1s mean the scheduler may not fire cron style jobs

[jmettraux]

Hello, thanks for reporting.

I don't know about this one. Should I consider it a bug and take the time to fix it ? Using a frequency < 1s "fixes" it.

Then scheduler is meant not to waste too much time when waking up and checking for jobs to trigger (Well maybe you have lots of jobs and that's becoming visible).

Your description in the gist is not accurate. It's not "trigger a job every 10s" but "trigger a job at seconds 0,10,20,30,40,50".

Setting a custom :frequency may make more sense for "in" and "at" jobs. Maybe I should add a warning to the documentation.

If you really really need that to work, I could re-implement the cron system to re-schedule each triggered cron job instead of iterating over cron jobs to filter the one that matches. That's a subtle yet radical change. Not sure about introducing it.

[soulware]

Hi,

I think maybe a warning in the documentation would be fine here - as you say, setting the frequency to <1s allows the cron style jobs to run as expected.
Do you think there are any situations where the default frequency would still not run at least once per second? What if a blocking job was running at the time?

[jmettraux]

I think under heavy load it's always possible to have "gaps".

Blocking jobs should be used with care.

Maybe you want something like http://gist.github.com/284467 (if you swap lines 17 and 18, the behaviour should be OK, though it's a blocking scheduler). This is how I do scheduling in the latest version of http://github.com/jmettraux/ruote

[jmettraux]

Closing.