Earlier quoted context omitted.
Yep... you spend hours messing around with docker containers and debugging all the weird build errors. I am less familiar with storing data in a db (for ml hosting concerns), but I'd imagine it would add overhead (as opposed to accessing files on disk). You also have to deal with hosting a db and configuring the schema.
You "spend hours messing around" with everything you don't know or understand at first. One could say the same about writing the software itself. At its core Dockerfiles are just shell scripts with worse syntax, so it's not really that much more to learn. Once you get it done once, you don't have to screw around with it anymore, and you have it on any box you want in seconds. In either case you have to spend hours sc…
Meta AI announces Massive Multilingual Speech code, models for 1000+ languages
181–190 of 232 posts
Re: Meta AI announces Massive Multilingual Speech code, models for 1000+ languages
#182Earlier quoted context omitted.
I'm having trouble imagining what data I would store in a database as opposed to a filesystem if my goal is to experiment with large models like Stable Diffusion.
I would take GP's kind of dogmatic jibber jabber with a grain of salt. There is an unspoken and timeless elegance to the simplicity of running a program from a folder with files as state
Re: Meta AI announces Massive Multilingual Speech code, models for 1000+ languages
#183Imagine if we used these types of models for like 500 years and it locked their vocabulary in time, disallowing any further language blending; then somehow the servers turned off and nobody could communicate across language barriers anymore. Someone should write that down in some sort of short-story involving a really tall structure.
Re: Meta AI announces Massive Multilingual Speech code, models for 1000+ languages
#184fairseq is a fairly missed naming opportunity. C-3PO would have been better.
Re: Meta AI announces Massive Multilingual Speech code, models for 1000+ languages
#185Earlier quoted context omitted.
aws s3 sync + image snapshot
all that costs time :-/ When you're finished working, you got to wait for the syncs to finish (or I guess run them all the time?). For home computer setups, you can simply walk away when you need a break.
The shutdown / stop on an instance is like closing the lid on your laptop. When you start it again it resumes where it was left off. In the mean time the instance doesn’t occupy a VM.
A caveat is you can’t really do this with spot instances. You would need to do a sync and rebuild on start. But, again, scriptable easily.
Re: Meta AI announces Massive Multilingual Speech code, models for 1000+ languages
#186Earlier quoted context omitted.
Besides some great tooling out there if you wanted to roll your own, you can literally rent windows/linux computers, with persistent disks. If you have good internet, you can even use it as a gaming PC, as I do.
Is there an easy way to off-board the persistent disk to cheaper machines when you don't need the gpus? Like imagine, setting up and installing everything with the gpu attached, but when you're not using the gpu or all the cpu cores, you can disconnect them. If you have docs on how to do this, please let me know.
AWS also provides accessible datasets of training data:
https://aws.amazon.com/marketplace/search/results?trk=868d87...
Re: Meta AI announces Massive Multilingual Speech code, models for 1000+ languages
#187The problem with all these model releases is they have no demos or even video of it working. It’s all just download it and run it, like it’s an app.
They're intended for researchers/professionals not consumers, and I'm not sure how a video is going to be helpful? And the issue with a live demo is that these are resource-intensive, they're not just webpages. It's an entire project to figure out how to host them, scale them to handle peaks, pay for them, implement rate-limiting, and so forth. For the intended audience, download-and-run-it doesn't seem like an issue…
Re: Meta AI announces Massive Multilingual Speech code, models for 1000+ languages
#188Re: Meta AI announces Massive Multilingual Speech code, models for 1000+ languages
#189Earlier quoted context omitted.
Wait why is renting a GPU in the cloud not a solution? You can even try multiple options and see which ones are capable enough for your use case. Look into some barebones cloud GPU services, for example Lambda Labs which is significantly cheaper than AWS/GCP but offers basically nothing besides the machine with a GPU. You could even try something like Vast in which people rent out their personal GPU machines for chea…
My annoyance was managing state. I’d have to spend hours installing tools, downloading data, updating code, then when I want to go to bed I have to package it up and store as much as I can on s3 before shutting off the $$ server.
It handles storage, setup, etc for machine learning work loads across several providers - which helps a lot if you need one of the instances that rarely have capacity like 8x A100 pods.
Re: Meta AI announces Massive Multilingual Speech code, models for 1000+ languages
#190I would like to use stuff like this as a side-project. Buy a Nvidia Geforce GPU and stick it into my 24/7 server and play around with it in my free time, to see what can be done. The issue with all these AI models is that there's no information on which GPU is enough for which task. I'm absolutely clueless if a single RTX 4000 SFF with its 20GB VRAM and only 70W of max power usage will be a waste of money, or really…
Wait why is renting a GPU in the cloud not a solution? You can even try multiple options and see which ones are capable enough for your use case. Look into some barebones cloud GPU services, for example Lambda Labs which is significantly cheaper than AWS/GCP but offers basically nothing besides the machine with a GPU. You could even try something like Vast in which people rent out their personal GPU machines for chea…
Edit; on Lambda labs, the only exception seems to be the H100; it would be 1.5 years or so, but even 2 years would still fast enough. I have an A100 which paid itself back; thinking of getting another one.