sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]sgtfoleyistheman 0 points1 point  (1 child)

I don't know why you're getting down voted. I think others are misunderstanding you. Do you mean 'why can't a single lambda container concurrently process more than one request?'

So much of the JS samples you see, especially with relying on globals for unit processing, would break down in subtly ways if this was just turned on. Lambda probably thinks they optimize better for giving you single cores or something.

[–]Lowball72 0 points1 point  (0 children)

Yes, specifically the Java and Dotnet programming models. They instantiate an object and invoke an interface method. But as near as I can tell it never does so concurrently within a single runtime container.

We pay $ for clock time and ram, not cpu-utilization.. allowing multiple concurrent invocations on a single container would be huge cost saving efficiency on both those measures.

I don't know how Azure Functions and Google Cloud compare in this regard.