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.

ibm-granite logo

Can the RTX 4060 run granite-4.1-3b-llmon-preview?

granite-4.1-3b-llmon-preview·3.7B·GeForce RTX 4060·8 GB VRAM

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

Yes. The RTX 4060 runs granite-4.1-3b-llmon-preview fully in VRAM at Q8_0 (about 4.9 GB of 8.0 GB), at roughly 38 tokens/s.

best quant
Q8_0
needs
4.9 GB
usable
8.0 GB
est. speed
~38 tok/s

Estimates for an 8K context; offload assumes 32 GB of system RAM.Try other contexts on the granite-4.1-3b-llmon-preview page →

Every quantisation of granite-4.1-3b-llmon-preview on the RTX 4060

QuantQualityMemoryFitSpeed
Q2_K Heavy loss2.6 GBfits~124 tok/s
Q3_K_M Noticeable loss2.9 GBfits~84 tok/s
Q4_K_M Small loss3.3 GBfits~67 tok/s
Q5_K_M Near-lossless3.7 GBfits~57 tok/s
Q6_K Near-lossless4.1 GBfits~50 tok/s
Q8_0 pickLossless4.9 GBfits~38 tok/s
FP16 / BF16 Lossless8.3 GBoffload~18 tok/s

Speed is a bandwidth-based estimate for generating text (272 GB/s); prompt processing and long contexts are slower.

Measured speed on the RTX 4060

No community reports for this pair yet.

Report your own speed →

Run granite-4.1-3b-llmon-preview on the RTX 4060

Using Q8_0, the best fit for RTX 4060.

llama.cpp · OpenAI-compatible server with a web UIdocs
llama-server -hf liodon-ai/granite-4.1-3b-llmon-preview-GGUF:Q8_0

Downloads the GGUF on first run. Installed through llama.app? The same flags work with `llama serve`.

vLLM · Serve an OpenAI-compatible APIdocs
vllm serve ibm-granite/granite-4.1-3b-llmon-preview
vLLM · Smaller FP8 builddocs
vllm serve liodon-ai/granite-4.1-3b-llmon-preview-FP8
vLLM · Docker Compose (NVIDIA)docs
services:
  vllm:
    image: vllm/vllm-openai:latest
    command: ibm-granite/granite-4.1-3b-llmon-preview
    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 an OpenAI-compatible APIdocs
sglang serve ibm-granite/granite-4.1-3b-llmon-preview --host 0.0.0.0 --port 30000
SGLang · Docker Compose (NVIDIA)docs
services:
  sglang:
    image: lmsysorg/sglang:latest
    command: sglang serve ibm-granite/granite-4.1-3b-llmon-preview --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.

Transformers · Chat with the pipeline APIdocs
from transformers import pipeline

pipe = pipeline("text-generation", model="ibm-granite/granite-4.1-3b-llmon-preview", 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 4060 comfortably

All that fit →
ModelParamsBest quantMemorySpeedLicence
4BQ8_0≈5.8 GBFits in memory~35 tok/sCommercial OK
3.2BQ8_0≈4.7 GBFits in memory~44 tok/sConditions
3.8BQ8_0≈5.5 GBFits in memory~37 tok/sCommercial OK
3.1BQ8_0≈4.3 GBFits in memory~46 tok/sNon-commercial
ibm-granite logogranite-4.2-3bibm-granite
3.7BQ8_0≈4.9 GBFits in memory~38 tok/sCommercial OK
4BQ8_0≈5.8 GBFits in memory~35 tok/sCommercial OK

Other GPUs that run granite-4.1-3b-llmon-preview

Frequently asked questions

Can the RTX 4060 run granite-4.1-3b-llmon-preview?
Yes. The RTX 4060 runs granite-4.1-3b-llmon-preview fully in VRAM at Q8_0 (about 4.9 GB of 8.0 GB), at roughly 38 tokens/s.
How fast does granite-4.1-3b-llmon-preview run on the RTX 4060?
An estimate from memory bandwidth gives about 38 tokens/s at Q8_0.
Which quantisation of granite-4.1-3b-llmon-preview should I use on the RTX 4060?
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.