Noticed they are present in OpenRouter, but Qwen 3.8 is not there yet. Hopefully it'll get there soon. For those who haven't noticed though, the context size they allow for Qwen is just 128k. Still interesting as a specialized sub-agent but not really well suited for long tasks.
Qwen 3.8 27B available on Cerebras at 1500 tokens/s
171–180 of 242 posts
Re: Qwen 3.8 27B available on Cerebras at 1500 tokens/s
#172Earlier quoted context omitted.
I (we) run Qwen3.8-27B-FP8 on a DGX Spark box - that's roughly £4000 of hardware. I did benchmark it in various ways and it runs quite well but it is a quantised jobbie and 1.5k t/s is also rather faster than anything I can possibly hope to achieve. To run that model at those sorts of speeds is going to need some serious investment and you are going to have to pay for it.
How fast is it?
Re: Qwen 3.8 27B available on Cerebras at 1500 tokens/s
#173Earlier quoted context omitted.
128k context is not a limit of the model, that's a limit of implementation: "Context Length: 262,144 natively and extensible up to 1,000,000 tokens." https://huggingface.co/Qwen/Qwen3.8-27B
TPM means Tokens per Minute.
Re: Qwen 3.8 27B available on Cerebras at 1500 tokens/s
#174Noticed they are present in OpenRouter, but Qwen 3.8 is not there yet. Hopefully it'll get there soon. For those who haven't noticed though, the context size they allow for Qwen is just 128k. Still interesting as a specialized sub-agent but not really well suited for long tasks.
128k is effectively useless on even trivial toy size "not for real business use" coding projects, by the time you reach 105k to 115k tokens with loading code into context and new research/tasks, and ask it to modify something, it'll be vacating older stuff out of context and forgetting the whole picture of what you're working on.
I guess this smaller context but faster llm engine could be good to develop your harness on to get faster results and faster iteration.
Re: Qwen 3.8 27B available on Cerebras at 1500 tokens/s
#175Earlier quoted context omitted.
128k is effectively useless on even trivial toy size "not for real business use" coding projects, by the time you reach 105k to 115k tokens with loading code into context and new research/tasks, and ask it to modify something, it'll be vacating older stuff out of context and forgetting the whole picture of what you're working on.
Isn't context size one of the central motivations of the whole agent / orchestration business - fanning out increasingly detailed work to a tree of subagents. Orchestrator vs worker, hierarchical multitier trees, etc. I guess this smaller context but faster llm engine could be good to develop your harness on to get faster results and faster iteration.
128k is pretty much only good for chat/conversational/question asking (including tool calls for searching things and spitting back/parsing a set of results) or human interactive agent purposes.
Re: Qwen 3.8 27B available on Cerebras at 1500 tokens/s
#176Re: Qwen 3.8 27B available on Cerebras at 1500 tokens/s
#177Earlier quoted context omitted.
> 150k TPM limit on public endpoint means that it's likely unusable for many coding tasks. I don't understand. How does that make it unusable? Is the limit shared by an entire team at once? 150,000 tokens per minute is a lot. You could start hitting that with a lot of concurrent requests in your session, but even throttled to 150k TPM it's still going to be faster than anything else you find. I think the 128K context…
128k context is not a limit of the model, that's a limit of implementation: "Context Length: 262,144 natively and extensible up to 1,000,000 tokens." https://huggingface.co/Qwen/Qwen3.8-27B
It's in the link.
Re: Qwen 3.8 27B available on Cerebras at 1500 tokens/s
#178Think, DeepSeek Flash (before the price hikes) prices.
If I can run this on a 32gb card while they have a datacenter with wholesale electricity prices, why are we not seeing "cents per billion tokens" pricing?
Re: Qwen 3.8 27B available on Cerebras at 1500 tokens/s
#179Earlier quoted context omitted.
Yeah, their public service isn't a serious/competitive offering. They don't have the capacity to serve all the customers who might want to use them at that speed. The public service exists so they get some users on OpenRouter, and that shows them as #1 on speed, which proves their tech is very fast, which gets them billions in hardware sales/licensing. If you have big enough pockets they can probably dedicate capacit…
GPUs can't reach these speeds. You could build a supercomputing cluster and still not reach these speeds.