4 ms·

So is this basically App Engine Flexible Environment with a quirk that it pauses (freezes for later thawing) your container (like GCF or AWS lambda) when not ha

So is this basically App Engine Flexible Environment with a quirk that it pauses (freezes for later thawing) your container (like GCF or AWS lambda) when not handling a request? Would be good to see more info like concurrency limits (80 mentioned in the quota is super low...) and cold start times. Things that affect how useful or not useful this is for handling large bursts.

tgtweak 8y ago
Likely some cascading logic to suspend to nvdimms, then local storage, then spin down entirely if no requests are made for a certain period (with some variable based on instantiation time I'm sure). Mix in machine learning pre-emptive loading for observed request patterns and it's pretty manageable. In order to be able to do that, and to save costly resources (memory and CPU) you need the workload to be interruptible vs flexible environnent which is persistant. In a sense this is closer to lambda but supporting native containers if I read into it correctly.
dhavalshreyas 8y ago
Where do you see that? I'm curious to read more about what happens when the service is "idle". What does freezing mean? What's the latency to resume an idle service?
- 013a 8y ago
  Here: https://cloud.google.com/run/docs/about-concurrency https://cloud.google.com/run/docs/about-concurrency
teraflop 8y ago
> Would be good to see more info like concurrency limits (80 mentioned in the quota is super low...) That's 80 concurrent requests per container.
- ec109685 8y ago
  Versus 1 on Lambda.