An image-conversion Lambda function takes too long.
Improve CPU and memory resources without changing the code, then measure the result.
Which adjustment is most appropriate?
Increasing a Lambda function's memory setting also changes its allocated CPU and other resources, so performance and cost can be measured and tuned together.
Detailed explanation
Zero concurrency prevents execution and cannot improve processing time.
Zero concurrency prevents execution and cannot improve processing time.
A bucket name does not affect Lambda execution resources.
A bucket name does not affect Lambda execution resources.
Permissions affect authorization, not the function's CPU or memory allocation.
Permissions affect authorization, not the function's CPU or memory allocation.
Lambda allocates more CPU and related resources as the configured memory increases.
Lambda allocates more CPU and related resources as the configured memory increases.
Check official documentation
Compare the following points with the official documentation.
AWS Lambdaのメモリ設定と実行環境リソースの公式説明を確認する。
What to confirm
Lambdaの性能調整軸としてメモリ設定を選び、実測で最適化できる。
Key points
- AWS Lambda
- Memory setting
- CPU allocation
Notes
- Environment: AWS公式Lambdaドキュメントの確認
- Confirm current AWS service behavior and architecture guidance in the official documentation.
Foundation review
Measure and tune
Increase memory, measure duration and cost, and then choose the best configuration instead of changing permissions.
Resource versus authorization
Execution resources affect speed; an IAM role affects what the function may call.