Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I was a subscriber of their now-unavailable coding plan. The 1000 TPS was very unique at the time, but nowadays their qwen 3.8 gets roflstomped by Mercury 3 at both cost and performance at similar TPS speed. There's not much reason to use them unless you're an enterprise with a custom deal.
 help



Qwen3.8 27B is a dense model with expensive K/V caching. It's fantastic if you have 32-48GB of VRAM and want to run 1 or 2 agent sessions locally. But if serving batch inference for many users, it's expensive.

DeepSeek V4 Flash 0731 is dirt cheap at scale, less than 10% of the cost of Qwen3.8 27B. This is because it's an MoE and it uses much less VRAM for KV cache. And it's generally a better model. V4.1 is also cheap at scale, though I've heard mixed reports on the optimized K/V caching.

You should not be running Qwen3.8 27B on an API normally. Maybe Cerberas's hardware is bad at batching or supporting more efficient K/V caching schemes, or something like that?


If you have 48GB of VRAM, you should be able to get Qwen3.8-Flash-Next running and from my use, it's basically the tipping point. 27B is great for a bit of work, but I have QFN running non stop (when I can gather the correct ideas for it to implement).

What quant and engine are you using? The smallest ones I’m seeing on ollama are > 100GB e.g. https://ollama.com/library/qwen3.8-flash-next/tags

This arch uses engrams aka per layer embeddings. Not all of those GBs need to go in vram.

Halogen flash server for strix halo with quant 4. Its offloading the PLE.



Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

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

Search: