3 ms·
> This will lower the price for most Lambda@Edge functions Isn't this guaranteed to lower the price for *all* Lambda@Edge functions? What is the case where it
by nrmitchi 6y ago
> This will lower the price for most Lambda@Edge functions
Isn't this guaranteed to lower the price for *all* Lambda@Edge functions? What is the case where it wouldn't result is a <= cost?
- cthalupa 6y agoIf the function still runs in a time evenly divisible by 50ms, the price will remain the same.
- happytoexplain 6y agoMore specifically, if it stops anywhere between 49ms and 50ms in each 50ms chunk. So the price would be the same in 2% of executions, I suppose. Edit: Assuming even distribution of run times within each 50ms chunk - I guess maybe that's a bad assumption.
- paxys 6y agoThat assumes the runtime is evenly distributed, which is probably not the case. But still yeah, there will be some functions that end exactly in multiples of 50ms.
- nrmitchi 6y agoYa, you're right. I interpretted the statement as "for some use cases the price might go up", which was a poor interpretation.
- tclancy 6y agoShout out to the person running `sleep(0.005)` just to make the point.
- paxys 6y agoNormally such announcements are coupled with an increase in per-unit price. Not sure if that is the case here though.
- jen20 6y ago> Normally such announcements are coupled with an increase in per-unit price. Are there any examples of AWS ever having done this? Personally I don't recall any, but would be interested to know!
- lostcolony 6y agoYeah; citation needed. I've never seen an instance of a price increase. I can find multiple forums of people claiming Amazon has never increased prices. The only instance I can find of any cloud provider increasing prices was once in 2015 when Microsoft did in Europe...and while that led to a flurry of "cloud providers are going to increase prices" blog posts and things, calmer heads noted the exchange rates as the likely reason (and, certainly, the claims that prices would increase across the board never came to pass).
- watermelon0 6y agoI remember Google starting to charge for managed Kubernetes clusters a year or two ago, I think the cost went from 0 to 75$ per month.
- temp667 6y agoGoogle has raised prices on all sorts of things - I think AWS is one with rep for not raising prices. Maps API's I think went up pretty big time on google side.