GR

granite 20b functioncalling i1

GraniteGGUF by mradermacherUpdated 2024-08-02
Download on Hugging Face
Parameters20B
Context8K
Layers52
Architecturestarcoder
Smallest quant4.5 GB
Quick answer

granite 20b functioncalling i1 needs about 13.5 GB of memory at Q4_K_M (a 12.8 GB file) with an 8K context window, so it fits on a 16 GB GPU. This repository has 21 quants, from 4.5 GB (IQ1_S) to 16.6 GB (Q6_K).

Granite‑20B FunctionCalling i1 – 20B starcoder model with function‑calling finetune

Granite‑20B FunctionCalling i1 is a 20‑billion‑parameter starcoder model fine‑tuned for function‑calling tasks. It supports a 8192‑token context window and is released under the Apache‑2.0 license. The model is available in multiple GGUF quantisations.

Good at

  • Function‑calling instruction handling
  • Nested and chained function execution
  • Parameter‑value pair detection

Limits

  • No vision support
  • Requires 8‑k context for full capability
  • Large VRAM needed for higher‑quality quants

Best for

  • Building function‑calling assistants
  • Automating API workflows
  • Testing function‑calling logic

Who it’s for. Developers and researchers building LLM‑based tools that need reliable function‑calling behaviour. The model is suitable for integration into applications that require structured output and API interaction.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
IQ1_S4.5 GB 5.2 GB
Fits Get file →
IQ1_M4.9 GB 5.6 GB
Fits Get file →
IQ2_XXS5.6 GB 6.3 GB
Fits Get file →
IQ2_XS6.2 GB 6.9 GB
Fits Get file →
IQ2_S6.5 GB 7.2 GB
Tight Get file →
IQ2_M7.1 GB 7.8 GB
Tight Get file →
Q2_K7.9 GB 8.6 GB
Too big Get file →
IQ3_XXS8.1 GB 8.8 GB
Too big Get file →
IQ3_XS8.7 GB 9.4 GB
Too big Get file →
IQ3_S8.9 GB 9.7 GB
Too big Get file →
Q3_K_S8.9 GB 9.7 GB
Too big Get file →
IQ3_M9.6 GB 10.3 GB
Too big Get file →
Q3_K_M10.6 GB 11.3 GB
Too big Get file →
IQ4_XS10.9 GB 11.7 GB
Too big Get file →
Q4_011.6 GB 12.3 GB
Too big Get file →
Q4_K_S11.7 GB 12.4 GB
Too big Get file →
Q3_K_L11.7 GB 12.5 GB
Too big Get file →
Q4_K_M12.8 GB 13.5 GB
Too big Get file →
Q5_K_S14.0 GB 14.7 GB
Too big Get file →
Q5_K_M14.8 GB 15.5 GB
Too big Get file →
Q6_K16.6 GB 17.4 GB
Too big Get file →

For 8 GB VRAM, use IQ1_S (4.52 GB file, ~5.2 GB VRAM). For 12 GB VRAM, IQ2_S (6.53 GB file, ~7.2 GB VRAM) or Q4_0 (11.61 GB file, ~12.3 GB VRAM). Higher‑quality quants like Q5_K_M need 15–16 GB VRAM.

What GPU do you need for granite 20b functioncalling i1?

These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.

  • 4 GB VRAM: no quant fits at an 8K context.
  • 6 GB VRAM: the best quant that fits is IQ1_M (4.9 GB file, about 5.6 GB in use).
  • 8 GB VRAM: the best quant that fits is IQ2_M (7.1 GB file, about 7.8 GB in use).
  • 12 GB VRAM: the best quant that fits is IQ4_XS (10.9 GB file, about 11.7 GB in use).
  • 16 GB VRAM: the best quant that fits is Q5_K_M (14.8 GB file, about 15.5 GB in use).
  • 24 GB VRAM: the best quant that fits is Q6_K (16.6 GB file, about 17.4 GB in use).

Which granite 20b functioncalling i1 quant should you choose?

Q4_K_M is the usual starting point for granite 20b functioncalling i1: it balances file size and quality well. Here it is a 12.8 GB file.

If memory is tight, the smallest file is IQ1_S at 4.5 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architecturestarcoder
Parameters20B
Layers52
Trained context8,192 tokens
KV cache (fp16)26 KB per token

Source

Quantized bymradermacher
FamilyGranite
Licenseapache-2.0
Downloads (HF)3,865
Last updated2024-08-02

Frequently asked questions about granite 20b functioncalling i1

How much VRAM does granite 20b functioncalling i1 need?

About 13.5 GB at Q4_K_M with an 8K context window. That is the 12.8 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.

Can I run granite 20b functioncalling i1 on an 8 GB GPU?

Yes, with IQ2_M: the 7.1 GB file needs about 7.8 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of granite 20b functioncalling i1 GGUF?

It depends on the quant: IQ1_S is 4.5 GB, IQ1_M is 4.9 GB, IQ2_XXS is 5.6 GB, IQ2_XS is 6.2 GB, IQ2_S is 6.5 GB, IQ2_M is 7.1 GB and 15 more.

What context length does granite 20b functioncalling i1 support?

The GGUF header lists a trained context length of 8,192 tokens (8K). The KV cache grows with the context you use: about 0.2 GB at 8K and 0.2 GB at 8K.

Where can I download granite 20b functioncalling i1 GGUF?

The files are on Hugging Face in the mradermacher/granite-20b-functioncalling-i1-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

What license does granite 20b functioncalling i1 use?

Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.

Can I run Granite‑20B FunctionCalling i1 on 8 GB VRAM?

Yes, using the IQ1_S quantisation which requires about 5.2 GB VRAM at 8‑k context.

Does this model support vision tasks?

No, the model is text‑only and has no vision capabilities.

What license applies to this model?

The model is released under the Apache‑2.0 license.

Other GGUFs of granite-20b-functioncalling

Similar models

Browse all →

More from mradermacher

All by mradermacher →

More Granite models

All Granite →

Other medium models

All medium models →