/ Модель

Характеристики

Базовая модель
Ring-mini-2.0
Опубликована
20 окт 2025

inclusionAI_Ring-mini-2.0-GGUF

Генерация текстаТекст → текст11 профессий

bartowski/inclusionAI_Ring-mini-2.0-GGUF — это набор квантизованных версий языковой модели Ring-mini-2.0, разработанной inclusionAI.

1 478скачиваний за 30 дней6лайковвеса обновлены20 окт 2025

Бенчмарки

Как модель справилась с задачами пользователей ailist и что о ней публикуют открытые лидерборды

Публичные оценки

Из открытых лидербордов. Сравнивайте результаты одного теста при одинаковых условиях — отсутствие оценки не значит, что модель хуже.

В подключённых источниках результатов для этой модели пока нет.

Что умеет модель

Описание составлено по карточке модели и метаданным Hugging Face

Модель предназначена для генерации текста и запускается в формате GGUF через llama.cpp, LM Studio и другие совместимые приложения. В README указано, что квантизация выполнена с использованием llama.cpp и метода imatrix.

Доступны варианты от BF16 до низкобитных форматов Q8_0, Q6_K, Q5_K, Q4_K, IQ4 и Q3_K с размером файлов примерно от 6,82 до 32,54 ГБ. Более крупные варианты обеспечивают более высокое качество, а Q4_K_M указан как вариант по умолчанию для большинства сценариев; Q6_K и Q6_K_L отмечены как версии очень высокого качества. Модель поддерживает формат промпта с ролями SYSTEM, HUMAN и ASSISTANT, а также специальным маркером рассуждений.

Набор подходит для локального вывода текста на устройствах с ограниченными ресурсами, если выбрать подходящий уровень квантизации. Ограничения, архитектура, количество параметров, поддерживаемые языки, размер контекстного окна и мультимодальные возможности в README не указаны. Лицензия модели также не указана, поэтому условия использования следует уточнять в описании исходной модели inclusionAI/Ring-mini-2.0.

Для каких профессий подходит11

Разделы каталога профессий, в задачах которых используется эта модель

Все профессии

Также подходит для

Карточка модели

README от автора на Hugging Face, как он его опубликовал

Открыть на Hugging Face

Llamacpp imatrix Quantizations of Ring-mini-2.0 by inclusionAI

Using llama.cpp release b6810 for quantization.

Original model: https://huggingface.co/inclusionAI/Ring-mini-2.0

All quants made using imatrix option with dataset from here combined with a subset of combined_all_small.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

<role>SYSTEM</role>{system_prompt}<role>HUMAN</role>{prompt}<role>ASSISTANT</role><role>ASSISTANT</role><think>

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

FilenameQuant typeFile SizeSplitDescription
Ring-mini-2.0-bf16.ggufbf1632.54GBfalseFull BF16 weights.
Ring-mini-2.0-Q8_0.ggufQ8_017.31GBfalseExtremely high quality, generally unneeded but max available quant.
Ring-mini-2.0-Q6_K_L.ggufQ6_K_L13.54GBfalseUses Q8_0 for embed and output weights. Very high quality, near perfect, recommended.
Ring-mini-2.0-Q6_K.ggufQ6_K13.39GBfalseVery high quality, near perfect, recommended.
Ring-mini-2.0-Q5_K_L.ggufQ5_K_L11.82GBfalseUses Q8_0 for embed and output weights. High quality, recommended.
Ring-mini-2.0-Q5_K_M.ggufQ5_K_M11.62GBfalseHigh quality, recommended.
Ring-mini-2.0-Q5_K_S.ggufQ5_K_S11.27GBfalseHigh quality, recommended.
Ring-mini-2.0-Q4_1.ggufQ4_110.28GBfalseLegacy format, similar performance to Q4_K_S but with improved tokens/watt on Apple silicon.
Ring-mini-2.0-Q4_K_L.ggufQ4_K_L10.18GBfalseUses Q8_0 for embed and output weights. Good quality, recommended.
Ring-mini-2.0-Q4_K_M.ggufQ4_K_M9.94GBfalseGood quality, default size for most use cases, recommended.
Ring-mini-2.0-Q4_K_S.ggufQ4_K_S9.60GBfalseSlightly lower quality with more space savings, recommended.
Ring-mini-2.0-Q4_0.ggufQ4_09.44GBfalseLegacy format, offers online repacking for ARM and AVX CPU inference.
Ring-mini-2.0-IQ4_NL.ggufIQ4_NL9.30GBfalseSimilar to IQ4_XS, but slightly larger. Offers online repacking for ARM CPU inference.
Ring-mini-2.0-IQ4_XS.ggufIQ4_XS8.80GBfalseDecent quality, smaller than Q4_K_S with similar performance, recommended.
Ring-mini-2.0-Q3_K_XL.ggufQ3_K_XL8.10GBfalseUses Q8_0 for embed and output weights. Lower quality but usable, good for low RAM availability.
Ring-mini-2.0-Q3_K_L.ggufQ3_K_L7.82GBfalseLower quality but usable, good for low RAM availability.
Ring-mini-2.0-Q3_K_M.ggufQ3_K_M7.54GBfalseLow quality.
Ring-mini-2.0-IQ3_M.ggufIQ3_M7.54GBfalseMedium-low quality, new method with decent performance comparable to Q3_K_M.
Ring-mini-2.0-Q3_K_S.ggufQ3_K_S7.20GBfalseLow quality, not recommended.
Ring-mini-2.0-IQ3_XS.ggufIQ3_XS6.82GBfalseLower quality, new method with decent performance, slightly better than Q3_K_S.
Ring-mini-2.0-IQ3_XXS.ggufIQ3_XXS6.55GBfalseLower quality, new method with decent performance, comparable to Q3 quants.
Ring-mini-2.0-Q2_K_L.ggufQ2_K_L6.16GBfalseUses Q8_0 for embed and output weights. Very low quality but surprisingly usable.
Ring-mini-2.0-Q2_K.ggufQ2_K5.84GBfalseVery low quality but surprisingly usable.
Ring-mini-2.0-IQ2_M.ggufIQ2_M5.28GBfalseRelatively low quality, uses SOTA techniques to be surprisingly usable.
Ring-mini-2.0-IQ2_S.ggufIQ2_S4.70GBfalseLow quality, uses SOTA techniques to be usable.
Ring-mini-2.0-IQ2_XS.ggufIQ2_XS4.66GBfalseLow quality, uses SOTA techniques to be usable.

Embed/output weights

Some of these quants (Q3_K_XL, Q4_K_L 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

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/inclusionAI_Ring-mini-2.0-GGUF --include "inclusionAI_Ring-mini-2.0-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/inclusionAI_Ring-mini-2.0-GGUF --include "inclusionAI_Ring-mini-2.0-Q8_0/*" --local-dir ./

You can either specify a new local-dir (inclusionAI_Ring-mini-2.0-Q8_0) or download them all in place (./)

ARM/AVX information

Previously, you would download Q4_0_4_4/4_8/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 Q4_0_X_X files and will instead need to use Q4_0.

Additionally, if you want to get slightly better quality for , you can use IQ4_NL thanks to this PR which will also repack the weights for ARM, though only the 4_4 for now. The loading time may be slower but it will result in an overall speed incrase.

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

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 Q4_K_M1.79 GiB3.09 BCPU64pp512301.02 ± 1.74147%
qwen2 3B Q4_K_M1.79 GiB3.09 BCPU64pp1024287.23 ± 0.20101%
qwen2 3B Q4_K_M1.79 GiB3.09 BCPU64pp2048262.77 ± 1.81101%
qwen2 3B Q4_K_M1.79 GiB3.09 BCPU64tg12818.80 ± 0.9948%
qwen2 3B Q4_K_M1.79 GiB3.09 BCPU64tg25624.46 ± 3.0483%
qwen2 3B Q4_K_M1.79 GiB3.09 BCPU64tg51236.32 ± 3.5990%
qwen2 3B Q4_0_8_81.69 GiB3.09 BCPU64pp512271.71 ± 3.53133%
qwen2 3B Q4_0_8_81.69 GiB3.09 BCPU64pp1024279.86 ± 45.63100%
qwen2 3B Q4_0_8_81.69 GiB3.09 BCPU64pp2048320.77 ± 5.00124%
qwen2 3B Q4_0_8_81.69 GiB3.09 BCPU64tg12843.51 ± 0.05111%
qwen2 3B Q4_0_8_81.69 GiB3.09 BCPU64tg25643.35 ± 0.09110%
qwen2 3B Q4_0_8_81.69 GiB3.09 BCPU64tg51242.60 ± 0.31105%

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

Which file should I choose?

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 'QX_K_X', like Q5_K_M.

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 IQX_X, like IQ3_M. 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.

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

Как запустить

На своей GPU в ailist. Цена — по текущим предложениям провайдеров

GPU в ailist

llama.cpp

Нельзя запустить

GGUF-модель ждёт проверки: нужно выбрать файл кванта под доступные GPU.

Ревизия весов
2825084

0 моделей