You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, thank you for the excellent suggestion! It sounds like a promising idea, and I was thinking about whether it's feasible. Here are the changes that would need to be made:
The scheduler currently ticks every minute. If it runs every second, that might be too frequent, so we'll need to think about how to manage that. Running per second could generate a lot of log and status files on disk, which might lead to inode capacity or performance issues. I believe it's possible, but at the moment, running every second might add too much overhead, and I’m not sure it’s worth it.
My suggestion is to create a loop inside the DAG to achieve a similar effect. For example:
it would be nice to have support for to run a job every n seconds, so i can do health monitoring every 5 seconds instead of every minute.
the cron libraries you use has support for seconds parsing, both in the frontend https://www.npmjs.com/package/cron-parser and in the backend https://github.com/robfig/cron?tab=readme-ov-file#upgrading-to-v3-june-2019
e.g.
so maybe it just has to be enabled ?
currently im using cronicle to check every 5 seconds, but i want to switch to dagu.
The text was updated successfully, but these errors were encountered: