Logo The David Page
  • Home
  • About
  • North Star
  • Recent Posts
  • Posts
Logo Inverted Logo
  • Posts
  • Cloud
    • AWS
      • CloudFront
        • CloudFront Flat-Rate Migration
      • Networking & VPC
        • Cross-AZ Data Transfer Cost
        • MTU 9001 / PMTUD Black Hole
        • NAT Gateway & S3 Gateway Endpoint
      • DynamoDB
        • DynamoDB On-Demand Ceiling
      • CloudWatch
        • CloudWatch Logs Insights Cost
      • S3
        • Glacier Small-Files Cost Trap
        • Incomplete Multipart Uploads
      • IAM
        • iam:PassRole Privilege Escalation
      • EC2
        • HTTP 429 – Gemini API on AWS
        • IMDSv2 Hop Limit / Containers
      • Lambda
        • Lambda arm64 vs x86_64 I/O Benchmark
        • Lambda /tmp Warm Start Persistence
      • RDS
        • RDS Proxy & CloudWatch Cost
    • Azure
      • Front Door
        • WAF Policy ArmResourceId Error
  • Software Engineering
    • System Design
      • System Design Survival Guide
Hero Image
I Benchmarked Lambda arm64 vs x86_64 on an I/O-Bound Workload So You Don't Have To

Graviton is always pitched as cheaper. I wanted to know if it’s also faster — for a boring, I/O-bound Lambda function, not the CPU-crunching demos AWS likes to show off. AWS says faster. I don’t do “trust me bro” benchmarks. AWS markets Lambda on Graviton (arm64) as up to 20% cheaper and faster than x86_64 for “most workloads.” Most of the public benchmarks backing that up are CPU-bound — image compression, number crunching, that kind of thing. But most Lambda functions running in production aren’t doing math, they’re doing I/O: call DynamoDB, call S3, call some other API, then wait.

  • AWS
  • Lambda
  • Graviton
  • arm64
  • Performance
  • Benchmark
  • DynamoDB
  • Node.js
Sunday, August 16, 2026 Read
Hero Image
AWS Lambda's /tmp Directory Isn't as Clean as You Think

Assuming every Lambda invocation runs in a fresh, isolated environment is a very reasonable guess. It’s also wrong. “Fresh environment” is carrying a lot of weight in that sentence. A lot of developers write Lambda functions on the assumption that each invocation starts in a completely clean, isolated sandbox — new environment, empty disk, nothing left behind from whatever ran before. That assumption is exactly what “serverless” seems to promise. It isn’t quite what happens.

  • AWS
  • Lambda
  • Serverless
  • Security
Sunday, August 2, 2026 Read
Navigation
  • About
  • North Star
  • Recent Posts
Contact me:
  • hi@thedavidlee.space

© 2026 David Lee.