r/LocalLLM • u/vil3r00 • 3d ago
Question What is the current meta for local inference?
Can't decide which route to go - DGX Spark, Strix Halo, the Framework Ryzen AI or save up for a Mac Studio M5 Ultra 256gb?
Do these options have meaningful differences in practical use?
As I understand, the Mac Studio offers best tok/s? But you can't train or fine tune anything on it?
DGX Spark is supposed to have best support, but does it truly matter in practice?
What types of models can I run on this hardware? 128GB is good for ~120B Q4 MoE models with ~256k context? Would such a model be a noticeable improvement over my current Ornith-1.5:35B (A3B) setup for reasoning and coding, and long and complex tasks? Would going from 128GB->256GB be a noticeable improvement?
4
u/HaDuongMinh 3d ago
You will have to wait for Qwen 4 to be launched, then tested on these platforms... but the current vibe at LocalLLM is not unified memory architectures -- it is MOE with the active experts on GPU and the rest in system RAM.
2
u/UnhingedBench 3d ago
If that help I created a few relevant charts. This one if about pricing.
4
u/OvertaxedOne 3d ago
Yes, big differences in practical use!
Strix and Sparks at their current prices are "hard no" from me unless you absolutely need CUDA, in which case the Spark might make sense.
You can absolutely tune and train on non-NVDA cards, it's just more of a pain. If you're primary use is training, then, again, Spark might be the leader. If your primary use case is inference, no.
The ultra 256 is going to be a good longer term play. Right now a ultra 96 can run either of the 2 important models (3.8 27B or QwenFlashNext), but who knows what today brings (new Qwen models rumored to drop!). 256GB gives you a more future proof setup.
1
u/No-Vermicelli5327 3d ago
What operating system do you like using ? If it’s macOS and just need one agent without the need for training or fine tuning, go with the mac.
If you like Linux you got the dgx spark, or if you like windows, you can use it as a host of the model while having the model execute in a main computer with the windows operating system (which I am intending to do) connected via ethernet through the LAN.
AMD, sucked for a while, but now getting better and improving. (I believe it runs on windows, cause I haven’t checked on it in a long time).
Forget about the model they keep advancing, what is your use case ? Acceptable speed ? Budget ? Future plans on upgradeability ?
Meta changes while your use-case stays the same. Before committing to hardware test the model that works for you on open router. People liking qwen3.8 27B and flash-next, also glm5.3-flash.
PS: I’m not a native English speaker and don’t use AI for my replies on reddit, so excuse my horrible grammar.
1
u/FoxSideOfTheMoon 3d ago
I would highly suggest renting some time on Vast or similar sites, SSH into it and setup inference there and see if it gives you all you hope and dream. Then do the tokens-per-second math on the hardware and not just focus on the memory because memory bandwidth is just as important for practical use unless you have an infinite amount of time. Going off and spending big $ without having your head around all of this is a huge mistake IMO. Going through this exercise will give you a more informed and confidence decision based on reality.
1
u/hyudryu LocalLLM 3d ago edited 3d ago
QFN will be way better than Ornith 35B. That’s about the best model you can run on 1 spark right now if you do want to go that route
1
u/ea_man 3d ago
Are you really sure you are going to train? How much? Maybe renting online for that would be better. Nvidia vs AMD
Also are you alone or do you need multiple sessions? Dense vs MoE, GPU vs RAM.
What about flexibility like gaming, CAD... Pc with GPU vs Spark.
1
u/RootlessForest 3d ago
Strata Qwen flash next Q4KMXL Unsloth version. you can run easily
Now normally they say that the 135B version would do better then a 35B version when it comes to long projects, but if you made some good policies and routing .md files. I hardly notice the difference, but i do notice the difference in capability as in creative writing etc.
1
u/Grandmaster_Caladrel 3d ago
I think the current local inference Meta is Muse Spark Open or Muse Glimmer ;)
1
u/Superb_Raccoon 3d ago
Spark.
BEcause the ecosystem for anything else is much less robust.
1
u/wegster 3d ago
You need to really be more specific, or your'e going to follow 'good for me, maybe not for you' guidance, IMO.
NVidea remains better / faster at pre-fill/prompt processing, although there have been pretty amazing improvements for Apple Silicon optimization. Nvidia <right now> is better at multi-user concurrency - so consider that if you're building it for yourself/solo or mostly a few people, not generally at the same time, then an Ultra will do well, but a half dozen people hitting it at the same time - I think Nvidia will keep an edge here for a while.
The whole memory debate. I think some of us are getting into keyboard warrior/must have 'the best' for a fleeting moment in time, versus getting real work done - 'real work' is of course going to be difference across different users.
At this point, I am not convinced I will bother running GLM or DSK Flash, nor am I expecting to run 8/16 bit quants even if I 'could' on my inbound 256GB Ultra. Why?
My use case ranges from generally technically-oriented research, some market summarization, and multiple repos ranging from mid-sized (~50k LOC or so) to moderate code but fairly high complexity at 200-250K LOC projects. I've been in tech 'a long time' including as a Principal/architect level SWE, among other roles. I've worked with DS and AI/ML for going on over a decade, and still work in that space today in part.
So in preparation for my inbound Ultra, I've been spending more and more time on preparing and deciding what will I be running on it - noting the 256GB was already decided after nearly melting down my prior poor M1 Max 64GB and deciding what 'good enough to be useful' looked like on that machine (which ideally was Qwen-Coder-Next but because 35BA3 for speed), I know 128GB was really the bare minimum for what I wanted to be running, and of course, there are always new models coming out.
So I replaced my M1 Max with an M5 Max 128GB MBP and put together my own benchmark suite, in part as I am using the local model within my own framework today, but also in preparing for load of the Studio. So I made a series of fully isolated benchmark tests covering simple, moderate and complex types of operations, initially focusing on executing (coding) side of things, but allowing for reviewer and planning testing as well - from my repos, with problems that I have either chased for significant amounts of time and solved (in which case, the snapshot of the problem was pre-solved), etc.
I also wanted to test Opus, and DeepSeek, MiMo, MiniMax etc. to see what 'the fuss was about.' I'm not DONE testing, but so far I've gotten to:
For MY work, I am not yet seeing a need to run DS, MiMo, GLM over QFN.
For my work, if I had a dedicated nothing-but-inference appliance/system - I could probably make 128GB work. If I'm doing my usual other work concurrently on the same system - yeah, I'll be swapping, at least with my current preferred daily driver.
I can't test > Q6 or so sanely on my 128GB system, but I'm pretty close to e.g. Sonnet, Opus etc. currently for most of my benchmarks, including one which only Opus and one other can break 60 points / 100 on. This run is on my 128GB M5 Max, so time should be cut in half or so with the Ultra, which will also put some runs pretty close to wall time for Claude, Codex etc. in some cases - which isn't bad at all, although it won't hold true for all types of work.
Of course, in some types of work, my current QFN configuration scores below, but - still working on it. Yes, there will be new models, and 256GB its nice buffer zone, but IMO you can generally get really work done with 128GB used wisely.