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

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

I‘m using Lambdalabs, mostly because I’m working on my own and don’t have a high budget, and they’re the cheapest option I found for what they offer. Additionally, you can create and end instances as you like and are billed for them by the minute, which also helps me.

I‘ve looked at services like AWS and Azure as well, but those seem more like they want you to do everything on their ecosystem. So I’d need to spend probably a week or so figuring out how to use their tools before I can do anything.

On Lambdalabs, you instead upload your SSH public key, and can then access your instances either through SSH or Jupyterlab, and that’s it. Given that all I need to do is set up a venv, clone my repo and run raytune scripts, this is perfect since there’s no unnecessary bloat at all.

As for instance types, 90% of the time I just take whatever is available, since they’re usually almost booked out. But if I have the choice, I adjust it to the type of network I‘m training. For example, some architectures like RNNs or anything that needs Fourier transforms don’t benefit as much from recent hardware as, say, attention layers. So in that case you’re getting better value on an older instance, but if you have a transformer, it’s the other way around.