Can the RTX A6000 run Axion-1.0-35B?
Axion-1.0-35B·35.1B (3.9B active)·RTX A6000·48 GB VRAM
Yes. The RTX A6000 runs Axion-1.0-35B fully in VRAM at Q8_0 (about 37 GB of 48 GB), at roughly 102 tokens/s.
- best quant
- Q8_0
- needs
- 37 GB
- usable
- 48 GB
- est. speed
- ~102 tok/s
Estimates for an 8K context; offload assumes 32 GB of system RAM.Try other contexts on the Axion-1.0-35B page →
Every quantisation of Axion-1.0-35B on the RTX A6000
| Quant | Memory | Fit | Speed |
|---|---|---|---|
| Q2_K | 14 GB | fits | ~329 tok/s |
| Q3_K_M | 18 GB | fits | ~222 tok/s |
| Q4_K_M | 22 GB | fits | ~179 tok/s |
| Q5_K_M | 25 GB | fits | ~152 tok/s |
| Q6_K | 29 GB | fits | ~131 tok/s |
| Q8_0 pick | 37 GB | fits | ~102 tok/s |
| FP16 / BF16 | 70 GB | offload | ~12 tok/s |
Speed is a bandwidth-based estimate for generating text (768 GB/s); prompt processing and long contexts are slower.
Measured speed on the RTX A6000
No community reports for this pair yet.
Report your own speed →Run Axion-1.0-35B on the RTX A6000
Using Q8_0, the best fit for RTX A6000.
ollama run hf.co/mradermacher/Axion-1.0-35B-GGUF:Q8_0 llama-server -hf mradermacher/Axion-1.0-35B-GGUF:Q8_0Downloads the GGUF on first run. Installed through llama.app? The same flags work with `llama serve`.
lms get mradermacher/Axion-1.0-35B-GGUF@Q8_0Then load it from the LM Studio app or with `lms load`.
vllm serve Axion1-0/Axion-1.0-35Bservices:
vllm:
image: vllm/vllm-openai:latest
command: Axion1-0/Axion-1.0-35B
ports:
- "8000:8000"
ipc: host
volumes:
- ~/.cache/huggingface:/root/.cache/huggingface
deploy:
resources:
reservations:
devices:
- driver: nvidia
count: all
capabilities: [gpu]API on port 8000.
sglang serve Axion1-0/Axion-1.0-35B --host 0.0.0.0 --port 30000services:
sglang:
image: lmsysorg/sglang:latest
command: sglang serve Axion1-0/Axion-1.0-35B --host 0.0.0.0 --port 30000
ports:
- "30000:30000"
ipc: host
volumes:
- ~/.cache/huggingface:/root/.cache/huggingface
deploy:
resources:
reservations:
devices:
- driver: nvidia
count: all
capabilities: [gpu]API on port 30000.
from transformers import pipeline
pipe = pipeline("text-generation", model="Axion1-0/Axion-1.0-35B", dtype="auto", device_map="auto")
messages = [{"role": "user", "content": "Explain self-hosting in one paragraph."}]
out = pipe(messages, max_new_tokens=512)
print(out[0]["generated_text"][-1]["content"])Chat models that fit the RTX A6000 comfortably
All that fit →| Model | Params | Best quant | Memory | Speed |
|---|---|---|---|---|
| 36BA3B | Q8_0 | ≈38 GBFits in memory | ~133 tok/s | |
| 31.2BA4.6B | Q8_0 | ≈39 GBFits in memory | ~86 tok/s | |
| 32.8B | Q8_0 | ≈37 GBFits in memory | ~12 tok/s | |
| 39.8BA1.3B | Q8_0 | ≈43 GBFits in memory | ~318 tok/s | |
| 20.9BA4.2B | Q8_0 | ≈13 GBFits in memory | ~95 tok/s | |
| 30.5BA3B | Q8_0 | ≈33 GBFits in memory | ~133 tok/s |
Other GPUs that run Axion-1.0-35B
Frequently asked questions
- Can the RTX A6000 run Axion-1.0-35B?
- Yes. The RTX A6000 runs Axion-1.0-35B fully in VRAM at Q8_0 (about 37 GB of 48 GB), at roughly 102 tokens/s.
- How fast does Axion-1.0-35B run on the RTX A6000?
- An estimate from memory bandwidth gives about 102 tokens/s at Q8_0.
- Which quantisation of Axion-1.0-35B should I use on the RTX A6000?
- Q8_0: the largest one that fits. Expected quality: lossless compared with the full-precision weights.
Memory and speed are estimates from the model's size and the card's memory bandwidth; real numbers depend on the runtime, drivers and context length. Community figures are medians of user reports.