Live data from Hacker News

Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025

chrisebert.net

11–20 of 60 posts

Re: Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025

#11
post #6

Can someone tell me why there isn't almost any laptop with Linux and ARM? Is it more efficient than x86 though

Software/driver compatibility and rational fear of change from users. (My work laptop is one of the few ARM laptops: Thinkpad T14s with Quallcomm Snapdragon Elite)

If you don’t mind me asking, what do you think of that laptop? What kind of workloads do you run and how is battery life? What OS? Would you choose it again?

Re: Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025

#12
Would be interesting to see a benchmark with the rust binary with successively more “bloat” in the binary to separate out how much of the cold start is app start time vs app transfer time. It would also be useful to have the c++ lambda runtime there too; I expect it probably performs similarly to rust.

Tangent: when you have a lambda returning binary data, it’s pretty painful to have to encode it as base64 just so it can be serialized to json for the runtime. To add insult to injury, the base64 encoding is much more likely put you over the response size limits (6MB normally, 1MB via ALB). The c++ lambda runtime (and maybe rust?) lets you return non-JSON and do whatever you want, as it’s just POSTing to an endpoint within the lambda. So you can return a binary payload and just have your client handle the blob.

Re: Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025

#13
post #7

Earlier quoted context omitted.

Chromebooks are essentially this, but not that great for local development.

Depends on which one, and what you want to locally develop.

Is there one that even has a full keyboard?

Re: Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025

#14
post #11
post #6

Earlier quoted context omitted.

Software/driver compatibility and rational fear of change from users. (My work laptop is one of the few ARM laptops: Thinkpad T14s with Quallcomm Snapdragon Elite)

If you don’t mind me asking, what do you think of that laptop? What kind of workloads do you run and how is battery life? What OS? Would you choose it again?

Was trying to install Linux on it, though its not working like a standard x86 laptop (for the installer on debian for example).

Battery is good, hardware is really rock solid (though I dislike the new plastic for the keyboard).

Really can’t complain, it’s nearly as good as my Macbook.

It runs Windows 11 today, and everything I need runs fine (jetbrains, rustc, clang, msvc, terraform and of course python).

I’m a technical CTO with infrastructure background, most of my time is spent in spreadsheets these days unfortunately.

Re: Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025

#15

Earlier quoted context omitted.

Depends on which one, and what you want to locally develop.

Is there one that even has a full keyboard?

HP makes a 17" Chromebook if that's what you're after.

Re: Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025

#16

Can someone tell me why there isn't almost any laptop with Linux and ARM? Is it more efficient than x86 though

How is the bootloader/peripheral compatibility on the non-SBC ARM systems these days? Can you plug in a boot disk on different machine and expect it to just work? My main problem with ARM is that many manufacturers act as if they're special little snowflakes and deserve to have their custom patched kernel/bootloader/whatever.

Re: Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025

#17
I would not be surprised that Rust be faster than Python, but looking at the code of his Benchmarks, I'm not sure that it really means anything.

For example, the "light" test will do calls to "dynamodb". Maybe you benchmark python, or you benchmark the aws sdk implementation with different versions of python, or just you benchmark average dynamodb latencies at different times of the day, ...

And, at least for Python, his cpu and memory test code looks like to be especially specific. For example, if you use "sha256" or any other hashlib, you will not really benchmark python but the C implementation of the hashlib, that might depend on the crypto or gcc libraries or optimization that was used by AWS to build the python binaries.

Re: Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025

#18
Yikes, Node.js did really badly. If this holds up, my take-away would be ...

If I want to use TypeScript for Functions, I should write to the v8 runtimes (Deno, Cloudflare, Supabase, etc) which are much faster due to being much more lightweight.

Re: Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025

#20

One of the easiest hack to reduce your AWS bills is to migrate from x86 to arm64 CPU. Performance difference is negligible, and cost can be upto 50% lower for arm machines. This is for both RDS and general compute (EC2, ECS). Would recommend to all.

How is the performance difference negligible? In my experience, for the same generation of hardware, ARM64 performance is better than the AMD64 one.

AFAIK ARM64 is around 20% cheaper, not sure where you got the 50%.

Post reply on HN