You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have 100s of lambdas. We build outside of SAM using esbuild into single files. When we deploy with SAM it zips up the code, checks the checksum against S3 and then decides whether to update the Lambda or not. This is a pretty slow process for us, and takes ~15m.
Proposal
SAM will zip + checksum + check s3 for each lambda in parallel batches, rather than 1 by 1.
The text was updated successfully, but these errors were encountered:
For your use case, do you have same folders that is been used by different lambda functions? In that sense, we should make sure that parallel uploads won't try to upload same folder in different threads.
Describe your idea/feature/enhancement
We have 100s of lambdas. We build outside of SAM using esbuild into single files. When we deploy with SAM it zips up the code, checks the checksum against S3 and then decides whether to update the Lambda or not. This is a pretty slow process for us, and takes ~15m.
Proposal
SAM will zip + checksum + check s3 for each lambda in parallel batches, rather than 1 by 1.
The text was updated successfully, but these errors were encountered: