← All models

General Q&A · Coding

Kimi-K3 · 2.8T cluster

A multimodal mixture-of-experts model for long-context reasoning, coding, and agent tasks. Distributed inference is validated on 16 MegaCubes with MXFP4 weights.

Multimodal understandingText, images, video → text
16 MegaCubesTest report available

01 / Model parameters

Model architecture & capabilities

Kimi K3, published by Moonshot AI, is designed for extended reasoning, multi-step tasks, and long contexts. Its mixture-of-experts architecture activates a subset of parameters at each step and combines linear and sparse attention to process long text. It also supports image and video understanding, with text or tool-call output.

  • Long-form material and cross-document Q&A
  • Code development, editing, and troubleshooting
  • Multi-step agent tasks
Publisher / model
Moonshot AI · Kimi-K3
Parameter count
2.8T total parameters; approx. 104B active per token
Architecture
93-layer MoE; 896 routed experts, 16 selected per step, plus 2 shared experts; KDA + Gated MLA
Model context
Native 1,048,576 tokens; see deployment and tests for the usable device context length
Input / output
Text, image, and video input; text and tool-call output
Weight precision / size
MXFP4 weights, MXFP8 activations; approx. 1.45 TB of weights in this test
License
Kimi K3 License; use and distribution must comply with the model license

MegaCube tests on this page primarily cover text reasoning, long-context retrieval, and concurrent inference. Published vision capabilities do not establish validation of every vision task on this configuration.

Model information checked on 2026-09-20

02 / Deployment

MegaCube deployment configuration

Compute devices
16 × MegaCube, each with 128 GB unified memory
Interconnect
H3C S9855-40B · Dual 200G RoCE v2 links · MTU 9000
Inference engine
vLLM · TP16 · DSpark speculative decoding
Context
Service configuration: 333,126 tokens; tested here up to 128K
Application integration
OpenAI-compatible API
  1. Prepare the cluster

    Connect 16 devices to the RoCE switching network and verify management connectivity and both high-speed links.

  2. Load the weights

    Verify the MXFP4 weights and run TP16 shards, with approx. 93 GB of weights per device.

  3. Start inference

    Start vLLM and DSpark with the report's configuration and confirm that all compute nodes join the service.

  4. Connect your application

    Check the API, long-document tasks, and tool calling, then connect PINVOU or your business application.

03 / Performance tests

MegaCube performance test results

2026-08-27; 16 devices; 234 model test requests. Per-request token generation and aggregate throughput under concurrency are measured separately. Short-context concurrency results do not apply to 128K input.

22.69 tok/s128-token input, single-stream decoding
0.573 sTTFT for the same short-input case
12 / 124K–128K long-context retrieval points passed
Single request: input length and decoding performance
Input lengthTime to first tokenToken generation rate
1280.573 s22.69 tok/s
1K0.727 s25.28 tok/s
32K10.903 s23.48 tok/s
128K44.216 s21.20 tok/s
Short context: concurrent throughput and TTFT
Short-context concurrencyAggregate system throughputTTFT P95Success rateRecommended use
1 request21.8 tok/s0.70 s100%Responsive single-user use
2 requests32.9 tok/s0.93 s100%Responsive shared use
4 requests42.7 tok/s1.31 s100%Recommended interactive concurrency limit
8 requests48.4 tok/s56.05 s100%Queued tasks
16 requests54.3 tok/s104.47 s100%Highest measured throughput / batch processing
  • Long-context retrieval was tested at 12 positions in the test text. This result does not measure accuracy across general knowledge Q&A.
  • Higher concurrency increases queueing and time to first token. Aggregate system throughput does not describe the response speed experienced by an individual user.

C1 / C4 / C8 denotes 1 / 4 / 8 concurrent requests. TTFT (time to first token) measures elapsed time from submitting a request to receiving its first output token. TPOT (time per output token) measures average time per generated token after the first token. Aggregate throughput is the combined output rate across concurrent requests; a single-request token generation rate is measured separately in tok/s.

Public benchmark references

Model capability & platform performance benchmarks

The following results are published by model developers or platform providers and are separate from the MegaCube tests above. Capability scores measure task performance; tok/s measures token throughput. Results obtained with different models, numerical precision, hardware, or test protocols are not directly comparable.

Kimi K3 official capability benchmarks

Evaluated model
Kimi K3
Test platform
Inference hardware not disclosed by the source
Kimi K3 official capability benchmarks · Data
BenchmarkScoreWhat it measures
GPQA Diamond93.5Challenging science Q&A
DeepSWE v1.167.5Real-world software problem solving
Terminal-Bench 2.188.3Multi-step terminal operations

Test conditionsMaximum reasoning effort, temperature=1. GPQA uses top_p=0.95; coding and terminal tasks use Kimi Code and top_p=1. Scores depend on the agent framework and tool environment.

View original benchmarks ↗

Plan model deployment and application integration

Evaluate device configurations and inference services for your model size, workloads, and concurrency needs.

Discuss this model