OK... we need way more information than this to validate this claim! I can run Qwen-8B at 1 billion tokens per second if you don't check the model's output quality. No information is given about the source code, correctness, batching, benchmark results, quantization, etc. etc. etc.
We validate with MMLU and Hellaswag presently, and are getting this independently verified by a 3rd party. We have considered open-sourcing some of our optimized inference libraries in the future, but have not yet come to a decision on this. Also if you need a rough intuition as to why this is possible: it's because this entire inference stack was built for exactly one model, and thus we can really tune the entire fr…
Surpassing vLLM with a Generated Inference Stack
11–20 of 26 posts
Re: Surpassing vLLM with a Generated Inference Stack
#12Earlier quoted context omitted.
We validate with MMLU and Hellaswag presently, and are getting this independently verified by a 3rd party. We have considered open-sourcing some of our optimized inference libraries in the future, but have not yet come to a decision on this. Also if you need a rough intuition as to why this is possible: it's because this entire inference stack was built for exactly one model, and thus we can really tune the entire fr…
I've no problem with the intuition. But I would hope for a lot more focus in the marketing materials on proving the (statistical) correctness of the implementation. 15% better inference speed is not worth it to use a completely unknown inference engine not tested across a wide range of generation scenarios.
Re: Surpassing vLLM with a Generated Inference Stack
#13Maybe I should learn more about ML to have a better instinct on optimization methods in general, so I can actually build AI optimizers like these.
Re: Surpassing vLLM with a Generated Inference Stack
#14Does it support paged attention like vLLM though? Without that they will run into memory fragmentation quickly.
Re: Surpassing vLLM with a Generated Inference Stack
#15Why do they need to run benchmarks to confirm performance? Can't they run an example prompt and verify they get the exact same output token probabilities for all prompts? The fact that they are not doing this makes me suspicious that they are in fact not doing the exact same thing as vLLM. It is also a bit weird that they are not incorporating speculative decoding, that seems like a critical performance optimization,…
Wouldn’t speculative decoding decrease overall throughput, but optimise (perceived) responsiveness?
Re: Surpassing vLLM with a Generated Inference Stack
#16Why do they need to run benchmarks to confirm performance? Can't they run an example prompt and verify they get the exact same output token probabilities for all prompts? The fact that they are not doing this makes me suspicious that they are in fact not doing the exact same thing as vLLM. It is also a bit weird that they are not incorporating speculative decoding, that seems like a critical performance optimization,…
> It is also a bit weird that they are not incorporating speculative decoding Wouldn’t speculative decoding decrease overall throughput, but optimise (perceived) responsiveness?
Re: Surpassing vLLM with a Generated Inference Stack
#17What's the post request latency of this part? What the ftt?
Re: Surpassing vLLM with a Generated Inference Stack
#18Re: Surpassing vLLM with a Generated Inference Stack
#19Earlier quoted context omitted.
We validate with MMLU and Hellaswag presently, and are getting this independently verified by a 3rd party. We have considered open-sourcing some of our optimized inference libraries in the future, but have not yet come to a decision on this. Also if you need a rough intuition as to why this is possible: it's because this entire inference stack was built for exactly one model, and thus we can really tune the entire fr…
I've no problem with the intuition. But I would hope for a lot more focus in the marketing materials on proving the (statistical) correctness of the implementation. 15% better inference speed is not worth it to use a completely unknown inference engine not tested across a wide range of generation scenarios.
Re: Surpassing vLLM with a Generated Inference Stack
#20Any place we can find the code?