selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

Axion1-0 logo

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

Saved in this browser, used on every model page.
Yes

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

QuantQualityMemoryFitSpeed
Q2_K Heavy loss14 GBfits~196 tok/s
Q3_K_M Noticeable loss18 GBfits~132 tok/s
Q4_K_M pickSmall loss22 GBfits~106 tok/s
Q5_K_M Near-lossless25 GBoffload~67 tok/s
Q6_K Near-lossless29 GBoffload~36 tok/s
Q8_0 Lossless37 GBoffload~18 tok/s
FP16 / BF16 Lossless70 GBtoo 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 · Q4_K_M straight from Hugging Facedocs
ollama run hf.co/mradermacher/Axion-1.0-35B-GGUF:Q4_K_M

Ollama’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.cpp · OpenAI-compatible server with a web UIdocs
llama-server -hf mradermacher/Axion-1.0-35B-GGUF:Q4_K_M

Needs a Vulkan build of llama.cpp. Downloads the GGUF on first run.

llama.cpp · Docker with Vulkandocs
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 99

Server and web UI on port 8080.

LM Studio · Download with the lms CLIdocs
lms get mradermacher/Axion-1.0-35B-GGUF@Q4_K_M

Then load it from the LM Studio app or with `lms load`.

Transformers · Chat with the pipeline APIdocs
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 →
ModelParamsBest quantMemorySpeedLicence
36BA3BQ4_K_M≈23 GBFits in memory~138 tok/sCommercial OK
32.8BQ4_K_M≈22 GBFits in memory~13 tok/sCommercial OK
30.5BA3BQ5_K_M≈22 GBFits in memory~118 tok/sCommercial OK
20.9BA4.2BQ8_0≈13 GBFits in memory~56 tok/sCommercial OK
32.8BQ4_K_M≈22 GBFits in memory~13 tok/sCommercial OK
33.4BA2.2BQ4_K_M≈22 GBFits in memory~185 tok/sCommercial OK

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.