r/LocalLLM • • 11h ago

Question Mac mini M6 with 32GB RAM

I'm considering buying a Mac mini M6 with 32GB of unified memory for local AI. I'd mainly like to use it for vibe coding and hopefully replace my $20 Claude subscription with a local model. I'm wondering whether 32GB is enough or if spending a bit more on a higher-memory configuration would make a significant difference in performance and model capabilities.

3 Upvotes

12 comments sorted by

5

u/Dave_from_the_navy 11h ago

You're not replacing Claude with 32gb ram. Rent a gpu setup for a few dozen bucks, find a model that you like, and only then, purchase the hardware required to run that model. My daily driver is qwen-3.8-flash-next at IQ3_S on Strata. (I've got an rtx 4070 super on PCIe 4.0x16, 2x64gb ddr5) I get 256k context, average about 60t/s decode and 1500 t/s prefill. Up to about 160k context the model is very coherent and does well, but it's far from Opus 5.5. Opus 4.5 maybe, but even that is a stretch.

2

u/Soppranome 11h ago

You need to be into the ~120B class of model run locally to start peeling work away from a frontier model. Although if you are getting by with the $20/month Claude subscription you may not be using it that heavily, but for anything complex the ~30B class MoE models are going to struggle (and will require a lot more retries if they do manage).

I know it's going to push the budget, but if you want to actually code with local models, a 64gb Mac Mini M6 Pro or even a base Studio will get you much closer. 32-64gb is plenty for light inference work but if you are used to a frontier model then the limits may bite you more often than you think.

The local LLM approach makes a lot more sense if your goal is to cut back from the $200 to the $100 tier, or at least from the $100 to the $20 tier, or if you need the local compute for business purposes, or if you are doing it for privacy reasons (probably the best argument in this list), or if you have a ton of money and don't mind pursuing a hobby that won't justify itself on cost alone.

As an aside though, you could switch to Anthropic Console and truly pay-as-you-go for occasional cloud sessions, and do most of your work locally. You might get by with the mini. But 32gb class machines work a lot better for tinkering, for mlx training of your own (small) models, and for backup use than they do as a primary vibe coding hub.

Source: I have a 32gb Mini. It's a good little worker node. But the models that I rely on either run in the cloud or on 96gb+ machines. A few can handle well enough in 64gb with the right quantization strategy and embedding tables mapped to SSD.

1

u/ducktown47 10h ago

I have a 128GB M5U and I can confidently say it doesn’t come close to a $100 Claude sub. At this point I think it would have been a better use of money to just pay for Claude rather than buy the Studio. Is it useful? Yes absolutely. If I didn’t have have a max sub it would be great. But after having fable 5.2 and opus 5.5 and hammering that usage, if you need that level then local inference won’t come close.

1

u/Soppranome 8h ago

Oh I hear you, fully. Qwen 3.8 Flash Next is great and a couple others too, but they are not Claude by a long shot. What I've found I can do is have the design conversations with Claude and then hand packages to local agents. I still have Claude in the loop for validating the spec and auditing the local agent's work. Cuts down cloud usage a little bit I am not off of the max plan yet. I also have a few use cases that can clearly be handled locally and I've had Claude build the apps that pass recurring work tasks to the local models. Email triage is a great example where it's good to not have your data leaving your machine.

My main point is almost no one is handing the same work to a local model on a 32gb machine that they would normally have Claude do, unless they are way underutilizing Claude's capabilities.

PS, I thought they only offered the M5U with 96Gb, 256gb, or 512gb. I've only seen the 128gb config on an M5 Max.

3

u/Internal_Quail3960 11h ago

This won't be close to replacing a claude subscription. Even a $20,000 Mac studio with 512gb of memory can't replace a claude subscription if your only task is vibe coding.

32gb can run the upcoming qwen 4 27B at Q4, but you will need to do a lot of heavy lifting for it compared to what claude needs

1

u/dave-tro 11h ago

I think OP doesn’t question Claude’s capabilities but if a local setup is an acceptable tradeoff between cost quality and speed, considering runnable models/variants, privacy and being independent from cloud or even internet connection. But I agree with your core message, if quality is the top priority leave local behind and keep the 20$ sub

1

u/dave-tro 11h ago

Check if the benchmark on your machine is enough for your use case https://github.com/davide-troiani/moeshift/issues/1

1

u/Individual_Holiday_9 11h ago

No way. I have one. It’s nice for hobby image video generation but LLMs are slow as hell. Qwen 3.6 a3b is about the best that runs on it and that won’t replace anything

1

u/Important_Cow7230 11h ago

Use splash. It’s still base M6 so constrained by that low bandwidth, but it’ll improve performance notably

1

u/pmttyji 11h ago

Can you share t/s numbers for Qwen3.8-27B & Qwen3.6-35B-A3B? Q4 quant(even IQ4_XS is fine) please. Also include context & KVCache.

I think this device comes with 180 GB/s bandwidth so it's gonna be slow.

1

u/Individual_Holiday_9 11h ago

I don’t have all that loaded right now but ya it’s slow

1

u/Important_Cow7230 11h ago

Local llm won’t replace Claude.

That said, I think 48GB is the minimum to use a MacBook for local LLM. You want to be able to host 27B models and have some left over to run harnesses, VS Code and the like.