Unpacking Cloudflare Workers CPU Performance Benchmarks

(blog.cloudflare.com)

151 points | by makepanic 8 hours ago

12 comments

  • syrusakbary 6 hours ago
    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

  • pyrolistical 2 hours ago
    This is why we need competition and independent benchmarks.

    This shames poor performing product/service into action.

  • zeroq 2 hours ago
    This is great PR. Well done to whoever orchestrated that post.
    • kentonv 1 hour ago
      Thanks! This was 100% produced and orchestrated by engineers on the Workers team (including me).
      • zeroq 1 hour ago
        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.

  • Havoc 3 hours ago
    Good job on taking the L gracefully and doing something constructive about it
  • hu3 2 hours ago
    My take from this article is that SvelteKit is crazy fast and Next.js is a snail
  • synunlimited 4 hours ago
    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

  • skeptrune 6 hours ago
    I loved this! Good writeup and very mature response to lots of criticism they took online prior.
  • nisten 4 hours ago
    nextjs being 4 times slower latency wise than plain react or even vanilla js is pretty funny
    • kentonv 4 hours ago
      The benchmark cases are not comparable to each other. Each does totally different work. They are only meant to compare hosting providers.
      • kentonv 4 hours ago
        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 3 hours ago
      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 2 hours ago
      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_ 4 hours ago
    Well played Cloudflare.
  • cmdhaus 4 hours ago
    [dead]
  • orliesaurus 4 hours ago
    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 2 hours ago
      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 1 hour ago
        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.

        • orliesaurus 1 hour ago
          I also got burned and yes I also feel this way about it, i.e. AutoRAG has huge issues too, not to mention the whole MCP/Agents suite of SDKs...
  • PranaFlux 7 hours ago
    Grab the popcorn, the Vercel v Cloudflare drama unfolds