# Why Does My Low-Memory Lambda Still Have Long Cold Starts in One Region?

**URL:** <https://forum.serverless.com/t/why-does-my-low-memory-lambda-still-have-long-cold-starts-in-one-region/21305>\
**Category:** Serverless Framework\
**Created:** [July 26, 2025, 12:27pm UTC](https://forum.serverless.com/t/why-does-my-low-memory-lambda-still-have-long-cold-starts-in-one-region/21305 "2025-07-26T12:27:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tisabib](https://avatars.discourse-cdn.com/v4/letter/t/58f4c7/32.png) [@tisabib](https://forum.serverless.com/u/tisabib)\
**Post date:** [July 26, 2025, 12:27pm UTC](https://forum.serverless.com/t/why-does-my-low-memory-lambda-still-have-long-cold-starts-in-one-region/21305/1 "2025-07-26T12:27:31Z")

</div>

Hello

I am seeing an unusual issue with a Lambda function deployed using the Serverless Framework. 🙂Even though the function runs under 100MB of memory during execution & has minimal dependencies; I am still experiencing cold start delays of 4–6 seconds; especially in the `us-east-1` region. 😇

This happens even when the function is set to a higher memory allocation (512MB) and when using the latest Node.js runtime. I was under the impression that low memory usage & fewer dependencies should result in faster cold starts. 🤔

I have already checked common suggestions like bundling with esbuild, trimming dependencies, and using the `package.individually` option in my `serverless.yml` but the cold start time doesn’t improve. When I deploy the same function in another AWS region; the cold start is almost instant. Could there be a region-specific issue / a hidden configuration I’m overlooking in the Serverless Framework setup? 🤔

Checked [Optimizing cold start performance of AWS Lambda using advanced priming strategies with SnapStart | AWS Compute Blog](https://aws.amazon.com/blogs/compute/optimizing-cold-start-performance-of-aws-lambda-using-advanced-priming-strategies-with-snapstart/) guide for reference. I came across a discussion on [what is pl sql](https://www.igmguru.com/blog/what-is-pl-sql), and it made me think about how different cloud-based & traditional approaches to logic execution really are. 😇

Has anyone else experienced similar inconsistent cold start times, and are there specific flags, plugins, or deployment practices that helped resolve it? 🤔I would appreciate any insights or even just confirmation that I am not alone in this weird behavior.

Thank you !!

---

<div class="post-metadata">

**Author:** ![discourse\_ai\_spam](https://avatars.discourse-cdn.com/v4/letter/d/c68b51/32.png) [@discourse\_ai\_spam](https://forum.serverless.com/u/discourse_ai_spam)\
**Post date:** [July 26, 2025, 12:27pm UTC](https://forum.serverless.com/t/why-does-my-low-memory-lambda-still-have-long-cold-starts-in-one-region/21305/2 "2025-07-26T12:27:33Z")

</div>

Unlisted on July 26, 2025, 12:27pm UTC



---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex036/uploads/serverless/original/2X/2/211f6ff09cc9caa0197840dcf84e296f7452618c.png) [@system](https://forum.serverless.com/u/system)\
**Post date:** [July 31, 2025, 2:52pm UTC](https://forum.serverless.com/t/why-does-my-low-memory-lambda-still-have-long-cold-starts-in-one-region/21305/3 "2025-07-31T14:52:15Z")

</div>

Listed on July 31, 2025, 2:52pm UTC


