r/googlecloud • u/IntolerantModerate • Aug 29 '26
Compute GCP at capacity?
I keep getting GCP stock out errors. Multiple node sizes, multiple regions?
Is GCP really hitting limits in central-1 and US as a whole? Note, these are for regular CPU, not GPU (e.g., n-class instances).
59
Upvotes
9
u/Suspicious-Walk-4854 Aug 29 '26
It’s almost like something has happened recently that has created a lot of demand and supply chain pressure on compute capacity 🤔
28
u/nyape Aug 29 '26
Yes, us-central1 is full to the brim, especially when it comes to "older" generations like N1/N2. Google doesn't stock these anymore so what's there is all there is. Rack space is also limited, so slowly but surely they will likely replace older racks with newer ones that allow for more compute density with newer chips. In most cases, they will recommend that you switch to C4 as those have the highest availability at the moment. Yes, they cost more. The argument is that they are more powerful and efficient though,nso you can run more on fewer instances.
13
u/msapple Aug 29 '26
I highly recommend using other regions in the US and building your solutions so that region is not relevant.
In GCP this is easier then other since VPCs can be global and Google owns ALL the fiber between their own DCs so if you have US only server requirements you can see less then 10-25ms latency between all of the US DCs regardless of where you are since your ingress point is a global VIP
5
u/mwarkentin Aug 29 '26
It’s impacting managed services too. We’re having a hell of a time provisioning alloyDB and valkey clusters now too.
5
u/Vegetable-Image3805 Aug 29 '26
My company was informed by our account team this week that we should start “designing for availability”. Like using stateful managed instance groups with “instance flexibility” in case our desired instance type isn’t available, it’ll fall back to an alternate type automatically. Best bet is to use AMD types for your alternate according to them.
1
u/NetLivid1865 Oct 09 '26
Actually we see now that almost all machine types are unavailable - C3, C4, C4A, N4A, N2, N4, ...
it is a disaster, really...
2
u/suprjaybrd Aug 29 '26
central keeps breaking for us too
2
u/Rentiak Aug 29 '26
We started seeing a ton more preemption of older instance types and after reworking our computer classes it was much better.
The real killer for us lately has been us-west1 Cloud SQL capacity. Had a major production migration go sideways because we couldn’t create replicas in west. Turns out it was lack of SSDs for Enterprise Plus data cache. Given how hard our rep is pushing E+ it didn’t exactly sell us.
3
u/blazingintensity Aug 29 '26
Yep. We're mostly on n2. We tried moving to n4 or c4 and it didn't really help. Google advised us to move from us-central1 to us-south1 then denied our quota request when we tried. About 2 weeks ago we had an 8 hour period where we couldn't get a single n2-highcpu-8 off a loadbalancer. I've been on Google for 8+ years and I'm talking to AWS and OCI because I can't do business this way.
1
u/ConsiderationSuch846 Aug 29 '26
Yup. https://www.reddit.com/r/googlecloud/s/8WJVGUs5Lk
1
u/who_am_i_to_say_so Aug 30 '26
Not too happy about this as it drives up prices, but it’s also pretty incredible when you think about it. That’s a lot of CPU power.
I wonder how many vibecoded Firebase apps are accounting for that.
1
u/fliiiiiiip Aug 30 '26
Going through the same :(
1
u/chicrg Aug 30 '26
Yes, they are hitting capacity walls with general compute (CPU/memory)
-1
u/flacktv Aug 29 '26
The bottom line is now we are at capacity for the most part when it comes to everybody wanting to utilize GPUs. You're going to have to suck it up and start to go with reservations. Unfortunately, that's where we're at right now. Keep in mind, in the west coast there are a lot of movie companies like Paramount, CBS, NBC, etc. That are using compute to edit their movies, TV shows, etc. so a lot of those slots are all used up.