Theres any plan to make that quicker? I mean, if i restrict my DO on one region (like on juristiction field, or any other form of restriction) they dont need a global lookup.

On my case, everytime the DO has been evicted i got 300ms+ on the first call and 150ms in the next one, ever without any form of initialization. Its like the information about the DO used on ifFromName is lost and need to be computed again. If i wait one minute after the last call I get this "cold start" ... And because i know that has no initialization on the constructor on that particular DO the additional time must be the ifFromName.

@User What's the latency for a

newUniqueId

from the same colo you're making the requests from using

idFromName

It won't be all that possible to make

idFromName

any faster than it is I would imagine. You need to have some kind of global coordination to know if a name is already assigned. But

newUniqueId

can be much quicker..

Do you have multiple names, or just one?

We could, in the future, let you make a namespace that is entirely restricted to a certain region and would only need to look up in that region

Fair 🙂

It has been discussed but we have a lot of other things to do first

That would actually be pretty cool.. but yeah, can't imagine that is the top concern right now

The same as for the second call using idFromName... like 150ms!

What's the basic structure for an ID? 20 character numeric?

Multiples, one for each user, and for workspaces, and for my indexes, etc....

256 bits / 32 bytes

This "cold start" latency is confusing. The location of your named object should still (most likely) be in the local cache

You can repeat this (recently)?

So if I just passed in a hardcoded variable with 32 bytes, it would be a valid id?

Nope

I did not tested recently, that was one month ago, but i will test that again in few hours.

Well.... Just test that again: The code: Bare DO returning a static hello world. First call: 770ms (very new DO) Second call: 176ms Subsequent calls (1s diff): ~170ms wait +60s after: 265ms Subsequent calls (1s diff): ~170ms wait +30s after: 180ms (ok, just network) Subsequent calls: ~170ms wait +420s after: 485ms Subsequent calls: ~170ms

Seeing a bunch of 503 "The page could not be rendered due to a temporary fault." this morning, anyone else?

for me it's this afternoon but yeah 😅 https://www.cloudflarestatus.com/incidents/fvfnlz7wbrgv

ah, right on, thanks

Would be cool to get Identified workers issues routed into the discord here somewhere in real time

This seems good right?

Ah sorry I misunderstood some of it

Is this a client that would hold connections open like a browser, or plain curl, or what?

I just call the rest api using insomnia....

Basically, if i wait few seconds i get this "cold start"

I've never used Insomnia, it'd be good to know if it keeps a connection open for some time. One way you could see this "cold start" is that your later requests have to establish a new connection to a local CF server, and that server probably has to establish a new connection to the colo where your DO is.

Its just like a curl, the connections is closed after the request. I got similar values using the curl.