‹ BackHN Continuity

Thread

Show HN: Run an 80B Qwen in 4.3 GB of RAM on a Mac, and a 35B on an iPhone

310 points · 140 comments · leonickson

  1. AHASIC · · focus · HN ↗
    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.
    1. Mistletoe · · focus · HN ↗
      What hardware advances would we need to see for that to happen? It feels like everything in that arena has kind of plateaued.
      1. sudo_cowsay · · focus · HN ↗
        It could be on software side too. OpenAI has certainly not plateaued.
      2. bobbylarrybobby · · focus · HN ↗
        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.
        1. swiftcoder · · focus · HN ↗
          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
        2. [deleted] · · focus · HN ↗

          [deleted]

      3. CircuitSeuss · · focus · HN ↗
        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] <a href="https:&#x2F;&#x2F;youtu.be&#x2F;x26A28DoT-w?t=605" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;x26A28DoT-w?t=605

        1. jsjohnst · · focus · HN ↗
          &gt; This is why even their single core mobile chips in the budget line Neo

          That’s a six core processor. It’s an A18 Pro in the Neo, same chip as on the Iphone 16 Pro

        2. ac29 · · focus · HN ↗
          &gt; 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]

          Unified memory has existed for decades in the PC space, Apple didnt invent it.

          And the test you linked to has nothing to do with unified memory, its a web browser benchmark (almost entirely constrained by single threaded CPU performance that Apple better than competitors at).

      4. ethersteeds · · focus · HN ↗
        I think a major factor is memory bandwidth. Apple has raised it steadily for each M series generation, and that hasn&#x27;t plateaued.

        Nvidia leads in bandwidth and specialized architecture, but local inference takes off when it&#x27;s usably fast at much lower cost and power consumption.

      5. harrouet · · focus · HN ↗
        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 ?

        1. KeplerBoy · · focus · HN ↗
          You don&#x27;t an FPGA if you&#x27;re taping out your own chips. But that is just a MMA accelerator with decent memory bandwidth. No secret sauce here.
          1. harrouet · · focus · HN ↗
            I am talking about reconfigurable gates to implement an LLM in silicon, i.e. an FPGA...
            1. xprnio · · focus · HN ↗
              What might the “parameters&#x2F;layers to gates” ratio look like? My naive and uninformed guess would be that 1B+ parameter would also need a 1B+ gate FPGA, but according to google they typically range from tens of thousands to several million (which would still be a fraction of a billion).
        2. dgently7 · · focus · HN ↗
          why would apple make a chip that could be updated to improve the model when they could just sell you a better chip in the next years device?

          on device llm gives apple the new &quot;better camera&quot; &quot;better screen&quot; race they need to keep people coming back for the latest.

          for average users everything else is tapped out... screens, cameras wifi... all the core stuff is good enough now its hard to feel&#x2F;see the difference model year to model year. embedded llm would let them ship something new and the on device ecosystem advantage is huge. especially as the gpt and claudes get ads and enshittified... the apple on device even if its less &quot;capable&quot; would be so compelling.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.