Yes. The RTX A6000 runs GLiDE-27B fully in VRAM at Q8_0 (about 30 GB of 48 GB), at roughly 15 tokens/s.
- best quant
- Q8_0
- needs
- 30 GB
- usable
- 48 GB
- est. speed
- ~15 tok/s
Estimates for an 8K context; offload assumes 32 GB of system RAM.Try other contexts on the GLiDE-27B page →
Every quantisation of GLiDE-27B on the RTX A6000
| Quant | Memory | Fit | Speed |
|---|---|---|---|
| Q2_K | 11 GB | fits | ~49 tok/s |
| Q3_K_M | 15 GB | fits | ~33 tok/s |
| Q4_K_M | 19 GB | fits | ~27 tok/s |
| Q5_K_M | 21 GB | fits | ~23 tok/s |
| Q6_K | 24 GB | fits | ~20 tok/s |
| Q8_0 pick | 30 GB | fits | ~15 tok/s |
| FP16 / BF16 | 54 GB | offload | ~3.7 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 GLiDE-27B on the RTX A6000
Using Q4_K_M, the best fit for RTX A6000.
llama-server -hf seamon67/GLiDE-27B-GGUF:Q4_K_MDownloads the GGUF on first run. Installed through llama.app? The same flags work with `llama serve`.
vllm serve fastino/GLiDE-27Bservices:
vllm:
image: vllm/vllm-openai:latest
command: fastino/GLiDE-27B
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 fastino/GLiDE-27B --host 0.0.0.0 --port 30000services:
sglang:
image: lmsysorg/sglang:latest
command: sglang serve fastino/GLiDE-27B --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("image-text-to-text", model="fastino/GLiDE-27B", 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 RTX A6000 comfortably
All that fit →| Model | Params | Best quant | Memory | Speed |
|---|---|---|---|---|
| 25.8BA4B | Q8_0 | ≈29 GBFits in memory | ~99 tok/s | |
| 27.8B | Q8_0 | ≈31 GBFits in memory | ~14 tok/s | |
| 27.8B | Q8_0 | ≈30 GBFits in memory | ~14 tok/s | |
| 31.3B | Q8_0 | ≈40 GBFits in memory | ~13 tok/s | |
| 27.4B | Q8_0 | ≈32 GBFits in memory | ~14 tok/s | |
| 27.8B | Q8_0 | ≈30 GBFits in memory | ~14 tok/s |
Other GPUs that run GLiDE-27B
Frequently asked questions
- Can the RTX A6000 run GLiDE-27B?
- Yes. The RTX A6000 runs GLiDE-27B fully in VRAM at Q8_0 (about 30 GB of 48 GB), at roughly 15 tokens/s.
- How fast does GLiDE-27B run on the RTX A6000?
- An estimate from memory bandwidth gives about 15 tokens/s at Q8_0.
- Which quantisation of GLiDE-27B 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.