Use the Lambda executable as the bootstrap when glibc is not required #191
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
marcomagdy
force-pushed
the
no-shell-script
branch
from
5949f19 to
adcbaf5
Compare
|
@bmoffatt and @Stefan9283 PTAL |
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.
This change decreases the cold-start times for functions developed on/for the same environment in which Lambda executes the binary.
When building the function on
provided:al2we don't need to package libc, and also we don't need the bootstrap bash script to start the executable.Previously, at the time it was initially written, it was important to have
LD_LIBRARY_PATHin the environment. But now Lambda environment already sets that for us.In my own measurements, this takes cold-start time down by about 5ms, bringing it to equivalence with Rust.
See https://maxday.github.io/lambda-perf/