When a worker (isolate) spins up it is actually not 0ms but in the range of 0.1 to 9ms depending on your worker and the server hardware it runs on. The true reason how they achieve 0ms is because your worker spins up during TLS handshake, instead of when HTTP request was received. The handshake will take some time and by the time it finishes, your worker is already started making it 0ms cold start.
Hi Red, this one is good. Now I know which one to choose. Many thanks. By the way, is there any special settings to use isolate, or at the fundamental design Cloudflare has done all for us?
Welcome! Glad you're enjoying some of the content :) It's the "TECKNET Extended Gaming Mouse Pad XXL", you can find it on amazon. Great value for the price.
Good question, although most of the time a new Isolate is created I don't think that is guaranteed. I think it is possible for an Isolate to be reused.
@@RedhwanNacef Thanks, the reason I asked is that this creates a problem of state from the previous invocation leaking through, creating more cognitive overhead for the engineer to take care. If isolates are so fast to create, perhaps Cloudflare should create a new one every time to simplify developers' lives.
@@Tech_Advisor_to_CXOs I'm not sure of the specifics, but this sounds like something like the Cloudflare team would have figured out! I think from the engineer side its safe to make the assumption that every request is stateless, hopefully meaning no overhead.
@@RedhwanNacef This contradicts your earlier message - if the isolate is reused, engineers have to be careful that state in global variables doesn't leak.
![Noob To Max With DRAGON REWORK In Blox Fruits [FULL MOVIE]](http://i.ytimg.com/vi/LnBMOinoOvA/mqdefault.jpg)
When a worker (isolate) spins up it is actually not 0ms but in the range of 0.1 to 9ms depending on your worker and the server hardware it runs on. The true reason how they achieve 0ms is because your worker spins up during TLS handshake, instead of when HTTP request was received. The handshake will take some time and by the time it finishes, your worker is already started making it 0ms cold start.
Hi Red, this one is good. Now I know which one to choose. Many thanks. By the way, is there any special settings to use isolate, or at the fundamental design Cloudflare has done all for us?
Thanks. This is just the design that Cloudflare (and other providers) has, so no extra steps on your end.
Nice one Red!
Thanks!
Hi Red, just found your channel (via the Pulumi video). Thanks for making this content, i'm learning lots! Curious as to what desk mat you have?
Welcome! Glad you're enjoying some of the content :) It's the "TECKNET Extended Gaming Mouse Pad XXL", you can find it on amazon. Great value for the price.
Thank you
Does Cloudflare spin up a new isolate for every request?
Good question, although most of the time a new Isolate is created I don't think that is guaranteed. I think it is possible for an Isolate to be reused.
@@RedhwanNacef Thanks, the reason I asked is that this creates a problem of state from the previous invocation leaking through, creating more cognitive overhead for the engineer to take care. If isolates are so fast to create, perhaps Cloudflare should create a new one every time to simplify developers' lives.
@@Tech_Advisor_to_CXOs I'm not sure of the specifics, but this sounds like something like the Cloudflare team would have figured out! I think from the engineer side its safe to make the assumption that every request is stateless, hopefully meaning no overhead.
@@RedhwanNacef This contradicts your earlier message - if the isolate is reused, engineers have to be careful that state in global variables doesn't leak.
This was COOL
Thanks