Re:Enabling next-generation AI workloads: Announcing TPU v5p...
by WendyTheWillow on Wednesday December 06, 2023 @12:58PM
(#38547315)
FWIW, my experience in AWS, as far as "engineer changes something and breaks your production," is not without its own set of issues. Perhaps the AWS version of this story hasn't impacted you, but AWS also constantly tweaks its services, sometimes to the detriment of its users.
Re:Enabling next-generation AI workloads: Announcing TPU v5p...
by leetharris on Wednesday December 06, 2023 @04:49PM
(#38550009)
I totally believe you. It could absolutely be bad luck / good luck.
I think if you search across the internet you find a lot more GCP horror stories than AWS ones. Considering the market ownership of the two platforms, I'd expect the opposite to be true.
Re:Enabling next-generation AI workloads: Announcing TPU v5p...
by belter on Wednesday December 06, 2023 @02:07PM
(#38548163)
References please.
Re:Enabling next-generation AI workloads: Announcing TPU v5p...
by WendyTheWillow on Wednesday December 06, 2023 @04:03PM
(#38549430)
You want me to provide references for my personal experience?
Re:Enabling next-generation AI workloads: Announcing TPU v5p...
by belter on Thursday December 07, 2023 @09:16AM
(#38556548)
Not necessarily. I would like examples of where "...AWS also constantly tweaks its services, sometimes to the detriment of its users..." so I can be better informed, and make better decisions within my projects.
Re:Enabling next-generation AI workloads: Announcing TPU v5p...
by WendyTheWillow on Thursday December 07, 2023 @01:11PM
(#38559686)
And you thought posting, “references please” would be the best way to get that info?
Also those are examples, or details, even. Not references.
Re:Enabling next-generation AI workloads: Announcing TPU v5p...
by belter on Friday December 08, 2023 @01:47PM
(#38572653)
Are you going to mention, describe or post some examples....Or...keep focusing on the way I asked for it?
Re:Enabling next-generation AI workloads: Announcing TPU v5p...
by WendyTheWillow on Friday December 08, 2023 @02:50PM
(#38573335)
No, because you've been a jerk during this conversation.
Re:Enabling next-generation AI workloads: Announcing TPU v5p...
by matthewcford on Wednesday December 06, 2023 @03:08PM
(#38548837)
I've seen issues with RDS after an update. We were seeing CPU max out; adding more readers didn't help, and in the end, we had to rebuild the entire cluster. This somehow fixed the issue, and CPU use returned to normal levels; we didn't make any code changes to the app.
Re:Enabling next-generation AI workloads: Announcing TPU v5p...
by edgoode on Wednesday December 06, 2023 @01:13PM
(#38547503)
What company is this? Curious if you'd be open to talking about how you manage compute across providers.
Re:Enabling next-generation AI workloads: Announcing TPU v5p...
by freedomben on Wednesday December 06, 2023 @01:21PM
(#38547604)
I'm not GP but have been in this boat. We tried a number of different approaches, and kubernetes was by far the most successful. Terraform to provision the k8s clusters, workloads deployed to k8s. With OpenShift it gets even better, though I left the project before we finished implementation so I can't say how it went in prod. Early tests were very good though. If you're feeling bold you can do a "stretch" cluster which has nodes in different data centers (some on-prem for example, some in the cloud, or all in the cloud but different zones). The latency between the masters and nodes can cause problems though so I wouldn't separate them geographically very far.
At my previous company, we even had an announced partnership with Google and did lots of co-marketing. That doesn't mean much when a GCP engineer changes something in GCP and breaks your production.
I wish it worked out. I liked working in GCP outside of these problems. I really like GKE.