-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Requests are slow #362
Labels
Comments
Running into the same thing right now. Would be great to have a flag to enable hot vs. cold behavior. |
Duplicate of #362 Closing |
@jfuss: you linked the same issue (this) number when you closed this. was that by accident? |
@mariotacke Yes that was. Thank you for pointing that out. The actually issue is #239 |
qingchm
pushed a commit
to qingchm/aws-sam-cli
that referenced
this issue
Sep 17, 2021
* implementation of XRay service graph * update xray service graph file mapper * update comments * add unit tests and addressed commments * refactor: rename class Service to XRayGraphServiceInfo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our team is using SAM Local to test our API locally and requests consistently take around 1 second to execute. It's a major bottleneck for us; the test suite takes about 12 minutes to run and most of that is due to SAM Local, unfortunately.
From what I gather from this issue, the problem is that a new container is spawned every time. Are there any plans for implementing functionality to keep the containers warm (if it's even feasible)? I'd be willing to have a look but I'd need some guidance.
The text was updated successfully, but these errors were encountered: