tokio-cron-scheduler
tokio-cron-scheduler copied to clipboard
Make channel capacity configurable
Is there any particular reason why channel capacity is limited to 200?
I have a use case where I need to schedule huge amount of jobs, which should be executed asap, and then I get RecvError::Lagged(10)
since the channel capacity is quickly filled. I can bypass this if I limit the scheduling to around 200 jobs per go.
I guess it would be nice feature if this can become configurable.