When you trigger a prod or staging run in the Trigger.dev cloud it takes 3 seconds on average for the machine to start up and your code to start executing. This same slowness happens when a run resumes, like after using wait.for if the delay is above a threshold when we shut the machine down.
They take this long because we're using Kubernetes for our cluster and a new pod takes a while to come up.
We're switching to using MicroVMs for the cloud machines. Our target is to get the p95 for starts and resumes to under 500ms.
Share update with 0 linked conversations as well
In Progress
π‘ Feature Request
Almost 2 years ago
Linear
Get notified by email when there are changes.
In Progress
π‘ Feature Request
Almost 2 years ago
Linear
Get notified by email when there are changes.