|
|
|
|
|
by ralph87
2052 days ago
|
|
Just for completeness, updating parent comment's Lambda estimates, not counting provisioned worker costs, and assuming no request takes more than 100 ms. Lambda requests: ((1.5e9 * 4) / 1e6) * .20 = $ 1,200
Lambda CPU (1536 MB): 0.0000025000 * 1.5e9 * 4 = $ 15,000
API Gateway HTTP reqs:
(count): 1.5e9 * 4 = (6 billion)
(first 300m): 300 * 1.0 = $ 300
(next 5700m): 5700 * 0.9 = $ 5,130
LAMBDA MONTHLY TOTAL = $ 21,630
LAMBDA YEARLY TOTAL = $ 259,560
And for comparison: NLB (2x)
(NLB hours 1 month):
2 * 0.0225 * 24 * 30.45 = $ 33
(NCLU hours):
2 * (2280/50) * 0.006 * 24 * 30.45 = $ 399
NLB MONTHLY TOTAL = $ 432
NLB YEARLY TOTAL = $ 5,184
EC2 YEARLY
(if 1 req/vCPU) = $ 253,926
(if 15 reqs/vCPU) = $ 67,704
(if 30 reqs/vCPU) = $ 33,852
Note the "1 req/vCPU" case would require requests to burn 250ms of pure CPU (i.e. not sleeping on IO) each -- which in an equivalent scenario would inflate the Lambda CPU usage by 3x due to the 100ms billing granularity, i.e. an extra $30,000/month.That's an 87% reduction in operational costs in the ideal (and not uncommon!) case, and a minimum of a 59% reduction in the case of a web app from hell burning 250 ms CPU per request. |
|
Now I have dozens of serverless projects for smaller use things because there is still a point where the gross costs just don't matter (as in, if my employer was worried about lambda vs EC2 efficiency, there are probably a few meetings we could cancel or trim the audience of that would make up for it.)
But not at this scale.