Hacker Newsnew | past | comments | ask | show | jobs | submit | hacklas's commentslogin

Thanks. I agree, GGUF and upstream contributions are on my radar.


Worth mentioning why this is harder than it looks.

There is a different set of experts at every layer, and each layer has a small router that decides which ones to use.

The router needs to look at the state produced by the experts below it.

Drafted tokens from the MTP head can be used to predict which experts the first layer will want, but not beyond that. To know what layer 10 experts needs, you have to run layers 1-9 which means loading their experts.

So, yes, instead of a next-token drafter like MTP, you'd want something trained to predict the expert activation across all layers at once.


That kind of sounds like a branch predictor in a CPU.


exactly. we need branch predictor for expert weight.


How large?

With 64 GB of unified memory, you should be able to run a DeepSeek V4 Flash quantisation at 7–10 t/s, for example with: https://github.com/antirez/ds4 or https://github.com/steadfastgaze/MoEspresso (my engine).

The routed experts needed for the next tokens that are not already in memory need to be read from the SSD, so the speed becomes SSD reading bound and the larger the memory, the faster the inference.


Is there a particular quant of DS v4 Flash you'd recommend that works on 64GB machines? None of the antirez versions on HF look small enough?

Also, FWIW, I've been experimenting with Laguna-S-2.1. It runs reasonably quickly (llama.cpp, IQ2_M quant) but the outputs so far aren't impressive, and it gets stuck and perseverates. Very subjectively, at that level of quantisation, it seems to perform worse than Qwen 3.6 27B at Q4_K_XL.


For a dense model this would be a limitation, but not all of a MoE model needs to be in memory, but the largest part of a MoE are the routed experts.

Some parts are needed to generated every single token and these really should fit in memory, but the router experts that are not neeed can rest on SSD and be read only if they are needed, so... you can run MoE models bigger than you memory, try the IQ2XXS.

It should work on your 64 GB after you enable SSD mode in DwarfStar (in MoEspesso it enables itself), while being slower, so... I am really hoping for good models between the 50-120 GB other than Laguna, there is a big gap right now unfortunately.


Thanks.

Agree on the sizing - selfishly, something like a 60B MoE would be great - fast on big machines, and a 4 or 5 bit quant should fit in 64GB and still work well.


> 7–10 t/s

Maybe use it for overnight batch work! Hopefully, you aren’t suggesting it using for realtime conversations!


The Deepseek V3 is a model with 671 billion parameters, of which 37 billion are active.

Magistral Small is a 24 billion parameter model.

Pretty impressive in terms of efficiency for Mistral.

The size of the Magistral Medium is not publicly available, so it is difficult to compare efficiency there.


> The size of the Magistral Medium is not publicly available, so it is difficult to compare efficiency there.

FWIW one of their 70B models has leaked in the past (search for "miqu") and rumors at the time were that it was their medium model.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: