Hey everyone! I'm running into a bit of an issue with my Node.js Lambda function that uses the AWS SDK for DynamoDB. When the Lambda function is cold, the first read from DynamoDB takes an excruciatingly long time—ranging from 800ms to over 2 seconds. This delay happens not because of DynamoDB itself, but due to several factors like the Lambda spin-up, Node.js runtime booting, SDK loading, and more. I've measured the cold start durations and they're pretty high, but once the function is warm, it executes the DynamoDB read in under 120ms. I'm currently keeping my Lambda warm by pinging it every 5 minutes, but that doesn't feel like a sustainable solution. What cleaner fixes do you all suggest? Provisioned concurrency feels too pricey for my low-traffic use, and SnapStart isn't yet available for Node.js. Any tips to speed up the cold init phase?
0 Answers
There is no answer to this question yet. If you know the answer or can offer some help, please use the form below.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically