Re:Cloud Run adds min instances feature for latency-sensitiv...
by netcyrax on Friday December 11, 2020 @04:55PM
(#25391721)
So if there's something always running .... isn't the same as having on always on server (with auto scaling of some sort)?
[ Parent
| on HN ]
Re:Cloud Run adds min instances feature for latency-sensitiv...
by steren on Friday December 11, 2020 @05:08PM
(#25391965)
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
Re:Cloud Run adds min instances feature for latency-sensitiv...
by jkaplowitz on Friday December 11, 2020 @10:09PM
(#25395025)
I 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?
Re:Cloud Run adds min instances feature for latency-sensitiv...
by giovannibonetti on Friday December 11, 2020 @08:07PM
(#25394090)
Interesting, 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.
Re:Cloud Run adds min instances feature for latency-sensitiv...
by YawningAngel on Friday December 11, 2020 @07:49PM
(#25393921)
How 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?
Re:Cloud Run adds min instances feature for latency-sensitiv...
by lights0123 on Friday December 11, 2020 @08:25PM
(#25394268)
You still pay for RAM, just not CPU.
Re:Cloud Run adds min instances feature for latency-sensitiv...
by davidspiess on Friday December 11, 2020 @05:06PM
(#25391922)
It seems they want to replace their managed AppEngine service through Cloud Run in the long run.
Re:Cloud Run adds min instances feature for latency-sensitiv...
by justicezyx on Friday December 11, 2020 @05:47PM
(#25392566)
Cloud run is developed by the same team that built AppEngine. They share the same technical leadership and a lot of the technical stacks, for example, billing and security (gVisor).
I dont think it's that simple to replace one service with another. It requires a lot of very sensitive dealing with external customers. And one cannot (easily) use the typical "Google deprecation" on a Cloud service offering, either.
So it's complicated. But your impression is not too far from the inclination.
Re:Cloud Run adds min instances feature for latency-sensitiv...
by nojvek on Saturday December 12, 2020 @12:27AM
(#25395834)
I’d imagine google would at-least make both appEngine run on the same core primitives that cloud run uses. So while the public facing api is the same, the internals are replaced. At-least that’s how I’d approach it. Deprecate app-engine in that it will be infinitely supported until the last customer, but all new stuff is advocated to be used on cloud run.
Re:Cloud Run adds min instances feature for latency-sensitiv...
by zadokshi on Friday December 11, 2020 @10:31PM
(#25395204)
This definitely appears to be their trajectory.
One would assume transition from AppEngine to Cloud Run would be directed by establishing a pricing differential that incentivises moving off AppEngine.