Machine Learning

1 readers

1 users here now

Community Rules:

Be nice. No offensive behavior, insults or attacks: we encourage a diverse community in which members feel safe and have a voice.
Make your post clear and comprehensive: posts that lack insight or effort will be removed. (ex: questions which are easily googled)
Beginner or career related questions go elsewhere. This community is focused in discussion of research and new projects that advance the state-of-the-art.
Limit self-promotion. Comments and posts should be first and foremost about topics of interest to ML observers and practitioners. Limited self-promotion is tolerated, but the sub is not here as merely a source for free advertisement. Such posts will be removed at the discretion of the mods.

founded 11 months ago

MODERATORS

communick@academy.garden

[D] How did you pick your GPU cloud provider? (alien.top)

submitted 10 months ago by Egor_S@alien.top to c/machinelearning@academy.garden

17 comments fedilink hide all child comments

You want to run some heavy tasks in a cloud using GPUs. What would you do?

What features are the most important for you in a GPU cloud provider? Is it price, availability, GPU models, or something else?
How do you choose an instance type to run? Typically there are dozens of different instances in each provider.
Do you regularly use one or more providers?

you are viewing a single comment's thread
view the rest of the comments

[–] chief167@alien.top 1 points 10 months ago

I find azure terrible for ml in general. They basically force you on databricks, azure ml studio just sucks compared to gcp vertex.

We're now on teradata for mlops, and it's surprisingly ok. High entry cost but overall a lot cheaper than what we used to have on azure/databricks, faster, and better.

We are forced on azure at work, but I used vertex for hobby projects