1 個回答
- 最新
- 最多得票
- 最多評論
1
First execution will always take longer than subsequent requests. Mostly it has to do with the client initialization, regardless if its outside of the Lambda handler the first request must initialize the client. Moreover, DynamoDB makes use of internal metadata caching, which also needs to be populated and can add a couple of extra hops to your first request which increases your overall latency slightly.
You can perhaps use the recently released Common Runtime (CRT) HTTP client for the SDK which boasts the following improvements:
- faster SDK startup time
- smaller memory footprint
- reduced latency time
- connection health management
- DNS load balancing
相關內容
AWS 官方已更新 3 年前
You might also consider SnapStart but it will require using a different Java version.
Thank you Brettski-AWS, but I am using Java 8.
Thank you Leeroy Hannigan, but i need a synchronous client.
Using CRT is only a suggestion, the rest of my answer still stands. You cannot avoid client initialization unless you initialize it in advance. Likewise, you cannot avoid DynamoDB metadata cache misses if you have not been sending requests frequently.