Durable Object "cold latency"

As I know, durable object is based on workers, so is there so called “cold start latency” for the object worker? Or is it keeping warm forever.


Variables in a Durable Object will maintain state as long as your Durable Object is not evicted from memory. A common pattern is to initialize an object from persistent storage and set class variables the first time it is accessed. Since future accesses are routed to the same object, it is then possible to return any initialized values without making further calls to persistent storage.

Your constructor function will be loaded whenever a DO is not in-memory, so that can be considered a cold start. I imagine the rules for when a DO is considered ‘popular’ enough to stay in-cache are similar to that of a regular Worker.

Thank you, that helps!

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.