Yes. The Arc A380 runs S5-nano fully in VRAM at Q6_K (about 5.2 GB of 6.0 GB), at roughly 27 tokens/s.
- best quant
- Q6_K
- needs
- 5.2 GB
- usable
- 6.0 GB
- est. speed
- ~27 tok/s
Estimates for an 8K context; offload assumes 32 GB of system RAM.Try other contexts on the S5-nano page →
Every quantisation of S5-nano on the Arc A380
| Quant | Memory | Fit | Speed |
|---|---|---|---|
| Q2_K | 3.3 GB | fits | ~67 tok/s |
| Q3_K_M | 3.6 GB | fits | ~45 tok/s |
| Q4_K_M | 4.2 GB | fits | ~36 tok/s |
| Q5_K_M | 4.8 GB | fits | ~31 tok/s |
| Q6_K pick | 5.2 GB | fits | ~27 tok/s |
| Q8_0 | 6.0 GB | tight | ~21 tok/s |
| FP16 / BF16 | 10.0 GB | offload | ~6 tok/s |
Speed is a bandwidth-based estimate for generating text (186 GB/s); prompt processing and long contexts are slower.
Measured speed on the Arc A380
No community reports for this pair yet.
Report your own speed →Run S5-nano on the Arc A380
Using Q6_K, the best fit for Arc A380.
ollama run hf.co/bartowski/maritaca-ai_S5-nano-GGUF:Q6_KOllama’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 bartowski/maritaca-ai_S5-nano-GGUF:Q6_KNeeds 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 bartowski/maritaca-ai_S5-nano-GGUF:Q6_K --host 0.0.0.0 --port 8080 -ngl 99Server and web UI on port 8080.
lms get bartowski/maritaca-ai_S5-nano-GGUF@Q6_KThen load it from the LM Studio app or with `lms load`.
from transformers import pipeline
pipe = pipeline("image-text-to-text", model="maritaca-ai/S5-nano", dtype="auto", device_map="auto")
messages = [
{
"role": "user",
"content": [
{"type": "image", "url": "https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/bee.jpg"},
{"type": "text", "text": "Describe this image."},
],
}
]
out = pipe(text=messages, max_new_tokens=256)
print(out[0]["generated_text"][-1]["content"])Vision models that fit the Arc A380 comfortably
All that fit →| Model | Params | Best quant | Memory | Speed |
|---|---|---|---|---|
| 4.7B | Q6_K | ≈4.9 GBFits in memory | ~27 tok/s | |
| 4.3B | Q8_0 | ≈5.2 GBFits in memory | ~22 tok/s | |
| 4.4B | Q6_K | ≈4.9 GBFits in memory | ~28 tok/s | |
| 5B | Q8_0 | ≈5.6 GBFits in memory | ~19 tok/s | |
| 4.3B | Q8_0 | ≈5.6 GBFits in memory | ~22 tok/s | |
| 4.3B | Q8_0 | ≈5.6 GBFits in memory | ~22 tok/s |
Other GPUs that run S5-nano
Frequently asked questions
- Can the Arc A380 run S5-nano?
- Yes. The Arc A380 runs S5-nano fully in VRAM at Q6_K (about 5.2 GB of 6.0 GB), at roughly 27 tokens/s.
- How fast does S5-nano run on the Arc A380?
- An estimate from memory bandwidth gives about 27 tokens/s at Q6_K.
- Which quantisation of S5-nano should I use on the Arc A380?
- Q6_K: the largest one that fits. Expected quality: near-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.