CoolFace
Modelpublic

bartowski/allenai_Olmo-3.1-32B-Think-GGUF

sourceHugging Faceapache-2.0updated 10mo agoView on Hugging Face
6likes12kdownloads
Model Card

Llamacpp imatrix Quantizations of Olmo-3.1-32B-Think by allenai

Using <a href="https://github.com/ggml-org/llama.cpp/">llama.cpp</a> release <a href="https://github.com/ggml-org/llama.cpp/releases/tag/b7340">b7340</a> for quantization.

Original model: https://huggingface.co/allenai/Olmo-3.1-32B-Think

All quants made using imatrix option with dataset from here combined with a subset of combinedallsmall.parquet from Ed Addario here

Run them in LM Studio

Run them directly with llama.cpp, or any other llama.cpp based project

Prompt format

<|im_start|>system
{system_prompt} You do not currently have access to any functions. <functions></functions><|im_end|>
<|im_start|>user
{prompt}<|im_end|>
<|im_start|>assistant
<think>

Download a file (not the whole branch) from below:

FilenameQuant typeFile SizeSplitDescription
Olmo-3.1-32B-Think-bf16.ggufbf1664.47GBtrueFull BF16 weights.
Olmo-3.1-32B-Think-Q8_0.ggufQ8_034.25GBfalseExtremely high quality, generally unneeded but max available quant.
Olmo-3.1-32B-Think-Q6_K_L.ggufQ6KL26.70GBfalseUses Q8_0 for embed and output weights. Very high quality, near perfect, recommended.
Olmo-3.1-32B-Think-Q6_K.ggufQ6_K26.45GBfalseVery high quality, near perfect, recommended.
Olmo-3.1-32B-Think-Q5_K_L.ggufQ5KL23.18GBfalseUses Q8_0 for embed and output weights. High quality, recommended.
Olmo-3.1-32B-Think-Q5_K_M.ggufQ5KM22.86GBfalseHigh quality, recommended.
Olmo-3.1-32B-Think-Q5_K_S.ggufQ5KS22.24GBfalseHigh quality, recommended.
Olmo-3.1-32B-Think-Q4_1.ggufQ4_120.25GBfalseLegacy format, similar performance to Q4KS but with improved tokens/watt on Apple silicon.
Olmo-3.1-32B-Think-Q4_K_L.ggufQ4KL19.86GBfalseUses Q8_0 for embed and output weights. Good quality, recommended.
Olmo-3.1-32B-Think-Q4_K_M.ggufQ4KM19.48GBfalseGood quality, default size for most use cases, recommended.
Olmo-3.1-32B-Think-Q4_K_S.ggufQ4KS18.42GBfalseSlightly lower quality with more space savings, recommended.
Olmo-3.1-32B-Think-Q4_0.ggufQ4_018.34GBfalseLegacy format, offers online repacking for ARM and AVX CPU inference.
Olmo-3.1-32B-Think-IQ4_NL.ggufIQ4_NL18.31GBfalseSimilar to IQ4_XS, but slightly larger. Offers online repacking for ARM CPU inference.
Olmo-3.1-32B-Think-Q3_K_XL.ggufQ3KXL17.36GBfalseUses Q8_0 for embed and output weights. Lower quality but usable, good for low RAM availability.
Olmo-3.1-32B-Think-IQ4_XS.ggufIQ4_XS17.33GBfalseDecent quality, smaller than Q4KS with similar performance, recommended.
Olmo-3.1-32B-Think-Q3_K_L.ggufQ3KL16.91GBfalseLower quality but usable, good for low RAM availability.
Olmo-3.1-32B-Think-Q3_K_M.ggufQ3KM15.60GBfalseLow quality.
Olmo-3.1-32B-Think-IQ3_M.ggufIQ3_M14.48GBfalseMedium-low quality, new method with decent performance comparable to Q3KM.
Olmo-3.1-32B-Think-Q3_K_S.ggufQ3KS14.06GBfalseLow quality, not recommended.
Olmo-3.1-32B-Think-IQ3_XS.ggufIQ3_XS13.37GBfalseLower quality, new method with decent performance, slightly better than Q3KS.
Olmo-3.1-32B-Think-IQ3_XXS.ggufIQ3_XXS12.54GBfalseLower quality, new method with decent performance, comparable to Q3 quants.
Olmo-3.1-32B-Think-Q2_K_L.ggufQ2KL12.51GBfalseUses Q8_0 for embed and output weights. Very low quality but surprisingly usable.
Olmo-3.1-32B-Think-Q2_K.ggufQ2_K12.01GBfalseVery low quality but surprisingly usable.
Olmo-3.1-32B-Think-IQ2_M.ggufIQ2_M10.97GBfalseRelatively low quality, uses SOTA techniques to be surprisingly usable.
Olmo-3.1-32B-Think-IQ2_S.ggufIQ2_S10.09GBfalseLow quality, uses SOTA techniques to be usable.
Olmo-3.1-32B-Think-IQ2_XS.ggufIQ2_XS9.69GBfalseLow quality, uses SOTA techniques to be usable.
Olmo-3.1-32B-Think-IQ2_XXS.ggufIQ2_XXS8.76GBfalseVery low quality, uses SOTA techniques to be usable.

Embed/output weights

Some of these quants (Q3KXL, Q4KL etc) are the standard quantization method with the embeddings and output weights quantized to Q8_0 instead of what they would normally default to.

Downloading using huggingface-cli

<details> <summary>Click to view download instructions</summary>

First, make sure you have hugginface-cli installed:

pip install -U "huggingface_hub[cli]"

Then, you can target the specific file you want:

huggingface-cli download bartowski/allenai_Olmo-3.1-32B-Think-GGUF --include "allenai_Olmo-3.1-32B-Think-Q4_K_M.gguf" --local-dir ./

If the model is bigger than 50GB, it will have been split into multiple files. In order to download them all to a local folder, run:

huggingface-cli download bartowski/allenai_Olmo-3.1-32B-Think-GGUF --include "allenai_Olmo-3.1-32B-Think-Q8_0/*" --local-dir ./

You can either specify a new local-dir (allenaiOlmo-3.1-32B-Think-Q80) or download them all in place (./)

</details>

ARM/AVX information

Previously, you would download Q4044/48/8_8, and these would have their weights interleaved in memory in order to improve performance on ARM and AVX machines by loading up more data in one pass.

Now, however, there is something called "online repacking" for weights. details in this PR. If you use Q4_0 and your hardware would benefit from repacking weights, it will do it automatically on the fly.

As of llama.cpp build b4282 you will not be able to run the Q40XX files and will instead need to use Q40.

Additionally, if you want to get slightly better quality for , you can use IQ4NL thanks to [this PR](https://github.com/ggml-org/llama.cpp/pull/10541) which will also repack the weights for ARM, though only the 44 for now. The loading time may be slower but it will result in an overall speed incrase.

<details> <summary>Click to view Q40X_X information (deprecated</summary>

I'm keeping this section to show the potential theoretical uplift in performance from using the Q4_0 with online repacking.

<details> <summary>Click to view benchmarks on an AVX2 system (EPYC7702)</summary>

modelsizeparamsbackendthreadstestt/s% (vs Q4_0)
qwen2 3B Q4_01.70 GiB3.09 BCPU64pp512204.03 ± 1.03100%
qwen2 3B Q4_01.70 GiB3.09 BCPU64pp1024282.92 ± 0.19100%
qwen2 3B Q4_01.70 GiB3.09 BCPU64pp2048259.49 ± 0.44100%
qwen2 3B Q4_01.70 GiB3.09 BCPU64tg12839.12 ± 0.27100%
qwen2 3B Q4_01.70 GiB3.09 BCPU64tg25639.31 ± 0.69100%
qwen2 3B Q4_01.70 GiB3.09 BCPU64tg51240.52 ± 0.03100%
qwen2 3B Q4KM1.79 GiB3.09 BCPU64pp512301.02 ± 1.74147%
qwen2 3B Q4KM1.79 GiB3.09 BCPU64pp1024287.23 ± 0.20101%
qwen2 3B Q4KM1.79 GiB3.09 BCPU64pp2048262.77 ± 1.81101%
qwen2 3B Q4KM1.79 GiB3.09 BCPU64tg12818.80 ± 0.9948%
qwen2 3B Q4KM1.79 GiB3.09 BCPU64tg25624.46 ± 3.0483%
qwen2 3B Q4KM1.79 GiB3.09 BCPU64tg51236.32 ± 3.5990%
qwen2 3B Q408_81.69 GiB3.09 BCPU64pp512271.71 ± 3.53133%
qwen2 3B Q408_81.69 GiB3.09 BCPU64pp1024279.86 ± 45.63100%
qwen2 3B Q408_81.69 GiB3.09 BCPU64pp2048320.77 ± 5.00124%
qwen2 3B Q408_81.69 GiB3.09 BCPU64tg12843.51 ± 0.05111%
qwen2 3B Q408_81.69 GiB3.09 BCPU64tg25643.35 ± 0.09110%
qwen2 3B Q408_81.69 GiB3.09 BCPU64tg51242.60 ± 0.31105%

Q408_8 offers a nice bump to prompt processing and a small bump to text generation

</details>

</details>

Which file should I choose?

<details> <summary>Click here for details</summary>

A great write up with charts showing various performances is provided by Artefact2 here

The first thing to figure out is how big a model you can run. To do this, you'll need to figure out how much RAM and/or VRAM you have.

If you want your model running as FAST as possible, you'll want to fit the whole thing on your GPU's VRAM. Aim for a quant with a file size 1-2GB smaller than your GPU's total VRAM.

If you want the absolute maximum quality, add both your system RAM and your GPU's VRAM together, then similarly grab a quant with a file size 1-2GB Smaller than that total.

Next, you'll need to decide if you want to use an 'I-quant' or a 'K-quant'.

If you don't want to think too much, grab one of the K-quants. These are in format 'QXKX', like Q5KM.

If you want to get more into the weeds, you can check out this extremely useful feature chart:

llama.cpp feature matrix

But basically, if you're aiming for below Q4, and you're running cuBLAS (Nvidia) or rocBLAS (AMD), you should look towards the I-quants. These are in format IQXX, like IQ3M. These are newer and offer better performance for their size.

These I-quants can also be used on CPU, but will be slower than their K-quant equivalent, so speed vs performance is a tradeoff you'll have to decide.

</details>

Credits

Thank you kalomaze and Dampf for assistance in creating the imatrix calibration dataset.

Thank you ZeroWw for the inspiration to experiment with embed/output.

Thank you to LM Studio for sponsoring my work.

Want to support my work? Visit my ko-fi page here: https://ko-fi.com/bartowski