
How to use Kimi K3.1 Pro and K3.1 Pro Highspeed on Runpod
Moonshot AI's Kimi K3.1 Pro and K3.1 Pro Highspeed are now available on Runpod Public Endpoints. Here's how to get started with the Playground, curl, and Python.
Blog
Launch benchmarks from April 2025: the NVIDIA RTX 5090 served Qwen2-0.5B at 65,000+ tokens/sec and 250+ requests/sec with vLLM at 1024 concurrent prompts.

In April 2025, Runpod added the NVIDIA RTX 5090 to its GPU lineup. We benchmarked it for real-time LLM inference on small and mid-sized models, the kind used in high-concurrency chatbots, inference APIs and multi-model backends.
In our internal benchmarks, the 5090 posted high throughput on small language models. Qwen2-0.5B achieved over 65,000 tokens per second and 250+ requests per second at 1024 concurrent prompts—a 2–3x leap compared to previous-gen cards. Similarly, Phi-3-mini-4k-instruct delivered 6,400 tokens/sec and ~25 requests/sec under the same conditions.
Even at lower batch sizes, both models maintained high throughput, with Qwen2-0.5B consistently outperforming Phi-3 in raw speed. It’s worth noting that these numbers represent high-concurrency performance, which is ideal for inference APIs and production deployments. As expected across the industry, single-prompt throughput will be lower.
All tests were run using vLLM, a high-performance inference engine optimized for large-batch and low-latency workloads. During our benchmarks, CPU usage averaged just 3.2%, confirming that the system is well-balanced and GPU-bound. VRAM usage sat at 95%, showing the 5090 was fully loaded with memory-bound tasks.
What really stands out is the linear scaling we observed as batch sizes increased—particularly with Qwen2-0.5B. Even at 1024 concurrent prompts, there was no significant drop-off in efficiency.
The benchmark setup was simple but representative of typical chat and instruction-following use cases. We used:
dtype: auto, no quantization)gpu_memory_utilization=0.95This means there’s still room to experiment—with quantized models, larger architectures, or even multi-model deployments on the same GPU.
In these tests, the RTX 5090 served small models at more than 250 requests per second while using 18 GB of its 32 GB of VRAM, which left room for larger models or several models on the same GPU.
For new workloads on Runpod that need more than 24 GB of VRAM, the RTX A6000 and L40S offer 48 GB. Both are slower than the 5090, so the numbers above won't carry over. Benchmark your own model before you size a deployment.
To run a similar test, start with our inference containers or the vLLM template.
Author profile: Alyssa Mazzina
Blog Posts