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.
sprt
All 4 comments
Running into the same thing right now. Would be great to have a flag to enable hot vs. cold behavior.
mariotacke
on 27 Apr 2018
Duplicate of #362 Closing
jfuss
on 9 May 2018
@jfuss: you linked the same issue (this) number when you closed this. was that by accident?
mariotacke
on 9 May 2018
@mariotacke Yes that was. Thank you for pointing that out. The actually issue is #239
jfuss
on 9 May 2018
Related issues
cmccoypdx
路
3Comments
terlar
路
3Comments
PhungXuanAnh
路
3Comments
cvuijst
路
3Comments
GerbenRampaart
路
3Comments
Most helpful comment
@mariotacke Yes that was. Thank you for pointing that out. The actually issue is #239