Re:AWS Lambda pricing now per ms
by throwaway894345 on Tuesday December 01, 2020 @01:25PM
(#25268072)
Wow, I haven’t read yet, but I’m very curious if this affects the size limits on the lambdas. I’ve tried to build lambdas for a small Python use case, but by the time I imported pandas and a few other libraries I exceeded the 250 mb limit and migrated to ECS/Fargate, but the startup times were much longer.
[ Parent
| on HN ]
https://twitter.com/chrismunns/status/1333825503464214530
Docker containers can be up to 10gb, traditional lambdas are still limited to 250mb.
Thats me. We've got some fun things we do behind the scenes to keep Lambda container image support snappy. SO yes, up to 10gb artifacts with container image support.
[dead]
Re:AWS Lambda pricing now per ms
by throwaway894345 on Tuesday December 01, 2020 @03:51PM
(#25269728)
I don’t know how this is related to my comment. In my case we used a slow language (although Python’s poor performance and its large bundle sizes are only indirectly related at best) and we had to spend a lot more by moving to ECS/Fargate. If we were using Go, our bundle sizes would’ve been 30x smaller (I checked) and would’ve fit in a lambda easily. Not only would it have fit easily, it would have made a lot of progress before the Python version even finished importing its dependencies. And in top of all of that, it would have out-performed the Python version by a good order of magnitude. If anything, my anecdote supports the idea that Amazon wants you to use fast languages, especially now that they offer per-ms pricing for lambdas.