Minions is an internal enterprise system already in use at Apple. It pools idle Mac GPUs into a shared compute cluster for ML inference.
There is no distributed execution of a single LLM across multiple GPUs using tensor parallelism here. Instead, it relies on task-level parallelism-breaking down a large workload into independent subtasks that run across separate machines. For example, generating embeddings for a million documents.
I guess for companies this can be nice? Run some inference in the off-hours on the machines that you already have. Could be useful for analytical tasks that don't require to be instant. On the technical side this doesn't seem that groundbreaking for me though.
My warm take is that Apple is leaving a lot of money on the table by not investing in creating an independent supply chain for their chips and building their own cloud. They arguably had the first mover advantage when it came to general purpose arm compute; all they had to do was flood the market and make it easy for anyone to rent it. Not only would they corner a part of the market but perhaps ease demand pressure on other chip manufacturers too.
Apart from straight up buying TSMC's or Samsung's fabs I don't see a way of building a vertically integrated high-end chip supply chain for Apple. At least not on timeframes measured below a decade. And on those time frames the current supply issues will probably be resolved by companies who put all their effort into it instead of just tweaking their bottom line.
They don't get enterprise, A/UX, mkLinux, OS X Server, Mac Pro tower, all gone now.
Swift's main reason to go open source and have good Linux support was naturally for app developers to be able to use it on server side, which naturally wasn't going to be macOS.
I macOS wasn't required for developing iDevices apps, they would surely sell even less desktops.
I don't get it. In the paper it sounds like it's "just" a CRUD DB, then you have some fleet of Macs, and they store inputs and outputs in S3. What's the innovation here? Not trying to poo on this, but it looked like the most basic and obvious approach.
That seems to be the point: you leverage existing workstations on your corporate network and run compute batches at night while they're idle. You don't have to buy any extra servers for your low-priority AI workloads.
We were doing this decades ago with engineer's HP C3600s under their desks. It wasn't AI, just low-priority HPC / fluid stuff batched out to hundreds of workstations.
Apple has released some small models previously that seemed genuinely great, along with some quality research/efforts. I’m just not seeing the same level of depth here, am I missing something?
Basically SETI for AI workloads? At least, this is the impression the landingpage left me with.
I am a bit lost, tbh.
There is no distributed execution of a single LLM across multiple GPUs using tensor parallelism here. Instead, it relies on task-level parallelism-breaking down a large workload into independent subtasks that run across separate machines. For example, generating embeddings for a million documents.
Swift's main reason to go open source and have good Linux support was naturally for app developers to be able to use it on server side, which naturally wasn't going to be macOS.
I macOS wasn't required for developing iDevices apps, they would surely sell even less desktops.
Apple has released some small models previously that seemed genuinely great, along with some quality research/efforts. I’m just not seeing the same level of depth here, am I missing something?
What is it actually like?