Does the scheduler only run one thing at a time?
I noticed that I fired off a bunch of scheduled mutations around the same time, but it seems like a queue it backed up somewhere or something. It's taking a long time to process through these scheduled mutations. Is there more insight into the concurrency limits on scheduled mutations?
6 Replies
I wonder if maybe it's just contention on a single db record. Also I'm trying to cancel all of these but it keeps giving me an error
I ended up just deleting my project and recreating it
if the mutations all update the same document, then they will run one at a time yes, to guarantee serializability. this is true for scheduled mutations and also for client-driven mutations. if the mutations read and write to different documents, they will run in parallel.
sorry that canceling is being difficult. completing a scheduled function and canceling a scheduled function are similarly writing to the same database record, so they can compete with each other. It may be easier if you pause your deployment first (in settings).
Do you know if the scheduler has any type of concurrency limits built into it or is it kind of operate the same way just running a mutation would
There are concurrency limits, yes. If they seem too low, let us know (we can increase them in a pinch). Typically throughput is more limited by contention on hot documents than by the concurrency limit