4 ms·
I'll copy from Twitter[1]: @zackbloom @jgrahamc I can't find it in the docs on AWS site, but I've read that AWS Lambda scales CPU linearly until 1.5GB, then gi
by wolf550e 8y ago
I'll copy from Twitter[1]:
@zackbloom @jgrahamc I can't find it in the docs on AWS site, but I've read that AWS Lambda scales CPU linearly until 1.5GB, then gives you 2nd thread/core and again scales linearly until 3GB. If your PBKDF2 was single threaded, Lambda bigger than 1.5GB is wasted.
11:12 AM - 9 Jul 2018
reply by blog post author[2]:
Replying to @ZTarantov @Cloudflare @jgrahamc
I can't think of a way to test that within the Node code. The only option seems to be to update the C++ version (or some other language) to use multiple threads.
5:16 PM - 9 Jul 2018
1 - https://twitter.com/ZTarantov/status/1016384547364229120 https://twitter.com/ZTarantov/status/1016384547364229120
2 - https://twitter.com/zackbloom/status/1016476314864312321 https://twitter.com/zackbloom/status/1016476314864312321
- Dunedan 8y agoYes, Lambda functions use a second core above 1536MB of memory. Back in the past they had it in their documentation, but removed it at a certain point. Also see: https://stackoverflow.com/questions/34135359/whats-the-maximum-number-of-virtual-processor-cores-available-in-aws-lambda/47582392#47582392 https://stackoverflow.com/questions/34135359/whats-the-maxim...
- manigandham 8y agoIt might not be true any longer if they removed it from the documentation.