3 ms·
> It's not clear at which point Lambda function receives access to more than 2 vCPU cores This is one of the more annoying things about the service. Why can't
by jlund-molfese 4y ago
> It's not clear at which point Lambda function receives access to more than 2 vCPU cores
This is one of the more annoying things about the service. Why can't AWS publish this information? I might get 4 vCPUs at 5308MB today, but there's no guarantee they won't raise that threshold to 6144MB tomorrow and cause my run times to increase. There should be a better way to figure out what my execution environment looks like than trial and error.
- arinlen 4y ago> There should be a better way to figure out what my execution environment looks like than trial and error. To be fair, once you start to be bothered with how many threads you get, I'd argue you are already way outside of AWS Lambda's domain and well inside plain old ECW/ECS territory. Keep in mind that AWS Lambdas are appropriate for a) glue code to plug together AWS events b) offload seldomly-ran background tasks, c) rarely executed tasks, such as a terribly simple REST API that is simpler to develop and maintain as a API Gateway+Lambda app instead of, say, express/spring/flask/whatever. Once your requirements don't unquestionably fit any of these scenarios, you have to take a very hard look at what you're doing to explain why aren't you just rolling your own web service and instead you're opting to both pay a premium and increase your maintenance needs.
- ransom1538 4y agoWell stated. Lambda is a specialized tool. It isn't some generic. Lambda doing image processing is damn impressive [s3 bucket hooks, almost no code, ...]. Lambda doing sql inserts is a tragic disaster [boot latency, hanging queries, ...].