3 ms·

I like deno.com, but I am deeply suspicious of their speed test methodology. I hope I am wrong, but it really looks like they are comparing time-to-first-byte (

I like deno.com, but I am deeply suspicious of their speed test methodology. I hope I am wrong, but it really looks like they are comparing time-to-first-byte (TTFB) including TLS, i.e. a 'cold start'. It should not be almost 400 ms from Amsterdam to Virginia on an existing connection. If your app makes one and only one connection, then fair enough, that is a real penalty. Otherwise, this is just the benefit of literally every single CDN. With enough traffic, their edge servers will keep connections open to origin. For serverless, there is no origin -- even better for performance, assuming it has no need for a common data store.

jacobn 4y ago
> With enough traffic, their edge servers will keep connections open to origin. Except AWS CloudFront when used with a custom origin server (whole site acceleration) - their "clever" load distribution algorithm requires inordinate amounts of traffic for effective origin connection re-use. I run multiple sites in the top 100k websites globally and am getting effectively zero origin connection re-use. Badgered them about it but all I got was a wontfix :-/ Sigh.
- jamesfinlayson 4y ago
  I'm glad it's not just me - I remember trying to improve site response times for a site using CloudFront and I thought I'd done the right thing as far a settings go, but got no improvement.
pier25 4y ago
> It should not be almost 400 ms from Amsterdam to Virginia on an existing connection. Exactly, it should be much closer to 100-150ms. My production server is in AMS and I'm in central Mexico (QRO). The response is around 200ms, often less than that.