2 ms·
I've found that mimo v2.5 works for very basic things like a python script to do one thing, but it also is very 'dumb' compared to qwen 3.8-flash-next (I think
by walrus01 10d ago
I've found that mimo v2.5 works for very basic things like a python script to do one thing, but it also is very 'dumb' compared to qwen 3.8-flash-next (I think the benchmark scores for terminal and coding specific benches back this up). And definitely not in the same class as like a GLM5.2 or 5.3. It's fast but makes basic mistakes that only get caught later.
- deleted 10d ago[deleted]
- girvo 9d agoThe fact I can run Qwen 3.8 Flash Next locally, forever (on my DGX Spark-alike) is genuinely shocking to me. It’s crazy good for how small it is. Fast, too.
- walrus01 9d agoYeah, I'm guessing you have a variant that fits in <128GB with 262k context? I have the unsloth Q8 GGUF of it here in a setup that with full context and ton of extra llama-server "--cache-ram" sits around 200GB RAM usage on a 256GB system, it's probably the best thing I've found for a 256GB class machine. Enough headroom for a rope/yarn extension to 524288 context if I need it.
- girvo 9d agoYep, the engrams are on NVMe (the speed penalty was lower than I expected) and it is quantised to fit. It’s good enough that I’m considering a second spark, or selling this and buying an M5 Ultra with 256GB for it
- gmerc 9d agoRTX6000 Blackwell with 96GB is enough to run it with NV4, 256k context, KVcache, multimodal at 130t/s (SGLang). It's toasty, you're using up 94GB of those 96, but it works and the results are great
- jonsoft 9d agoI made this 3D game in a day on the same setup with Qwen Code as agent: https://games.jonathanpage.com/ https://games.jonathanpage.com/ And I am not a web developer! It's an extraordinary model. (Mouse and keyboard required)