Well no clue what the limit might be, how many DOs do you create per second?

Thanks a lot! So it will be a service to my saas customers to setup sequences for their users. What would be a better way? I want it to work like workers where there is no limit to scaling it.

Around 8?

That actually sounds kind of low…

If DOs stopped creating after 8rps that would be very bad 😅

And I just realized that I broke WDL. Again

In bursts, maybe. But I’m assuming it isn’t supposed to run at that sustained

About 27k an hour

I was hoping to be able to do 1 request = 1 DO as a sort of express step functions like AWS has which allows 6,000 RPS 😅

Dont need anywhere near 6000 rps myself but

You know, you just have me the idea to try to push DO creation to its limits

We all know who to blame when the DO incident starts

Wonder what would happen if I set WDL to update every second…

Yeah, you lol /s

I would maybe suggest doing a DO per customer (either yours or theirs) rather than per email

and if a given customer had multiple scheduled emails, use a different storage key for each, starting with time they needed to be sent

Hey @ckoeninger, just want to check with you, would 450 DO creations per second break anything?

Wanna test something, but also don’t want to actually break something

I'm not sure off the top of my head at what point we start throwing that "limit on how quickly you create new objects"

I certainly wouldn't suggest trying to load test it on a friday evening when my team is trying to verify whether a feature everyone wants is ready to release 😉

I’ll wait for Monday then 😜

Thanks. Will do! Is there a way to calculate what scheduling and triggering one email would cost from a DO perspective?

👀 we do love 🥱 features

it depends somewhat on how much storage you're using for each and how long it stays undeleted, as well as how long the request / alarm itself takes to run

but if you want to do a back of the envelope through each category in https://developers.cloudflare.com/workers/platform/pricing/#durable-objects you'd have 2 requests for the initial setting of the email (worker and DO), a request for the alarm activation, whatever duration associated with both of those, 2 storage writes, a storage read, and a storage delete, and however long you stored the data

Awesome! That doesnt sound very expensive!

Why two storage writes. Just curious haha

The set alarm.. just understood it

I’m building a chatbot and looking at dos for storing some user context, will the do and state live indefinitely?

State will, the DO will not