Skip to content
Discussion options

You must be logged in to vote

Hi @praepanwa-ted ! A single sensor is light, but every sensor is checked by the dagster-daemon on a loop (every 30 sec in your case), and each check calls your code location. So with many chained sensors, there is always some background work running, even on days when no job runs. Also, each step in the chain can wait up to one interval before the next job starts.

Some options I would suggest, from simple to more "Dagster way":

1. Keep steps that always run together in the same job (or make them dependent assets). Then you don't need a sensor between them at all.

2. If you still need sensors, use one run status sensor for many jobs instead of one sensor per job. Since your jobs don't run…

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@praepanwa-ted
Comment options

@sai-sakalam
Comment options

Answer selected by praepanwa-ted
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants