I think about provisioned concurrency as something that eliminates the cold starts and not something that saves money. There is a bit of saving if you can keep the lambda function running all the time (100%) utilization, but as you've calculated it becomes quite expensive when the provisioned capacity sits idle.
Answer from Tamás Sallai on Stack OverflowI was trying to setup provisioned concurrency in AWS lambda, and wanted some guidance on the cost overhead that I'll bear.
Let's say I decide to setup provisioned concurrency as 5.
My memory size 3072 MB.
Estimated total cost per month: $0.00000005 (cost per ms for 3072 mb) * 1000*60*60*24*30 (total ms in a month) * 5 (provisioned concurrency) = 648 $
A) is this calculation correct?
B) With every update do I have to deploy a new version and setup concurrency?