These benchmarks on @fastly's Compute@Edge vs Cloudflare workers are seriously flawed.The biggest problem is that they conflate network round trip time with “execution at edge” time. CF is measuring cherry-picked RTT instead of edge compute performance. From their blog:
@fastly Our early numbers show @fastly’s Compute@Edge Rust implementation is much faster than Cloudflare’s published numbers for their JavaScript implementation. We will publish comparisons once we have enough data to be statistically significant, because that is kind of important.
@fastly You have to dig into the details of any benchmark because they are rarely simple, and can easily be constructed to suit specific systems. Source: I spent more than a decade working at a web browser company.
To build a meaningful benchmark a great deal of care has to go into setting up the test correctly.
You have to make sure the test doesn't hit artificial limits (for example, free trial resource limits) as primary evidence suggests happened in this case.
The test methodology Cloudflare used is also flawed, even as an RTT comparison. They didn’t publish which CatchPoint nodes were used so, conveniently, no one else can do apples to apples comparisons.
The benchmarks claim to compare @fastly’s JS implementation which is in beta vs CF’s JS, which is not. I wonder why they didn’t measure Rust which is much more mature on our platform than theirs.
I encourage everyone to run their own benchmarks on @fastly, bearing in mind there are CPU limits on free trial accounts. You won’t be able to benchmark on Cloudflare (and we can’t either) because their terms of service forbid it.

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with Laura Thomson

Laura Thomson Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Thank you for your support!

Follow Us on Twitter!