Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Unpacking Cloudflare Workers CPU Performance Benchmarks

blog.cloudflare.com

Post reply on HN
Print view View original

21–30 of 80 posts

Re: Unpacking Cloudflare Workers CPU Performance Benchmarks

#21

Post by nmfisher »

weird-eye-issue wrote: post #16
orliesaurus wrote: post #12

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. it…

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

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.

Re: Unpacking Cloudflare Workers CPU Performance Benchmarks

#22

Post by zeroq »

kentonv wrote: post #20
zeroq wrote: post #19

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

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

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.

Re: Unpacking Cloudflare Workers CPU Performance Benchmarks

#23

Post by orliesaurus »

nmfisher wrote: post #21
weird-eye-issue wrote: post #16

Earlier quoted context omitted.

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

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 wil…

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...

Re: Unpacking Cloudflare Workers CPU Performance Benchmarks

#24

Post by eastdakota »

zeroq wrote: post #22
kentonv wrote: post #20

Earlier quoted context omitted.

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

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.

Blog run by the engineering team. I wouldn’t even know how to veto a post if I wanted to. Not in our DNA.

Re: Unpacking Cloudflare Workers CPU Performance Benchmarks

#29

Post by weird-eye-issue »

nmfisher wrote: post #21
weird-eye-issue wrote: post #16

Earlier quoted context omitted.

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

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 wil…

Yeah I just use Workers and Durable Objects. Stuff like Queues built on DO is better to just use DO

Re: Unpacking Cloudflare Workers CPU Performance Benchmarks

#30

Post by Waterluvian »

eastdakota wrote: post #24
zeroq wrote: post #22

Earlier quoted context omitted.

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.

Blog run by the engineering team. I wouldn’t even know how to veto a post if I wanted to. Not in our DNA.

Is there any secret beyond what I’m guessing is “hire the right people and then trust them”?
Post reply on HN