Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
~$6,500 MSRP
BaichuanMed OCR 72B i1 needs ~41.7 GB VRAM. NVIDIA A100 40GB has 40.0 GB. With Q2_K quantization, expect ~27 tok/s.
Operating mode
Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.
Current mode
Balanced
Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.
Select quantization to explore
17.6 GB over capacity — needs offload or smaller quantization
Fit status
Too heavy
Decode
10.4 tok/s
TTFT
18671 ms
Safe context
4K
Memory
57.6 GB / 40.0 GB
Offload
30%
This setup is broadly balanced for this model.
Very little memory headroom
You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.
Buy headroom, not only minimum fit
A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | F | Too heavy | 12.2 tok/s | 8676 ms | 4K |
| Coding | F | Too heavy | 10.4 tok/s | 18671 ms | 4K |
| Agentic Coding | F | Too heavy | 7.8 tok/s | 36221 ms | 4K |
| Reasoning | F | Too heavy | 10.4 tok/s | 22066 ms | 4K |
| RAG | F | Too heavy | 7.8 tok/s | 45276 ms | 4K |
How BaichuanMed OCR 72B i1 (72B params) fits at each quantization level on NVIDIA A100 40GB (40.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_KBest for your GPU | 2 | 28.1 GB | Low | C47 |
Q3_K_S | 3 | 35.3 GB | Low | F0 |
NVFP4 | 4 | 40.3 GB | Medium | F0 |
Q4_K_M | 4 | 43.9 GB | Medium | F0 |
Q5_K_M | 5 | 51.8 GB | High | F0 |
Q6_K | 6 | 59.0 GB | High | F0 |
Q8_0 | 8 | 77.0 GB | Very High | F0 |
F16 | 16 | 147.6 GB | Maximum | F0 |
Copy-paste commands to run BaichuanMed OCR 72B i1 on your machine.
Run
lms load hf-mradermacher--baichuanmed-ocr-72b-i1-gguf && lms server startOpções de upgrade
Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
~$6,500 MSRP
Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
~$9,999 MSRP
Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
~$9,999 MSRP
Yes, NVIDIA A100 40GB can run BaichuanMed OCR 72B i1 at Q2_K quantization (Runs with offload (needs ~1.2 GB host RAM)). The recommended Q4_K_M requires 57.6 GB which exceeds available memory, but at Q2_K it needs only 41.7 GB. Expected decode speed: 27.1 tok/s.
BaichuanMed OCR 72B i1 (72B parameters) requires approximately 57.6 GB at Q4_K_M quantization. On NVIDIA A100 40GB, it fits at Q2_K using 41.7 GB.
The recommended quantization is Q4_K_M, but on NVIDIA A100 40GB the best fitting quantization is Q2_K, which uses 41.7 GB.
On NVIDIA A100 40GB, BaichuanMed OCR 72B i1 achieves approximately 27.1 tokens per second decode speed with a time-to-first-token of 7133ms using Q2_K quantization.
For coding workloads, BaichuanMed OCR 72B i1 on NVIDIA A100 40GB receives a F grade with 10.4 tok/s and 4K context.
On NVIDIA A100 40GB, BaichuanMed OCR 72B i1 can safely use up to 13K tokens of context at Q2_K quantization. The model's official context limit is —, but available memory constrains the safe maximum.
Buy headroom, not only minimum fit. A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/hf-mradermacher--baichuanmed-ocr-72b-i1-gguf-on-a100-40gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: