Can the Arc Pro B60 run Axion-1.0-35B?
Axion-1.0-35B·35.1B (3.9B active)·Arc Pro B60·24 GB VRAM
Yes. The Arc Pro B60 runs Axion-1.0-35B fully in VRAM at Q4_K_M (about 22 GB of 24 GB), at roughly 106 tokens/s.
- best quant
- Q4_K_M
- needs
- 22 GB
- usable
- 24 GB
- est. speed
- ~106 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 Arc Pro B60
| Quant | Memory | Fit | Speed |
|---|---|---|---|
| Q2_K | 14 GB | fits | ~196 tok/s |
| Q3_K_M | 18 GB | fits | ~132 tok/s |
| Q4_K_M pick | 22 GB | fits | ~106 tok/s |
| Q5_K_M | 25 GB | offload | ~67 tok/s |
| Q6_K | 29 GB | offload | ~36 tok/s |
| Q8_0 | 37 GB | offload | ~18 tok/s |
| FP16 / BF16 | 70 GB | too big | — |
Speed is a bandwidth-based estimate for generating text (456 GB/s); prompt processing and long contexts are slower.
Measured speed on the Arc Pro B60
No community reports for this pair yet.
Report your own speed →Run Axion-1.0-35B on the Arc Pro B60
Using Q4_K_M, the best fit for Arc Pro B60.
ollama run hf.co/mradermacher/Axion-1.0-35B-GGUF:Q4_K_MOllama’s ROCm/CUDA builds don’t cover this GPU. Recent Ollama releases use Vulkan when its Vulkan backend and driver are installed (older ones needed OLLAMA_VULKAN=1); llama.cpp or LM Studio with Vulkan are the safer bet.
llama-server -hf mradermacher/Axion-1.0-35B-GGUF:Q4_K_MNeeds a Vulkan build of llama.cpp. Downloads the GGUF on first run.
docker run -d --name llama --device /dev/dri -p 8080:8080 \
-v ~/.cache/llama.cpp:/root/.cache/llama.cpp \
ghcr.io/ggml-org/llama.cpp:server-vulkan \
-hf mradermacher/Axion-1.0-35B-GGUF:Q4_K_M --host 0.0.0.0 --port 8080 -ngl 99Server and web UI on port 8080.
lms get mradermacher/Axion-1.0-35B-GGUF@Q4_K_MThen load it from the LM Studio app or with `lms load`.
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 Arc Pro B60 comfortably
All that fit →| Model | Params | Best quant | Memory | Speed |
|---|---|---|---|---|
| 36BA3B | Q4_K_M | ≈23 GBFits in memory | ~138 tok/s | |
| 32.8B | Q4_K_M | ≈22 GBFits in memory | ~13 tok/s | |
| 30.5BA3B | Q5_K_M | ≈22 GBFits in memory | ~118 tok/s | |
| 20.9BA4.2B | Q8_0 | ≈13 GBFits in memory | ~56 tok/s | |
| 32.8B | Q4_K_M | ≈22 GBFits in memory | ~13 tok/s | |
| 33.4BA2.2B | Q4_K_M | ≈22 GBFits in memory | ~185 tok/s |
Other GPUs that run Axion-1.0-35B
Frequently asked questions
- Can the Arc Pro B60 run Axion-1.0-35B?
- Yes. The Arc Pro B60 runs Axion-1.0-35B fully in VRAM at Q4_K_M (about 22 GB of 24 GB), at roughly 106 tokens/s.
- How fast does Axion-1.0-35B run on the Arc Pro B60?
- An estimate from memory bandwidth gives about 106 tokens/s at Q4_K_M.
- Which quantisation of Axion-1.0-35B should I use on the Arc Pro B60?
- Q4_K_M: the largest one that fits. Expected quality: small loss 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.