Absolute adoration for how this was published, broken down, and discussed. It really improves my trust in the workers team at Cloudflare.
Unpacking Cloudflare Workers CPU Performance Benchmarks
31–40 of 80 posts
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#32Reading this really makes me wonder how does Chrome actually optimize for the plethora of devices running v8 (under Chrome). Definitely involves tricky decisions to be taken for great performance.
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#33I am in the process of porting my web app[1] from NextJS hosted at Vercel to Astro/React hosted at Cloudflare, and something that particularly surprises me is that I can render a web app on every request at “the edge” and have response times of 100-200ms. That is almost as fast as fully static pages.
I have also definitely noticed an improvement in Cloudflare Worker over the last few weeks; cold starts have practically disappeared, and they are significantly more stable in terms of response times.
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#34It’s good that CF is actually trying to improve its platform instead of blaming others for smearing its product. Still, the breakneck pace is a mixed blessing. Things change so fast it’s hard to keep up, and launches often outrun polish. The R2 Data Catalog still lacks Iceberg v3 support; Wrangler has shifted dramatically in just a few months; and Pages seems to be on the way out, leaving me with Workers Assets that are painful to migrate. Configs that worked in Wrangler 3 didn’t carry over cleanly to Wrangler 4, and it feels like Wrangler 5 will introduce yet another interaction model.
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#35It’s good that CF is actually trying to improve its platform instead of blaming others for smearing its product. Still, the breakneck pace is a mixed blessing. Things change so fast it’s hard to keep up, and launches often outrun polish. The R2 Data Catalog still lacks Iceberg v3 support; Wrangler has shifted dramatically in just a few months; and Pages seems to be on the way out, leaving me with Workers Assets that…
Where do you see that "pages seems to be on the way out"? I use pages for a few projects...
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#36It’s good that CF is actually trying to improve its platform instead of blaming others for smearing its product. Still, the breakneck pace is a mixed blessing. Things change so fast it’s hard to keep up, and launches often outrun polish. The R2 Data Catalog still lacks Iceberg v3 support; Wrangler has shifted dramatically in just a few months; and Pages seems to be on the way out, leaving me with Workers Assets that…
Where do you see that "pages seems to be on the way out"? I use pages for a few projects...
CF used to encouraged people to move to Workers instead of using Pages. They recently removed the message in their landing page that said so (just checked, you could visit Wayback Machine to verify), so I guess Pages will still be available anyway. Btw the best thing that Pages gives out is allowing people to use different domain from another domain registry when Workers force user move their domain to CF.
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#37I am in the process of porting my web app[1] from NextJS hosted at Vercel to Astro/React hosted at Cloudflare, and something that particularly surprises me is that I can render a web app on every request at “the edge” and have response times of 100-200ms. That is almost as fast as fully static pages. I have also definitely noticed an improvement in Cloudflare Worker over the last few weeks; cold starts have practical…
Hello! How are you collecting your edge workload to the database? Are you using cloudflare’s database?
I’ve wanted to try out this edge hosting thing but because of the amount of round trips involved between the application and the database, the application performs worse on the edge.
Thanks!
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#38My take from this article is that SvelteKit is crazy fast and Next.js is a snail
I hope a pragmatic framework like SvelteKit, Astro or TanStack replace NextJS complexity vendors soon.
React router is ... an option. but tanstack is a the most promising one to change the status quo.
With the rolldown update coming with vite 8, It is just a matter of time before next. js is forced to fix its issues
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#39I am in the process of porting my web app[1] from NextJS hosted at Vercel to Astro/React hosted at Cloudflare, and something that particularly surprises me is that I can render a web app on every request at “the edge” and have response times of 100-200ms. That is almost as fast as fully static pages. I have also definitely noticed an improvement in Cloudflare Worker over the last few weeks; cold starts have practical…
Hello! How are you collecting your edge workload to the database? Are you using cloudflare’s database? I’ve wanted to try out this edge hosting thing but because of the amount of round trips involved between the application and the database, the application performs worse on the edge. Thanks!
The database is hosted on Railway. I have enabled Smart Placement that should, depending on request time, automatically use an endpoint closer to the database to speed it up. When requesting a route that includes a database request, the response time on the US east coast is around 200ms and closer to 1000ms in Denmark. I am hoping that the Smart Placement will work better when I go live with the app (still in beta) and that it mainly needs more traffic to calculate optimal endpoint placement.
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#40Earlier quoted context omitted.
Where do you see that "pages seems to be on the way out"? I use pages for a few projects...
CF used to encouraged people to move to Workers instead of using Pages. They recently removed the message in their landing page that said so (just checked, you could visit Wayback Machine to verify), so I guess Pages will still be available anyway. Btw the best thing that Pages gives out is allowing people to use different domain from another domain registry when Workers force user move their domain to CF.
Workers require you to use CF as a domain registry? Where is that written and what possible reason do they give for it? That's quite an imposition.