| ▲ | Show HN: Run an 80B Qwen in 4.3 GB of RAM on a Mac, and a 35B on an iPhone(github.com) |
| 163 points by leonickson 16 hours ago | 67 comments |
| |
|
| ▲ | dghlsakjg 5 hours ago | parent | next [-] |
| I know everyone wants to crap all over these setups that are impractical, but this is how progress happens. People will keep plugging away at this and figure out how to avoid wearing the hard drive, how to make it run faster, custom hardware buses etc. Keep going! I personally can't wait for the day when a 1t param model runs off a $200 SSD instead of a $50k rack of Nvidia chips. |
| |
| ▲ | gpt5 3 hours ago | parent | next [-] | | Most people are already used to rely on the internet on basically everything. At best, they download a tiny chunk of entertainment from it when they go on a plane, and as soon as they land they immediately abandon that offline chunk. In addition, LLMs, small or large, are highly parallelizable. This means that running on the same machine/GPUs many requests in parallel is significantly more efficient, and the sum of tok/s will far outweight any single user use case. Those two combined means that unless LLMs reach the state of 'good enough' (TBD), I fully expect the economics and people's interest to align with 99%+ of LLM usage would be in centralized servers. (not dismissing the fact that there are use cases for local LLMs, and that the progress matters). | | |
| ▲ | anon373839 2 hours ago | parent | next [-] | | I suspect the economics favor centralized servers, if you only look at the aggregated cost to serve X number of users' tokens. But we could say the same thing about a lot of the computation that iPhones do locally. They could have been much thinner clients, but instead they now have more compute power than desktops had when iPhones launched. | | |
| ▲ | zozbot234 40 minutes ago | parent | next [-] | | > I suspect the economics favor centralized servers, if you only look at the aggregated cost to serve X number of users' tokens. The economics of real-time, low-latency inference of very large near-SOTA models will heavily favor a centralized setup. But if you can afford to wait for your answer - be it a day, a week, or even more at the extreme low end (or if you just stick to leaner models for your relatively quick replies) the economics start to shift in a very clear way. A slow-going local inference setup relying on cheap SSD offload does not need the high power input of a datacenter rack, and the cooling load is outright trivial - even when working on many requests in parallel, which (in a SSD offload context) is what maximizes throughput even for local inference. These are serious problems for centralized inference that will probably limit the scale at which it can be applied. | |
| ▲ | xyzsparetimexyz an hour ago | parent | prev | next [-] | | A lot of the compute that iPhones do either has high bandwidth requirements (photo editing etc) or low latency requirements (games etc). LLMs are an interesting case where unless you're feeding in images, it's just text | |
| ▲ | gpt5 2 hours ago | parent | prev [-] | | iPhone are in practice more reliant on central servers than ever before. Except for some games, if you take a random person's iPhone it becomes almost useless without internet connection. Which is exactly my point, it's not about compute, it's about people's expecations and priorities. The main driver of the need for higher performance chips on iPhones is its camera and smooth 120fps UI animations, not local processing for apps for almost all people. However, the compute situation just skew it even further when it comes to LLMs. | | |
| ▲ | anon373839 2 hours ago | parent [-] | | Phones are communication devices. So I would always expect connectivity to be central to their use. But that's a different issue than the "inefficiency" of edge computation and whether powerful edge devices can sell (they obviously can). |
|
| |
| ▲ | submeta an hour ago | parent | prev [-] | | I don’t understand the downvotes. It’s perfectly reasonable to disagree, but the argument is laid out clearly. Why not engage with it instead? |
| |
| ▲ | marci an hour ago | parent | prev | next [-] | | Seems like what Apple's going for with afm3. Their latest model that will be embedded in macOS 27 is a quantized dense 20B that only select between 1 to 4B at inference, based on the prompt, not token by token. If only they could make a 100B or 400B dense that selects ~5 to 15B... | | |
| ▲ | josu 38 minutes ago | parent [-] | | I don't understand, if they are only using a subset of the tokens then it's a sparse model. What do you mean by dense? | | |
| ▲ | l33tman 30 minutes ago | parent [-] | | Could it be some sort of permanently routed MoE where they detect and switch for the whole prompt instead of token by token? |
|
| |
| ▲ | arjie 5 hours ago | parent | prev [-] | | Haha 1T on $50k might be a bit hopeful, mate, even at FP8. But I too am hopeful. | | |
| ▲ | apimade 4 hours ago | parent | next [-] | | 8800 GTX in 2006. Cutting-edge, an insanely powered consumer card for the time. Theoretically around 0.3456 TFLOPS. 1080 GTX in 2016. Cutting-edge, an insanely powerful consumer card for the time. Theoretically around 8.87 to 8.9 TFLOPS. 5090 RTX in 2026. Cutting-edge, an insanely powerful consumer card for today.
Theoretically around 104.8 TFLOPS. In the same timeframe mobile processor CPU's went from 0.001 TFLOPS, to today's Apple's A19 Pro chip which delivers 2.074 TFLOPS. That's _without_ getting into ASIC's, or purpose-built hardware like Taalas's model on silicon HC1, or generic AI dies like what they're planning with HC2 or Cerebras, which will massively compress the timeline. | | |
| ▲ | flaburgan 2 hours ago | parent | next [-] | | Yeah but here you describing the opposite phenomenon. You're saying that the hardware is going to become cheaper and more powerful with the years, to the point a current State of the Art model from today will run on a normal consumer hardware in ten years. What people are trying to do now is the opposite, optimize the software as much as possible so that it does not need the best hardware but the normal one we currently have. As if we were trying to make a current AAA game to run smoothly on the 1080 GTX of your example. | |
| ▲ | foxrider 30 minutes ago | parent | prev | next [-] | | Speaking of ASICs - how likely is it that as models get better we'll see someone baking a whole model directly into the silicon? It's like having l0 cache. | | |
| ▲ | SJC_Hacker 5 minutes ago | parent [-] | | You could do it but there would be no point, The only advantage over would be power consumption. And it would be quite expensive. At the rate models are improving, it would be obsolete in six months. |
| |
| ▲ | root_axis 2 hours ago | parent | prev | next [-] | | Ok, now do memory capacity and bandwidth - the things that actually constraint local LLMs. | | |
| ▲ | apimade an hour ago | parent [-] | | 8800 GTX in 2006: 768 MB of GDDR3, with 86.4 GB/s of theoretical memory bandwidth. GTX 1080 in 2016: 8 GB of GDDR5X, with 320 GB/s. RTX 5090 in 2026: 32 GB of GDDR7, with 1.792 TB/s. This is fun, what's next?! PCI 8.0 is breaking 1TB/s, GDDR7 is 1TB/s. With just the _current_ timeline, things are looking like they'll compress once we get over this initial lump. |
| |
| ▲ | jack_pp 2 hours ago | parent | prev | next [-] | | Isn't there such a thing as low hanging fruit? Aren't we already approaching theoretical physical limits? We're at 2nm | | |
| ▲ | kaashif an hour ago | parent | next [-] | | (1) Yes. (2) Are you saying that you think we're at the limits of computing in general, or that specific technology? We know, for example, that a human brain level intelligence is possible to run on a human brain. We are nowhere near that. And actually that's not even a physical limit necessarily. But that is...not a low hanging fruit. | | |
| ▲ | fragmede an hour ago | parent [-] | | > We are nowhere near that. Nowhere? | | |
| ▲ | darkwater 35 minutes ago | parent [-] | | Leaving aside the discussion on LLMs intelligence vs human intelligence, on a purely energy consumption level we are definitely and without any possible questioning nowhere near that indeed. |
|
| |
| ▲ | cvak an hour ago | parent | prev [-] | | we are not at 2nm, we just call it that. |
| |
| ▲ | zmmmmm 2 hours ago | parent | prev | next [-] | | Sadly while the FLOPS are increasing nicely, total graphics memory is stalled in consumer cards by comparison. | |
| ▲ | xbmcuser 2 hours ago | parent | prev | next [-] | | We will see such power and price now only when AI market crashes or China reaches node parity and goes after market share as currently the way they are buying out most of the latest node production the consumer prices will only be palatable to the very rich or we will need to be happy with older slower nodes | |
| ▲ | cududa 3 hours ago | parent | prev | next [-] | | Just a note that I think the direction most people are paying attention to is memory bandwidth; thats the real bottleneck and “number go up” but also constraint people are designing around | |
| ▲ | formerly_proven 2 hours ago | parent | prev [-] | | Except the 499$ of a 1080 GTX inflation-adjusted only buys you a 5070 or 5070 Ti even by MSRP. |
| |
| ▲ | hedora 4 hours ago | parent | prev | next [-] | | AMD already demonstrated 1T on strix halo clusters. << $10K at original MSRP. | |
| ▲ | sh3rl0ck an hour ago | parent | prev [-] | | We'd bought 4 x $11K Mac Studios at my college and via exo, we had Kimi K2.5 at 30 TPS. Not too wild an idea! |
|
|
|
| ▲ | gitpusher42 2 hours ago | parent | prev | next [-] |
| Thank you for using TurboFieldfare as a starting point for this project and thank you for mentioning it at the README.
I am glad it inspired more people to explore area of on-device AI further! |
|
| ▲ | AHASIC 5 hours ago | parent | prev | next [-] |
| I read a comment on here a few months back I wanna restate. Basically, there is a good chance that Apple is betting that the LLMs in the future will be so efficient that those that consumers will use everyday will be easily computed by the iPhone or even bigger ones on Macs. Honestly makes the most sense that we are heading that way in a few years latest. |
| |
| ▲ | greggsy 3 hours ago | parent | next [-] | | The innovation curve doesn’t always reward the innovators.
It pays to let others test the waters before you. | | |
| ▲ | dd8601fn 2 hours ago | parent [-] | | Especially if you’re Apple and your expertise and reputation is in making privacy conscious devices and cloud services that are exceptionally user friendly. Then you go to the AI labs and say, “We see you’ve spent a trillion dollars on that model… we’ll write you a check today to let us run it how we want.” Skips the ugly horse race and massive risk while focusing on what they do better than anyone. And they’re the only ones who have cultivated the trust with normal people to be able to say, “We now have the only AI service that can safely reference your personal info without giving it all to strangers.” They could possibly end up the second biggest winners in this insane hype cycle… without having had to compete on making a sota model. |
| |
| ▲ | Mistletoe 5 hours ago | parent | prev [-] | | What hardware advances would we need to see for that to happen? It feels like everything in that arena has kind of plateaued. | | |
| ▲ | CircuitSeuss 4 hours ago | parent | next [-] | | A lot of this will come from co-optimizing hardware and low level machine code for this specific use case… something apple is coincidently very good at. Apple has worked very hard to make unified memory a feasible approach, and the benefits of that are pretty clear in apple silicon- that efficiency not only results in power and therefore thermal gains, but also in a significantly faster full loop per process: or a faster time to token. This is why even their single core mobile chips in the budget line Neo out perform PC processors with several times more threads and RAM[1]. Turns out, unified memory lets you have a whole lot more control over things like RAM bussing and core use for specific workflows. Speculatively, a unified memory approach could also allow you to more easily integrate things like ReRAM to solve the current memory swapping bottleneck. Let’s say a friend of mine works hardware at apple and works on exactly this… on device processing is the future I’m betting on. [1] https://youtu.be/x26A28DoT-w?t=605 | |
| ▲ | bobbylarrybobby 4 hours ago | parent | prev | next [-] | | The models themselves have far from plateaued. Maybe someone finds a way to get a really capable model down to, say, 12GB of ram. Then we'd be in business. | | |
| ▲ | swiftcoder 3 hours ago | parent [-] | | Agreed. We've just seen DeepSeek post-train their ~300 billion parameter flash model to outperform their 1.6 trillion parameter pro model, in the space of a few months. There would seem to still be quite a few opportunities on the table to bring big model smarts down to the smaller models |
| |
| ▲ | ethersteeds 3 hours ago | parent | prev | next [-] | | I think a major factor is memory bandwidth. Apple has raised it steadily for each M series generation, and that hasn't plateaued. Nvidia leads in bandwidth and specialized architecture, but local inference takes off when it's usably fast at much lower cost and power consumption. | |
| ▲ | sudo_cowsay 4 hours ago | parent | prev | next [-] | | It could be on software side too. OpenAI has certainly not plateaued. | |
| ▲ | harrouet 2 hours ago | parent | prev [-] | | I could definitely image Apple embedding a kind of LLM-optimized FPGA: slow to load (update) an LLM, but blazing fast at computing tokens. Who needs memory when your model is set in silicon ? | | |
| ▲ | KeplerBoy 18 minutes ago | parent [-] | | You don't an FPGA if you're taping out your own chips. But that is just a MMA accelerator with decent memory bandwidth. No secret sauce here. |
|
|
|
|
| ▲ | throwawayffffas 7 minutes ago | parent | prev | next [-] |
| > One expectation to set honestly Hello Claude! |
|
| ▲ | sallymander an hour ago | parent | prev | next [-] |
| "As far as we know, that is the first time a model of this class has run natively on a phone.". I feel like I've seen a similar statement on a lot of these streaming weight projects. 400b model on an iPhone:
https://x.com/anemll/status/2035901335984611412 |
|
| ▲ | adrianco 3 hours ago | parent | prev | next [-] |
| This looks useful, you can increase the RAM cache so if you have a Mac with 24-32GB it should speed up a lot and still run models that wouldn’t normally fit. I’m going to run some tests… |
|
| ▲ | CyLith 4 hours ago | parent | prev | next [-] |
| I know relatively little about the workings of LLMs, but I keep seeing projects like this that run massive MoE models using very modest amounts of RAM, perhaps excessively so. I wonder, is there a way to make the RAM usage tunable? I have a Macbook with 32 GB of RAM, and it'd be great if I could run the same model but take advantage of the additional RAM to make it run faster. |
| |
| ▲ | fodkodrasz 2 hours ago | parent | next [-] | | > I wonder, is there a way to make the RAM usage tunable? In LM Studio I can tune it by selecting different quantation of the model, by selecting how many layers of the neural net to be loaded to GPU (rest stays in main mem, evaluated by the CPU), and by adjusting context window. | |
| ▲ | zamadatix 4 hours ago | parent | prev | next [-] | | That's about the turning point for just using typical quants for me. Larger still and you can just do the full model. Smaller to this degree and you need all sorts of extra tricks to get anything. | |
| ▲ | ianmurrays 4 hours ago | parent | prev [-] | | I guess you have to know which experts to keep “hot” in ram, which you can’t know beforehand, so there wouldn’t be much gain. | | |
| ▲ | spockz 2 hours ago | parent [-] | | I do wonder if there are some experts that are more likely to be hit. So if the normal optimised setup runs in 12GiB an you have 4GiB extra to spare, you could say “promote the most used X experts to this stable (old gen in GC parlance) region and don’t swap it out. Maybe you could even do something like profiling and remember over multiple sessions (per project/workspace) what the most used agents are and load those up before hand. |
|
|
|
| ▲ | brrrrrm 5 hours ago | parent | prev | next [-] |
| this is cool but like, are we just vibe coding NAND burners at this point? these decode times don't really tell the whole story, because prefill becomes the bottleneck. half an hour to process 10k tokens on an M5 seems... not great |
| |
| ▲ | fsuts 2 hours ago | parent | next [-] | | This is how progress happens, someone gets to 3t/s, the next person gets to6/s and eventually we get to 100t/s. People like this person are laying the foundations. | | |
| ▲ | IsTom an hour ago | parent [-] | | There is a limit how much you can squeeze out of given hardware. Betting on it being closer to 100t/s than 6t/s is only that, a bet. |
| |
| ▲ | kennywinker 5 hours ago | parent | prev [-] | | Not great for coding, or realtime agent interactions. But for background processing tasks overnight? Seems like it’d work pretty well | | |
| ▲ | selcuka 3 hours ago | parent [-] | | I'm pretty sure one can rent a GPU for a few minutes with the electricity cost of leaving an M5 overnight. | | |
| ▲ | hdgvhicv 2 hours ago | parent | next [-] | | Domestic electricity is free nowadays, certainly for most of the year, as solar plus battery covers your usage for a tiny percentage of the cost of your house. | |
| ▲ | kennywinker an hour ago | parent | prev [-] | | Sure. One could. But then one wouldn’t be in control of every step of the process. |
|
|
|
|
| ▲ | jbird99 5 hours ago | parent | prev | next [-] |
| At what, 10 tokens per hour? These disk swapping methods all have the same drawbacks - kill your drive early, and slow as hell. |
| |
| ▲ | throwawayffffas 3 minutes ago | parent | next [-] | | Am I the only one that has no flash lifetime anxiety? I still have drives from more than a decade ago that keep on chugging fine. I remember the time spinning rust was the only option and reliable they weren't. In 30 years of computing I have had more than ten hdds and zero ssds die. | |
| ▲ | kennywinker 5 hours ago | parent | prev | next [-] | | It says very prominently in the post: 4.5-5t/s for 80b on an M5 | |
| ▲ | wat10000 5 hours ago | parent | prev [-] | | Isn’t it only writes that kill drives? | | |
| ▲ | petu 3 hours ago | parent | next [-] | | There's read disturb on SSDs, enough reads will eventually force controller to rewrite the cell and it's neighbours. Practically if you're not streaming weights 24/7 from a full SSD, then it shouldn't be a problem. | | |
| ▲ | zozbot234 an hour ago | parent [-] | | Read disturb ought to be quite rare, especially on a fresh drive that was written only once or a handful of times (WORM-like usage). Practically, it's not likely to be an issue even with very heavy read workloads. |
| |
| ▲ | sudo_cowsay 4 hours ago | parent | prev | next [-] | | Yeah, that's why most of these comments seem weird to me. | |
| ▲ | Alpha3031 4 hours ago | parent | prev [-] | | Yes for NAND, and I suppose nobody is using mechanical hard drives for this. |
|
|
|
| ▲ | crossroadsguy 3 hours ago | parent | prev [-] |
| I see this at the end of the README > Swiftlet was built in collaboration with Claude Code. Did this really happen (some sort of working with Anthropic or Claude Code team) or is it some kind of requirement when you develop some software with Claude Code (I see the other author is: https://github.com/claude), or sort of reuse some of its parts? Is it like someone saying "built in collaboration with VS Code" or ".. in collaboration with <xyz> autocomplete plugin"? Or merely a disclaimer about vibe-coding or AI written tool? |
| |
| ▲ | vermarish 2 hours ago | parent | next [-] | | When you have Claude Code indepedently author commits and PRs and merge them in, it'll always credit itself as an author. I assume it showing up in the README is a byproduct of the same logic. | |
| ▲ | iamflimflam1 3 hours ago | parent | prev [-] | | It means they used Claude code to write the software. |
|