Datasets:
Clean up dataset card: simplify retention table, remove AI-generated prose
Browse files
README.md
CHANGED
|
@@ -31,38 +31,37 @@ configs:
|
|
| 31 |
|
| 32 |
# AgentPerfBench
|
| 33 |
|
| 34 |
-
LLM inference benchmark dataset
|
| 35 |
|
| 36 |
## Dataset Configurations
|
| 37 |
|
| 38 |
-
|
| 39 |
|
| 40 |
### trace_replay (3,147 rows)
|
| 41 |
|
| 42 |
-
|
| 43 |
|
| 44 |
Profiles: `chat-medium`, `chat-multiturn-long`, `chat-multiturn-medium`, `chat-multiturn-short`, `chat-short`, `chat-singleturn`, `coding-singleturn`, `decode-heavy`, `osworld-multiturn-long`, `osworld-multiturn-medium`, `osworld-multiturn-short`, `prefill-heavy`, `random-1k`, `swebench-multiturn-medium`, `swebench-multiturn-short`, `terminalbench-multiturn-medium`, `terminalbench-multiturn-short`
|
| 45 |
|
| 46 |
### distributional (245 rows)
|
| 47 |
|
| 48 |
-
|
| 49 |
|
| 50 |
Profiles: `chat-multiturn`, `chat-singleturn`, `coding-singleturn`, `osworld-multiturn`, `swebench-multiturn`, `terminalbench-multiturn`
|
| 51 |
|
| 52 |
### Why two configurations?
|
| 53 |
|
| 54 |
-
|
| 55 |
|
| 56 |
### Concurrency filtering
|
| 57 |
|
| 58 |
-
The benchmark harness capped actual concurrent connections at the session pool size. Rows where declared concurrency exceeds the pool size never achieved the intended load and have been excluded.
|
| 59 |
|
| 60 |
-
|
|
| 61 |
-
|-------
|
| 62 |
-
| trace_replay
|
| 63 |
-
| distributional
|
| 64 |
-
|
|
| 65 |
-
| **Total** | **5,743** | **3,392** | **2,351** | **Retention: 59.1%** |
|
| 66 |
|
| 67 |
## Coverage
|
| 68 |
|
|
@@ -138,9 +137,9 @@ Per-request and multi-turn granularity data will be added when full result JSON
|
|
| 138 |
|
| 139 |
## Intended Uses
|
| 140 |
|
| 141 |
-
-
|
| 142 |
- Capacity planning for agentic LLM deployments.
|
| 143 |
-
-
|
| 144 |
- Studying TTFT degradation under multi-turn context accumulation.
|
| 145 |
|
| 146 |
## Limitations
|
|
@@ -148,14 +147,12 @@ Per-request and multi-turn granularity data will be added when full result JSON
|
|
| 148 |
- Results are specific to tested hardware and software versions (vLLM 0.19.0, SGLang 0.5.9).
|
| 149 |
- Distributional profiles approximate but do not replicate exact production traffic patterns.
|
| 150 |
- No consumer GPUs beyond RTX 3090; no non-NVIDIA accelerators.
|
| 151 |
-
- Closed-loop concurrency only; open-loop (Poisson arrival)
|
| 152 |
- No model quality metrics. This is a systems benchmark.
|
| 153 |
|
| 154 |
## Ethical Considerations
|
| 155 |
|
| 156 |
-
|
| 157 |
-
- Synthetic profiles use random tokens. Trace-replay profiles derive from open benchmarks (SWE-Bench MIT, TerminalBench, OSWorld).
|
| 158 |
-
- Benchmark results should not be used as sole basis for hardware purchasing decisions.
|
| 159 |
|
| 160 |
## Source Datasets
|
| 161 |
|
|
|
|
| 31 |
|
| 32 |
# AgentPerfBench
|
| 33 |
|
| 34 |
+
LLM inference benchmark dataset: serving performance (TTFT, TPOT, ITL, throughput) across 9 models, 14 GPU configurations, 2 engines, and 20+ workload profiles covering single-turn chat, multi-turn agent sessions, and stress tests. Includes per-kernel CUDA profiling for roofline analysis.
|
| 35 |
|
| 36 |
## Dataset Configurations
|
| 37 |
|
| 38 |
+
Two benchmark configurations, each with a different data collection method.
|
| 39 |
|
| 40 |
### trace_replay (3,147 rows)
|
| 41 |
|
| 42 |
+
Replays exact ISL/OSL sequences from recorded agent sessions (SWE-Bench, TerminalBench, OSWorld, ShareGPT). Input distributions come from real tool-use patterns.
|
| 43 |
|
| 44 |
Profiles: `chat-medium`, `chat-multiturn-long`, `chat-multiturn-medium`, `chat-multiturn-short`, `chat-short`, `chat-singleturn`, `coding-singleturn`, `decode-heavy`, `osworld-multiturn-long`, `osworld-multiturn-medium`, `osworld-multiturn-short`, `prefill-heavy`, `random-1k`, `swebench-multiturn-medium`, `swebench-multiturn-short`, `terminalbench-multiturn-medium`, `terminalbench-multiturn-short`
|
| 45 |
|
| 46 |
### distributional (245 rows)
|
| 47 |
|
| 48 |
+
Samples ISL/OSL from parameterized distributions (e.g., lognormal) fitted to real workload statistics. Faster to run than full trace replays; MSE-validated against trace_replay.
|
| 49 |
|
| 50 |
Profiles: `chat-multiturn`, `chat-singleturn`, `coding-singleturn`, `osworld-multiturn`, `swebench-multiturn`, `terminalbench-multiturn`
|
| 51 |
|
| 52 |
### Why two configurations?
|
| 53 |
|
| 54 |
+
trace_replay grounds results in observed agent behaviour; distributional covers the model-hardware-concurrency matrix faster.
|
| 55 |
|
| 56 |
### Concurrency filtering
|
| 57 |
|
| 58 |
+
The benchmark harness capped actual concurrent connections at the session pool size. Rows where declared concurrency exceeds the pool size never achieved the intended load and have been excluded. This affects trace_replay data at concurrency > 100 (session pool was 100) and distributional data collected before the fix at concurrency > 10 (session pool was 10). Distributional data collected after the fix has no such limitation.
|
| 59 |
|
| 60 |
+
| Config | Rows |
|
| 61 |
+
|--------|------|
|
| 62 |
+
| trace_replay | 3,147 |
|
| 63 |
+
| distributional | 245 |
|
| 64 |
+
| **Total** | **3,392** |
|
|
|
|
| 65 |
|
| 66 |
## Coverage
|
| 67 |
|
|
|
|
| 137 |
|
| 138 |
## Intended Uses
|
| 139 |
|
| 140 |
+
- Inference engine comparison under controlled conditions.
|
| 141 |
- Capacity planning for agentic LLM deployments.
|
| 142 |
+
- GPU roofline analysis across workload types.
|
| 143 |
- Studying TTFT degradation under multi-turn context accumulation.
|
| 144 |
|
| 145 |
## Limitations
|
|
|
|
| 147 |
- Results are specific to tested hardware and software versions (vLLM 0.19.0, SGLang 0.5.9).
|
| 148 |
- Distributional profiles approximate but do not replicate exact production traffic patterns.
|
| 149 |
- No consumer GPUs beyond RTX 3090; no non-NVIDIA accelerators.
|
| 150 |
+
- Closed-loop concurrency only; no open-loop (Poisson arrival).
|
| 151 |
- No model quality metrics. This is a systems benchmark.
|
| 152 |
|
| 153 |
## Ethical Considerations
|
| 154 |
|
| 155 |
+
No PII. Synthetic profiles use random tokens; trace-replay profiles derive from open benchmarks (SWE-Bench MIT, TerminalBench, OSWorld). Not a basis for hardware purchasing decisions on its own.
|
|
|
|
|
|
|
| 156 |
|
| 157 |
## Source Datasets
|
| 158 |
|