How to improve lambda cold starts
Sep. 24, 2020•0 likes•864 views
Download to read offline
Report
Technology
AWS has improved Lambda cold starts by leaps and bounds in the last year. But for performance-sensitive applications such as user-facing APIs, Lambda cold starts are still a thorn in one’s side, especially when working with languages such as Java and .Net Core. In this webinar, we will dive into strategies for improving cold start latency and how to mitigate them altogether with Provisioned Concurrency, and how Lumigo helps you optimize your use of Provisioned Concurrency.
Yan CuiFollow
More Related Content
What's hot
Serverless ArchitectureElana Krasner
DevOps, Microservices and Serverless ArchitectureMikhail Prudnikov
Debunking serverless mythsYan Cui
Adapting Java for the Serverless World at JUG BarcelonaVadym Kazulkin
Gab2015 nicolas fonrose_costefficiencywithmicrosoftazure.pptxVincent Thavonekham-Pro
Introduction to ServerlessNikolaus Graf
![[AWSKRUG&JAWS-UG Meetup #1] Serverless Real-Time Analysis](https://cdn.slidesharecdn.com/ss_thumbnails/awskrugjawsugmeetupeng-160526114220-thumbnail.jpg?width=2048&height=1162&fit=bounds)
Similar to How to improve lambda cold starts
AWS Lambda SnapStart: Why, How and What AWS Serverless Meetup New York Boston...Vadym Kazulkin
How to reduce cold starts for Java Serverless applications in AWS at InfoShar...Vadym Kazulkin
Serverless in Java Lessons learntKrzysztof Pawlowski
Adopting Java for the Serverless world at Serverless Meetup New York and BostonVadym Kazulkin
Serverless in java Lessons learntKrzysztof Pawlowski
AutoScaling and DrupalPromet Source
More from Yan Cui
How to win the game of trade-offsYan Cui
How to choose the right messaging serviceYan Cui
How to choose the right messaging service for your workloadYan Cui
Patterns and practices for building resilient serverless applications.pdfYan Cui
Lambda and DynamoDB best practicesYan Cui
Lessons from running AppSync in prodYan Cui
Recently uploaded
Document Understanding as Cloud APIs and Generative AI Pre-labeling Extractio...DianaGray10
BuilderAI Proposal_MalesniakMichael Lesniak
Elevate Your Enterprise with FME 23.1Safe Software
Swiss Re Reinsurance Solutions - Claims Automated Rules Engine – Insurer Inno...The Digital Insurer
TEKART CON 2023AdedoyinSamuel1
Accelerating Data Science through Feature Platform, Transformers, and GenAIFeatureByte
How to improve lambda cold starts
- 1. Improving AWS Lambda Cold Starts Yan Cui @theburningmonk Developer Advocate, Lumigo AWS Serverless Hero Author of Production-Ready Serverless
- 2. Lambda autoscales by traffic
- 3. Multi-AZ by default
- 4. MyApiFunction Worker Worker …
- 5. Overloaded servers are a thing of the past
- 6. “cold starts”
- 7. www.youtube.com/watch?v=xmacMfbrG28
- 10. cold start
- 11. find space allocate worker init function module invoke function handler Time Cold Start
- 13. find space allocate worker init function module invoke function handler Time Cold Start out of your control
- 14. find space allocate worker init function module invoke function handler Time Cold Start optimize this
- 15. Q: When should I optimize for cold start time?
- 16. Q: When should I optimize for cold start time? A: When someone is going to notice it
- 17. Background data processing? Don’t bother.
- 18. Web app with stable traffic?
- 20. Workers are reused as much as possible.
- 21. time invocation
- 22. time invocation invocation
- 23. time invocation invocation
- 24. time invocation invocation invocation invocation
- 25. time invocation invocation invocation invocation invocation invocation
- 26. time invocation invocation invocation invocation invocation invocation
- 27. time invocation invocation invocation invocation invocation invocation invocation
- 28. time invocation invocation invocation invocation invocation invocation invocation invocation
- 29. Workers are garbage collected after *5-10 mins of idle. * variable
- 30. time invocation invocation invocation invocation invocation invocation invocation invocation
- 31. time invocation invocation invocation invocation invocation invocation invocation invocation
- 36. traffic keeps workers warm
- 37. Web app with stable traffic? It depends.
- 39. function-a function-b function-c
- 40. function-a function-b function-c cold startzzz!
- 41. It depends. What does the data say? Web app with stable traffic?
- 43. optimize these
- 47. find space allocate worker init function module invoke function handler Time Cold Start optimize this
- 48. User behaviours change. Traffic patterns change. Function behaviours change. Cold starts change.
- 51. platform.lumigo.io/signup
- 52. trace 500K invocations per month for FREE with promo code Yan500 platform.lumigo.io/signup
- 53. Yan Cui http://theburningmonk.com @theburningmonk Developer Advocate @ AWS user since 2009
- 54. Yan Cui http://theburningmonk.com @theburningmonk Independent Consultant advisetraining delivery
- 55. FREQUENCY DURATION
- 56. Either stop cold starts from happening, or make them fast enough it doesn’t matter anyway
- 57. FREQUENCY DURATION dictated by user traffic
- 58. Either stop cold starts from happening, or make them fast enough it doesn’t matter anyway
- 59. Lambda Warmers
- 60. time invocation invocation ping invocation invocation invocation ping ping
- 61. Lambda warmers are ineffective when you have more than one worker
- 63. pay for uptime of warm workers
- 64. Either stop cold starts from happening, or make them fast enough it doesn’t matter anyway
- 65. Q: how do I improve cold start time?
- 66. “use higher memory size”
- 67. “use higher memory size”
- 68. find space allocate worker init function module invoke function handler Time Cold Start Always run at FULL power!
- 69. find space allocate worker init function module invoke function handler Time Cold Start Always run at FULL power! EXCEPT for Provisioned Concurrency
- 70. https://bit.ly/32YoIbC
- 71. https://mikhail.io/serverless/coldstarts/aws/instances/
- 72. https://mikhail.io/serverless/coldstarts/aws/instances/
- 73. “use higher memory size” unless you’re using DotNetCore
- 74. More memory More expensive
- 75. “keep deployment artefact small”
- 77. find space allocate worker init function module invoke function handler Roundtrip time for cold starts
- 78. adds 30-60ms
- 79. adds up to 450ms!
- 81. “keep deployment artefact small”
- 82. doesn’t do anything with the AWS SDK
- 83. 383ms 391ms 402ms 408ms 444ms
- 84. 383ms 391ms 402ms 408ms 444ms bundling AWS SDK adds 30-60ms
- 85. doesn’t do anything with the AWS SDK module resolution (CPU) + Filesystem calls
- 86. loading from Lambda Layer is faster than bundling
- 87. loading from Lambda Layer is faster than bundling loading from the built-in AWS SDK is even faster
- 89. use the built-in AWS SDK* * AWS might update the version without notice
- 90. “What about the other dependencies? Put them in Lambda Layers?”
- 91. sure, but, Lambda Layer has problems…
- 92. still need dependencies for local tests
- 93. you need 2 deployments instead of 1… 1 for the layer, and 1 for the service
- 94. no semantic versioning
- 95. doesn’t work with compiled languages
- 96. [Python] use Lambda Layers
- 97. www.npmjs.com/package/serverless-layers
- 98. [Node] use Webpack
- 101. Treeshaking FTW!
- 102. doesn’t do anything with the AWS SDK module resolution (CPU) + Filesystem calls
- 104. require specific clients
- 105. saves 200ms in at least 75% of cases
- 106. webpack still FTW!
- 108. [Node] use Webpack [Node] require only clients you need
- 109. [Node] use Webpack [Node] require only clients you need [Node] package functions individually
- 110. “what about Java?”
- 111. [Java] one JAR per function
- 112. [Java] one JAR per function [Java] reduce dependencies
- 113. [Java] one JAR per function [Java] reduce dependencies [Java] avoid big frameworks like SpringBoot
- 114. [Java] one JAR per function [Java] reduce dependencies [Java] avoid big frameworks like SpringBoot [Java] use AWS SDK v2
- 115. [Java] one JAR per function [Java] reduce dependencies [Java] avoid big frameworks like SpringBoot [Java] use AWS SDK v2 [Java] exclude dependencies you don’t need
- 116. [Java] one JAR per function [Java] reduce dependencies [Java] avoid big frameworks like SpringBoot [Java] use AWS SDK v2 [Java] exclude dependencies you don’t need [Java] remove reflections
- 117. [Java] one JAR per function [Java] reduce dependencies [Java] avoid big frameworks like SpringBoot [Java] use AWS SDK v2 [Java] exclude dependencies you don’t need [Java] remove reflections [Java] avoid dependency injection frameworks
- 118. www.npmjs.com/package/lumigo-cli
- 119. Either stop cold starts from happening, or make them fast enough it doesn’t matter anyway
- 121. Doens’t work on $LATEST alias
- 122. Integrates with Application Auto-Scaling
- 123. time req/s lunch dinner Provisioned Concurrency
- 124. time req/s lunch dinner Provisioned Concurrency On-Demand Concurrency
- 125. https://lumigo.io/blog/provisioned-concurrency-the-end-of-cold-starts/
- 126. there are no silver bullets
- 127. reserved concurrency is a powerful tool IFF you have a cold start problem don’t use it by default
- 130. trace 500K invocations per month for FREE with promo code Yan500 platform.lumigo.io/signup
- 132. @theburningmonk theburningmonk.com github.com/theburningmonk yan@lumigo.io