- Find a configuration
- RTX 4080 SUPER · 32 GB
RTX 4080 SUPER · 32 GB
Task · models with qualified results on this GPU
Decision · Qualified results
No qualified results yet · Decision · RTX 4080 SUPER · 32 GB
No reports for this task have been recorded here. This does not show that the model or GPU cannot run it.
Measured alternatives on other GPUs
Measured on different GPUs with the same or smaller listed capacity. These are references for choosing hardware, not performance or compatibility evidence for your selected GPU.
clef-flash
Cloudflare · 4 tested configurations · 1 GPU
- vGPU-32GB · 32 GBbf16 · Text → Structured data · typed-invoices-v1 · Test duration 1 s
- Throughput · Batch 1
- 10.3decisions/sec
- Best measured · Batch 4
- 10.9decisions/sec
- Observed GPU occupancy
- 18.2GiB
- P95 latency
- 104 ms
Test details · 2 batch sizes
Occupancy includes engine buffers and reserved KV cache. It is not the minimum VRAM required by the model.
Reports combined counts reports, not inference requests. Request successes and failures are listed in each report.
- Engine
- clef-native
- Protocol
- native-forward-v1
- Dataset
- typed-invoices-v1
- Workload
- decision
Batch size Mean throughput (decisions/sec) P95 TTFT Observed occupancy (GiB) GPU power (W) Reports combined View report B1 10.26 104 ms — 18.17 67.9 1 1d1661ad ↗ B4 10.89 389 ms — 18.49 156 1 1d1661ad ↗ 3 other test configurations on this GPU
- bf16 · Text → Structured data · typed-invoices-v1 · Test duration 6 s
- Throughput · Batch 1
- 10.6decisions/sec
- Best measured · Batch 4
- 11decisions/sec
- Observed GPU occupancy
- 18.2GiB
- P95 latency
- 99 ms
Test details · 2 batch sizes
Occupancy includes engine buffers and reserved KV cache. It is not the minimum VRAM required by the model.
Reports combined counts reports, not inference requests. Request successes and failures are listed in each report.
- Engine
- clef-native · PyTorch 2.13.0+cu130
- Protocol
- native-forward-v1
- Dataset
- typed-invoices-v1
- Workload
- decision
Batch size Mean throughput (decisions/sec) P95 TTFT Observed occupancy (GiB) GPU power (W) Reports combined View report B1 10.56 99 ms — 18.17 206.1 2 63f44036 ↗ B4 11.04 402 ms — 18.55 244.4 2 63f44036 ↗ - bf16 · Text → Structured data · typed-invoices-v1 · Test duration 6 s
- Throughput · Batch 1
- 10.6decisions/sec
- Best measured · Batch 4
- 11.1decisions/sec
- Observed GPU occupancy
- 18.2GiB
- P95 latency
- 103 ms
Test details · 2 batch sizes
Occupancy includes engine buffers and reserved KV cache. It is not the minimum VRAM required by the model.
Reports combined counts reports, not inference requests. Request successes and failures are listed in each report.
- Engine
- clef-native
- Protocol
- native-forward-v1
- Dataset
- typed-invoices-v1
- Workload
- decision
Batch size Mean throughput (decisions/sec) P95 TTFT Observed occupancy (GiB) GPU power (W) Reports combined View report B1 10.56 103 ms — 18.17 196.8 1 4eb73a4d ↗ B4 11.1 390 ms — 18.56 235.9 1 4eb73a4d ↗ - bf16 · 1K → 1K tokens
- Throughput · Batch 1
- 10.2decisions/sec
- Best measured · Batch 4
- 10.9decisions/sec
- Observed GPU occupancy
- 18.2GiB
- P95 latency
- 104 ms
Test details · 2 batch sizes
Occupancy includes engine buffers and reserved KV cache. It is not the minimum VRAM required by the model.
Reports combined counts reports, not inference requests. Request successes and failures are listed in each report.
- Engine
- vLLM
- Protocol
- native-forward-v1
- Dataset
- typed-invoices-v1
- Workload
- decision
Batch size Mean throughput (decisions/sec) P95 TTFT Observed occupancy (GiB) GPU power (W) Reports combined View report B1 10.19 104 ms — 18.17 69.8 1 caef7154 ↗ B4 10.88 388 ms — 18.49 152.8 1 caef7154 ↗
Occupancy includes engine buffers and reserved KV cache. It is not the minimum VRAM required by the model.
Original reports
Running benchmarks
0Updates automaticallyNo benchmarks are currently reported as running.
Methodology
Average of error-free runs for the selected recorded configuration. Missing methods and fallback runs are not ranked. Performance index = average / fastest matching hardware × 100. Value index = performance per purchase cost / best comparable value × 100. Quality is separate by dataset and protocol. Prices are dated seller listings, not completed transactions or market averages.
Updated 11/5/2026, 11:07:29 PM