Deepseek Coder 1.3B Kexer — Hardware Requirements & GPU Compatibility
ChatCodeSpecifications
- Publisher
- JetBrains
- Family
- DeepSeek Coder
- Parameters
- 1.3B
- Architecture
- LlamaForCausalLM
- Context Length
- 16,384 tokens
- Vocabulary Size
- 32,256
- Release Date
- 2024-05-22
- License
- Apache 2.0
Get Started
HuggingFace
How Much VRAM Does Deepseek Coder 1.3B Kexer Need?
Select a quantization to see compatible GPUs below.
| Quantization | Bits | VRAM | + Context | File Size | Quality |
|---|---|---|---|---|---|
| BF16 | 16.00 | 3.4 GB | 6.2 GB | 2.69 GB | Brain floating point 16 — preferred for training |
Which GPUs Can Run Deepseek Coder 1.3B Kexer?
BF16 · 3.4 GBDeepseek Coder 1.3B Kexer (BF16) requires 3.4 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 5+ GB is recommended. Using the full 16K context window can add up to 2.8 GB, bringing total usage to 6.2 GB. 35 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti.
Runs great
— Plenty of headroomWhich Devices Can Run Deepseek Coder 1.3B Kexer?
BF16 · 3.4 GB33 devices with unified memory can run Deepseek Coder 1.3B Kexer, including NVIDIA DGX H100, NVIDIA DGX A100 640GB.
Runs great
— Plenty of headroomRelated Models
Frequently Asked Questions
- How much VRAM does Deepseek Coder 1.3B Kexer need?
Deepseek Coder 1.3B Kexer requires 3.4 GB of VRAM at BF16. Full 16K context adds up to 2.8 GB (6.2 GB total).
VRAM = Weights + KV Cache + Overhead
Weights = 1.3B × 16 bits ÷ 8 = 2.7 GB
KV Cache + Overhead ≈ 0.7 GB (at 2K context + ~0.3 GB framework)
KV Cache + Overhead ≈ 3.5 GB (at full 16K context)
VRAM usage by quantization
BF163.4 GBBF16 + full context6.2 GB- Can I run Deepseek Coder 1.3B Kexer on a Mac?
Deepseek Coder 1.3B Kexer requires at least 3.4 GB at BF16, which exceeds the unified memory of most consumer Macs. You would need a Mac Studio or Mac Pro with a high-memory configuration.
- Can I run Deepseek Coder 1.3B Kexer locally?
Yes — Deepseek Coder 1.3B Kexer can run locally on consumer hardware. At BF16 quantization it needs 3.4 GB of VRAM. Popular tools include Ollama, LM Studio, and llama.cpp.
- How fast is Deepseek Coder 1.3B Kexer?
At BF16, Deepseek Coder 1.3B Kexer can reach ~857 tok/s on AMD Instinct MI300X. On NVIDIA GeForce RTX 4090: ~193 tok/s. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.
tok/s = (bandwidth GB/s ÷ model GB) × efficiency
Example: AMD Instinct MI300X → 5300 ÷ 3.4 × 0.55 = ~857 tok/s
Estimated speed at BF16 (3.4 GB)
AMD Instinct MI300X~857 tok/sNVIDIA GeForce RTX 4090~193 tok/sNVIDIA H100 SXM~641 tok/sAMD Instinct MI250X~530 tok/sReal-world results typically within ±20%. Speed depends on batch size, quantization kernel, and software stack.
- What's the download size of Deepseek Coder 1.3B Kexer?
At BF16, the download is about 2.69 GB.
- Which GPUs can run Deepseek Coder 1.3B Kexer?
35 consumer GPUs can run Deepseek Coder 1.3B Kexer at BF16 (3.4 GB). Top options include AMD Radeon RX 6700 XT, AMD Radeon RX 6800, AMD Radeon RX 6800 XT. 35 GPUs have plenty of headroom for comfortable inference.
- Which devices can run Deepseek Coder 1.3B Kexer?
33 devices with unified memory can run Deepseek Coder 1.3B Kexer at BF16 (3.4 GB), including Mac Mini M4 (16 GB), Mac Mini M4 (32 GB), Mac Mini M4 Pro (24 GB), Mac Mini M4 Pro (48 GB). Apple Silicon Macs use unified memory shared between CPU and GPU, making them well-suited for local LLM inference.