> Starting containers on Cloud Run is weirdly slow
What is this about? I assumed a highly throttled cpu or terrible disk performance. A python process that would start in 4 seconds locally could easily take 30 seconds there.
Re:Fly.io Has GPUs Now
by JoshTriplett on Wednesday February 14, 2024 @05:03AM
(#39368270)
Last I checked, Cloud Run isn't actually running real Linux, it's emulating Linux syscalls.
Re:Fly.io Has GPUs Now
by seabrookmx on Thursday February 15, 2024 @02:57AM
(#39380196)
Cloud Run "gen2" runs a microvm (ala lambda) rather than gvisor, so it depends on your settings.
Re:Fly.io Has GPUs Now
by JoshTriplett on Thursday February 15, 2024 @02:50PM
(#39387642)
Ah, good to know, thank you! I hadn't seen the announcement of the second generation environment.
> I'm getting the impression that pure VMs + Nomad would be a way better option
As a long time Nomad fan (disclaimer: now I work at HashiCorp), I would certainly agree. You lose some on the maintenance side because there's stuff for you to deal with that Google could abstract for you, but the added flexibility is probably worth it.
I just use AWS EC2, load balancer, auto scaling groups. The user_data pulls and runs a docker image. To deploy I do an instance refresh which has no downtime. Obvious downside is more configuration than more managed services.
Starting containers on Cloud Run is weirdly slow, and oh boy, how expensive that thing is. I'm getting the impression that pure VMs + Nomad would be a way better option.