on MacOS, mounting /tmp/localstack makes lambdas slow #2515
Labels
Comments
|
Thanks for reporting @yonahforst . Not sure if this is a bug per se, but performance can indeed become a bit slow if you're using large Lambda archives in the mounted tmp folder under MacOS. Would you mind creating a pull request with a small note in the README that describes your fix (perhaps in the Troubleshooting section)? Apart from the documentation change, is there anything else you think we can/should do here? Thanks |
|
Thanks again. A short note on performance and Lambda mounting has now been added to the Troubleshooting part of the README: https://github.com/localstack/localstack#troubleshooting |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type of request: This is a ...
[x] bug report
[ ] feature request
Detailed description
When running localstack on MacOS using the example
docker-compose.yml, Lambda functions can take a long time to start up.I think this is because of existing performance issues with
osxfs, the file system server in Docker for Mac.If your using
LAMBDA_EXECUTOR=docker, the copying of zipped code to newlambci/lambdacontainers can take a very long time.If you're using
serverless-localstack, enablingmountCodesolves the slow copying, but then actually requiring your code inside the lambda function can take a long time (mostly because of node_modules).To solve this, I disabled mounting
/tmp/localstackin mydocker-compose.yml...
Expected behavior
...
Actual behavior
...
Steps to reproduce
Command used to start LocalStack
...
Client code (AWS SDK code snippet, or sequence of "awslocal" commands)
...
The text was updated successfully, but these errors were encountered: