Follow-up reading the most technical and research people here: Monokernel deep dive (GPU Engineering): http://blog.kog.ai/building-a-single-kernel-latency-optimize... Delayed Tensor Parallelism (research): http://blog.kog.ai/delayed-tensor-parallelism-for-faster-tra... To try the speed on the playground: http://playground.kog.ai
Real-time LLM Inference on Standard GPUs: 3k tokens/s per request
61–70 of 108 posts
Re: Real-time LLM Inference on Standard GPUs: 3k tokens/s per request
#62Follow-up reading the most technical and research people here: Monokernel deep dive (GPU Engineering): http://blog.kog.ai/building-a-single-kernel-latency-optimize... Delayed Tensor Parallelism (research): http://blog.kog.ai/delayed-tensor-parallelism-for-faster-tra... To try the speed on the playground: http://playground.kog.ai
It looks like DTP is a distinct architectural choice that would require training new models accordingly? This wouldn't be able to just run inference for existing models.
DTP is something we built for our roadmap in order to get to extremely high speeds (like 10k+ tokens/s). When the budget is under 10 µs per layer, any little overhead matters.
For 1k to 5k tokens/s, regular TP still works because we are able to optimize the inter-GPU all-reduce collectives at under 3 µs, which allows to continue streaming model weights in shared memory, registers and caches while GPUs exchange data.
Re: Real-time LLM Inference on Standard GPUs: 3k tokens/s per request
#63Earlier quoted context omitted.
thanks! we explain how it scales to larger models in the last section the OP blog post
Shame you stopped short of actually benchmarking that scale though, eh?
Re: Real-time LLM Inference on Standard GPUs: 3k tokens/s per request
#64H200 isn't a standard GPU at all
Re: Real-time LLM Inference on Standard GPUs: 3k tokens/s per request
#65I have a naive question here - first, the token speed is very impressive. but why this is the highlight? I would prefer the actual performance.
About model performance, we plan to support the latest frontier models (this tech preview is about the speed of the engine)
Re: Real-time LLM Inference on Standard GPUs: 3k tokens/s per request
#66Earlier quoted context omitted.
I guessed you thought about consumer GPUs. We are about standard datacenter GPUs indeed.
What a lot of use on here are salivating for is the ability to run these on prosumer hardware at home. So we tend to jump to the conclusion that "standard" means "consumer-grade" because that's what we want to see. Still, very cool work!
Re: Real-time LLM Inference on Standard GPUs: 3k tokens/s per request
#67Earlier quoted context omitted.
what did you have in mind when you read "Standard GPUs"?
I guessed you thought about consumer GPUs. We are about standard datacenter GPUs indeed.
Re: Real-time LLM Inference on Standard GPUs: 3k tokens/s per request
#68Earlier quoted context omitted.
Great points. We strived to be fair as possible in the benchmark, but it's indeed not perfect. Taalas should have been added in the dedicated hardware section, even though they use 3-bit quantization when we are on FP16 (to be fair in both directions) and they burn the model directly on the card. Our tech preview is about the speed (hence the small dense model, it was easier to implement). The math checks out though…
Your playground/write-up is very interesting and I would be really interested when you can have something like Deepseek V4 Flash model (49B) running as you are suggesting. I haven't read the article at the moment and I will try to read them hopefully but I wish to ask a question regarding, can this approach be done for say trillion or large parameter models as well or is there some wall which gets hit that makes it v…
The authors' approach also encompasses multi-node approaches that won't apply easily to consumer inference since consumer GPUs have very low-performance interconnects, hence why layer parallelism is usually favored. (But that doesn't work very well with the monokernel approach, since it involves running distinct logic on each separate GPU. It also doesn't speed up single inference, though you can get that throughput back by pipelining small minibatches.)