Detailed summaries index

Qwen-Bailian Anonymous Dataset Overview

Four anonymized production-derived Qwen serving traces from Aliyun Bailian. Each record has trace-relative arrival timestamp, input/output token counts, request type, session turn metadata, and 16-token KV block hash IDs. Request durations are not included.

Use for benchmarking: AIPerf supports these JSONL files with --custom-dataset-type bailian_trace and --fixed-schedule. Since durations are absent, concurrency should be measured during replay rather than inferred directly from the raw trace.

Scenario Comparison

TraceScenarioRequestsHoursMean RPSPeak 1s RPSInput minInput maxInput p50Input p99Output p50Output p99Hash reuse
Qwen Bailian Trace ATo-C chat-style interactive services43,0582.0005.98118.005689,2861,046.0014,364.59375.501,641.4359.8%
Qwen Bailian Trace BTo-B API-driven task automation172,8002.00024.00052.001966,446574.006,294.0139.001,006.0261.5%
Qwen Bailian ThinkingReasoning-intensive chat workload10,8121.9981.50340.001151,6223,680.0024,972.681,665.5034,686.5346.2%
Qwen Bailian CoderCode generation workload43,0112.0005.97519.00925,7774,540.0014,406.90469.005,842.2066.4%

Request Type Composition

For Trace A and Trace B, the text-only windows used for benchmark selection are lower RPS than the aggregate traces because non-text request types are excluded.
TracePer-type loadInterpretation
Qwen Bailian Trace Atext: 31,744 (73.72%, 4.409 RPS); search: 8,187 (19.01%, 1.137 RPS); image: 1,617 (3.76%, 0.225 RPS); file: 1,510 (3.51%, 0.210 RPS)Text-only RPS is close to the full trace, but still lower than aggregate.
Qwen Bailian Trace Bapi: 150,936 (87.35%, 20.963 RPS); text: 21,864 (12.65%, 3.037 RPS)Aggregate 24 RPS is mostly api traffic; text-only load is ~3 RPS.
Qwen Bailian Thinkingthinking: 10,812 (100.00%, 1.503 RPS)Single native workload type.
Qwen Bailian Codercoder: 43,011 (100.00%, 5.975 RPS)Single native workload type.

Comparison Plots

Reports