12gb vram

#4
by revster1337 - opened

Did anyone tried this with 12gb vram

Tested this on my Mechrevo Jiaolong (Ryzen 9-9955HX, RTX 5070 Ti 12GB VRAM, 32GB RAM). Running the Q8_0 version via Ollama, and it works surprisingly well! While the model is larger than 12GB, the split between VRAM and system RAM is handled smoothly. Speeds are decent for daily coding and complex logic tasks. Definitely usable on 12GB VRAM if you have enough system memory.

Tested this on my Mechrevo Jiaolong (Ryzen 9-9955HX, RTX 5070 Ti 12GB VRAM, 32GB RAM). Running the Q8_0 version via Ollama, and it works surprisingly well! While the model is larger than 12GB, the split between VRAM and system RAM is handled smoothly. Speeds are decent for daily coding and complex logic tasks. Definitely usable on 12GB VRAM if you have enough system memory.

How many tokens/s ?

Yes, RTX 3080 12GB + RAM 32GB DDR4 + i7-12700F, LM Studio.
It writes code with compilation errors, doesn't fix it completely, and then just breaks in the middle of the code. The context is not over yet (32K tokens), Context Overflow = Rolling Windows, Temp = 0.1, Top K = 20, Top P = Off, 10 CPU threads. I don't know how to get it to finish fixing the code (do you know?) 🤷‍♂️
Speed is about 10-20 t/sec depending on quantification (Q4-Q6) and duration of communication.
P.S. Perhaps I'm giving not so trivial request (write a class to generate TOTP codes without external dependencies), but Claude handles it easily.

Request (Russian) Напиши класс на C++ для создания TOTP-кодов по ключу, time_point любого типа или по текущему времени (т.е. 2 перегрузки, и чтобы при этом было корректное преобразование времени в Unix time) и по длине кода (по умолчанию 6 цифр). Без внешних зависимостей и POSIX. Сделай пример, который выводит кол-во оставшегося времени и 2 TOTP-кода: для текущего времени utc_clock и system_clock. Стиль именования типов, функций и переменных используй привычный для C++, не camelCase. Перепроверь код на ошибки и сразу исправь, если они есть.

This model performed the task almost at the level of large cloud models with hundreds of billions of parameters.: https://huggingface.co/Qwen/Qwen3.6-35B-A3B (Q6_K).
With disabled thinking!

This model performed the task almost at the level of large cloud models with hundreds of billions of parameters.: https://huggingface.co/Qwen/Qwen3.6-35B-A3B (Q6_K).
With disabled thinking!

What iq rig and config you used

What iq rig and config you used

LM Studio
64K tokens, 10 CPU threads, Thinking Off, everything else is by default.
Temp = 0.2, Context Overflow = Rolling Window, Top P = 0.95, Min P = 0.05, Repeat Penalty = 1.05 (but all this is not particularly important AFAIK, except for the temperature).
Speed = 15.6 t/s (1st answer), 12.03 (2nd), 10.13 (3rd, final).

4070ti 12gb, 64gb ddr4, i7-13700f (16 cores).
45 t/s, 100k context
Q4 quant
--temp 0.6 --top-k 20 --top-p 0.95 --repeat-penalty 1.0 --presence-penalty 0.0 --min-p 0.0 --host 127.0.0.1 --port 8000 --threads 12 --threads-batch 16 --parallel 1 --fit on --fit-ctx 92160 --fit-target 512 -n 8192 -b 2048 -ub 512 --mlock --jinja --chat-template-file ./chat_template.jinja --chat-template-kwargs '{"preserve_thinking": true}' --flash-attn on -ctk q8_0 -ctv q8_0

4070ti 12gb, 64gb ddr4, i7-13700f (16 cores).
45 t/s, 100k context
Q4 quant
--temp 0.6 --top-k 20 --top-p 0.95 --repeat-penalty 1.0 --presence-penalty 0.0 --min-p 0.0 --host 127.0.0.1 --port 8000 --threads 12 --threads-batch 16 --parallel 1 --fit on --fit-ctx 92160 --fit-target 512 -n 8192 -b 2048 -ub 512 --mlock --jinja --chat-template-file ./chat_template.jinja --chat-template-kwargs '{"preserve_thinking": true}' --flash-attn on -ctk q8_0 -ctv q8_0

Did you tried to compare with 27B model ?

Did you tried to compare with 27B model ?

Today I added a system prompt for 35B A3B and tried again. It generated a fully working code on the first try! Even Claude Haiku 4.5 succeeded only on the second attempt, leap seconds were not taken into account in the first iteration (the main problem of this task). The speed is 13.1 t/s.

27B (even Q4) is significantly slower because it's not A3B — 3.57 t/s. And the code doesn't even compile (the system prompt was the same).

So i should go for the A3B with 12 VRAM

Did you tried to compare with 27B model ?

No. But I think I’ll get something around 15 T/s. I really like 35b-a3b - the speed is excellent. And when connected to the web (search, fetch, ground), the model performs just as well as Sonnet or GPT 5.2. It’s also very important to use “thinking” mode on these models, because without it they’re pretty dumb. In my llama.cpp config, I consider the most important settings to be --fit-on --fit-ctx 92160 --fit-target 512 and -ctk q8_0 -ctv q8_0. Fit-on distributes available resources very well, there’s no need to fiddle with the config to match your specific hardware. With fit-on, it’s important to use fit-ctx for the context, not just --ctx-size. And --fit-target specifies how much VRAM to leave free.

Did you tried to compare with 27B model ?

No. But I think I’ll get something around 15 T/s.

27b dense with most of your weights on 64gb ddr4 will give about 3 t/s initially dropping down to 1.5 at high context -- not 15.

At least that's my guess. Give it a spin and let us know :)

Sign up or log in to comment