4 ms·
When a container is kept warm via " min-instances" but is not receiving requests ("idle"), its CPU costs 10x less than when it's actively processing requests, s
by steren 6y ago
When a container is kept warm via " min-instances" but is not receiving requests ("idle"), its CPU costs 10x less than when it's actively processing requests, see pricing: https://cloud.google.com/run/pricing https://cloud.google.com/run/pricing
- YawningAngel 6y agoHow is this cost saving achieved? At the risk of being reductive, surely the container is either in memory and ready to serve requests or it isn't?
- lights0123 6y agoYou still pay for RAM, just not CPU.
- giovannibonetti 6y agoInteresting, if an idle CPU costs 10x less, it ends up costing the same as 1 GB of memory, which amounts to about US$ 6/month each (Tier 1 pricing). For an app with low usage, you start getting a price that can compete with Heroku.
- jkaplowitz 6y agoI don't see the pricing for idle billable time disclosed on that site, only an indication that there is pricing. Am I missing it, or alternatively, could it be clarified?