Profiling Code to Identify Bottlenecks in Migrated Nodejs Lambda
Hey, guys. I'm migrating my python AWS lambda to the Effect based Nodejs lambda and noticed that response from new lambda is getting twice longer in the same memory/cpu setup. 300ms vs 150ms in average How can I profile my code to determine bottlenecks?
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
