21–30 of 43 posts
Very odd that AWS Lambda/Google Cloud Functions weren't tested. Those CF numbers are impressive though, they beat Lambda cold start by a mile.
They always will; starting an Isolate in v8 will always beat a Docker or VM start. They only work with Javascript, but if you're okay with that, then you will have tiny cold start times.
OP's note about Johannesburg's latency is something I've noticed over the past few weeks in particular. Our servers are hosted in South Africa, yet accessing most of our sites and services from within South Africa causes traffic to be re-routed via other nodes, mostly London (LHR). This is easy to verify by appending cdn-cgi/trace onto a Cloudflare-proxied domain. Something is definitely up with Cloudflare's Johannes…
Nice tip thanks
(Render CEO) Our free services are meant for personal hobby projects that don't need to stay up all the time; I'd love to see tests (and uptime monitoring) for the $7/mo server on Render. Happy to give you credits if it helps.
im curious what the results would be with a more production-like app e.g. if you add prisma connecting to postgres, presumably there's extra latency to create the client. for the fly app, you have a server reusing the client while it's warm. presumably for the cloudflare worker, you're recreating the client per request, but im not 100% on that. how would the latency change then for cold vs warm, and on the other plat…
https://developers.cloudflare.com/hyperdrive/configuration/h...
I feel like this title is misleading compared to the original article. (cc @dang) Fly.io without cold starts (which is a one-line configuration change) is 2x faster than Cloudflare Workers.
Very odd that AWS Lambda/Google Cloud Functions weren't tested. Those CF numbers are impressive though, they beat Lambda cold start by a mile.
I would love to see Wasmer Edge in the next comparison! A summary for the lazy readers: * Cloudflare workers outperforms the rest by a big margin (~80ms avg) * Fly.io cold starts are not great for the Hono use case (~1.5s avg) * Koyeb wraps the requests behind Cloudflare to optimize latency (150ms best case) * Railway localized the app in one region (80ms best case, ~400ms rest) * Render has some challenges scaling f…
That's... no longer a cold start, right?
OP's note about Johannesburg's latency is something I've noticed over the past few weeks in particular. Our servers are hosted in South Africa, yet accessing most of our sites and services from within South Africa causes traffic to be re-routed via other nodes, mostly London (LHR). This is easy to verify by appending cdn-cgi/trace onto a Cloudflare-proxied domain. Something is definitely up with Cloudflare's Johannes…
I would love to see Wasmer Edge in the next comparison! A summary for the lazy readers: * Cloudflare workers outperforms the rest by a big margin (~80ms avg) * Fly.io cold starts are not great for the Hono use case (~1.5s avg) * Koyeb wraps the requests behind Cloudflare to optimize latency (150ms best case) * Railway localized the app in one region (80ms best case, ~400ms rest) * Render has some challenges scaling f…
> only achieve good cold starts by never shutting down the app That's... no longer a cold start, right?