Ignoring SMT (as others already mentioned it's not used for AWS Lambda), I also expect different vCPU scaling and they also hint at that in the detailed blog po

Ignoring SMT (as others already mentioned it's not used for AWS Lambda), I also expect different vCPU scaling and they also hint at that in the detailed blog post for this feature [1]: > Workloads using multithreading and multiprocessing, or performing many I/O operations, can experience lower execution time and, as a consequence, even lower costs. [1]: https://aws.amazon.com/blogs/aws/aws-lambda-functions-powered-by-aws-graviton2-processor-run-your-functions-on-arm-and-get-up-to-34-better-price-performance/ https://aws.amazon.com/blogs/aws/aws-lambda-functions-powere...