feat(sdk): optimize cold-start performance #320
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jianzs
added
sdk
🦋 Changeset detectedLatest commit: a1d47be The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
PR conflicted. |
Move import statements to container initialization to enhance runtime performance. By shifting import statements to container initialization rather than at invocation time, we ensure that the import process is completed with more resources available, leading to improved cold-start performance. For the `hello` and `store` path handlers in the quickstart example, this change reduces the latency of the first request from 9s to 2.4s. Increasing the memory size from 128MB to 1024MB further cuts the first request latency down to 1.8s. These measurements were taken in China, and the lambda instance is deployed in the us-east-1 region.
jianzs
force-pushed
the
feat-speedup-cold-start
branch
from
4cfc6cf
to
a1d47be
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Move import statements to container initialization to enhance runtime performance.
By shifting import statements to container initialization rather than at invocation time, we ensure that the import process is completed with more resources available, leading to improved cold-start performance.
For the
helloandstorepath handlers in the quickstart example, this change reduces the latency of the first request from 9s to 2.4s. Increasing the memory size from 128MB to 1024MB further cuts the first request latency down to 1.8s. These measurements were taken in China, and the lambda instance is deployed in the us-east-1 region.The image below shows the execution time of a function when the import statement is placed inside and outside the handler under different memory sizes.
1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):
2. What is the scope of this PR (e.g. component or file name):
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):
5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links: