Unpacking Cloudflare Workers CPU Performance Benchmarks
blog.cloudflare.com
Unpacking Cloudflare Workers CPU Performance Benchmarks
1–10 of 80 posts
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#2Grab the popcorn, the Vercel v Cloudflare drama unfolds
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#3I 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
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#4I loved this! Good writeup and very mature response to lots of criticism they took online prior.
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#5I 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
[deleted]
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#6Speaking 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.
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#7[dead]
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#8nextjs being 4 times slower latency wise than plain react or even vanilla js is pretty funny
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#9nextjs being 4 times slower latency wise than plain react or even vanilla js is pretty funny
The benchmark cases are not comparable to each other. Each does totally different work. They are only meant to compare hosting providers.
Re: Unpacking Cloudflare Workers CPU Performance Benchmarks
#10Well played Cloudflare.