3 ms·

RTT to a local edge is about 100ms. So lets be generous and give it 150ms for TLS handshake. This still doesnt explain the other 500ms-1500ms startup time a ser

• jgrahamc 6y ago
  From the article: It’s impractical to keep everyone’s functions warm in memory all the time. Instead, serverless providers only warm up a function after the first request is received. Then, after a period of inactivity, the function becomes cold again and the cycle continues. For Workers, this has never been much of a problem. In contrast to containers that can spend full seconds spinning up a new containerized process for each function, the isolate technology behind Workers allows it to warm up a function in under 5 milliseconds. So, we've always had very low cold start times, and now we've made them disappear "inside" the TLS handshake.
  • grezql 6y ago
    ok.. so theres a new technology that does this.
    • kentonv 6y ago
      Yes. More here: https://blog.cloudflare.com/cloud-computing-without-containers/ https://blog.cloudflare.com/cloud-computing-without-containe... Or deep dive here: https://www.infoq.com/presentations/cloudflare-v8/ https://www.infoq.com/presentations/cloudflare-v8/ (Disclosure: That's me giving that talk.)
    • deleted 6y ago
      [deleted]