Skip to content(if available)orjump to list(if available)

Unpacking Cloudflare Workers CPU Performance Benchmarks

Unpacking Cloudflare Workers CPU Performance Benchmarks

21 comments

·October 14, 2025
Visit

syrusakbary

I really appreciated that the tone of the article is about what can be improved, rather than dunking on the competition.

That's what everything is about!

PS: It's awesome to see improvements on the OpenNext implementation, that other providers can also reuse

null

[deleted]

zeroq

This is great PR. Well done to whoever orchestrated that post.

kentonv

Thanks! This was 100% produced and orchestrated by engineers on the Workers team (including me).

zeroq

Well, that only speaks better of higher ups who (a) offered you a space to that and (b) didn't micro managed you into something, like vercels hate piece.

Again, well played, nice fix, nice writeup.

pyrolistical

This is why we need competition and independent benchmarks.

This shames poor performing product/service into action.

Havoc

Good job on taking the L gracefully and doing something constructive about it

synunlimited

Speaking of `JSON` functions that can have drastic performance differences, V8 blog[0] recently had a post about improving `JSON.stringify` performance when you don't pass a `replacer` function. Some of the most used functions with performance pitfalls that are easy to trip into.

0: https://v8.dev/blog/json-stringify

hu3

My take from this article is that SvelteKit is crazy fast and Next.js is a snail

skeptrune

I loved this! Good writeup and very mature response to lots of criticism they took online prior.

nisten

nextjs being 4 times slower latency wise than plain react or even vanilla js is pretty funny

kentonv

The benchmark cases are not comparable to each other. Each does totally different work. They are only meant to compare hosting providers.

kentonv

Correction: The author of the SvelteKit benchmark says it is designed to do the same work as the Next.js one: https://x.com/bmdavis419/status/1978242304432325041

But the "vanilla" benchmark generates some 3x as much HTML and the react one generates half, so they aren't comparable.

auxiliarymoose

Keep in mind that Theo said the Vanilla benchmark was running too fast so he made it "way way slower" so 4x is not representative of a direct comparison

https://youtube.com/clip/UgkxvcydgHKf-76rZasr0ykMZZol57apKp9...

zeroq

nextjs is spring of the web, it optimizes productivity rather than app speed.

and whether you are more productive with it or not is completely up to you.

bradleyg_

Well played Cloudflare.

cmdhaus

[dead]

orliesaurus

cf has to hire people with obsession not benchwarmers that only activate when someone yells at them because of a twitter argument. there i said it.

vercel only exists because cf got lazy. huge fan of CF, and if cloudflare had the attention to details that vercel has, there would be no vercel. fullstop.

CFs docs, repos, video content but also code samples, sdks (lol all the mcp stuff) usually is subpar to vercel's.

its really annoying that nextjs has to be forked and/or patched to work on cloudflare.

weird-eye-issue

CF isn't lazy at all. Their docs often aren't that great but it's because they seem to be prioritizing launching new products and features

nmfisher

Overall I'm quite positive towards core Cloudflare products like Tunnels, Workers, R2, KV etc, but a lot of newer products are often either thoroughly broken (e.g. Cloudflare AI) or unusable due to insufficient documentation (e.g. Email Routing).

After being burned a few times, I think I'm going to ignore any new Cloudflare product for 12 months after stable release. If their products worked as advertised, I'd be willing to pay considerably more. I think their commitment to the free tier is hamstringing them a little bit.

PranaFlux

Grab the popcorn, the Vercel v Cloudflare drama unfolds