4 ms·

And AWS lambda cpu performance is proportional to mem setting https://aws.amazon.com/blogs/compute/operating-lambda-performance-optimization-part-2/ https://a

• capableweb 5y ago
  Giving further proof that if you actually care about increasing throughoutput + saving costs, you won't be anywhere near Lambda. Thanks for the additional resource and confirmation.
  • rualca 5y ago
    You're insisting in a red herring that tries to misrepresent the actual problem and the whole point of this discussion. The whole point is that memory costs money, and the more memory you require, the more you pay. AWS Lambdas is a clear example that demonstrates this, but is not an isolated case. This is the case for all cloud providers selling VM time. All of them. Even bare metal providers charge you more for more memory. Isn't it clear that if your app requires more and more memory, that comes out of your pocket? Is this something that really warrants a debate?
    • Chyzwar 5y ago
      The problem is that the only way to get more CPU, you need to assign more memory to lambda. Most node.js lambdas would have stable idle/low memory usage around 200MB but you get ~1/9of vCPU core, this have severe impact performance. You are forced to overprovision lambdas with more memory, even then performance is still very much a disappointment. People that sold promise of serverless framework should have a special place in hell.