Tested Q6, uses 567Gb Ram

#2
by krustik - opened

Q5-K-M uses 502GB RAM, Q6-K almost 567GB RAM. Tested on CPU, on my ancient 10 years old enterprise Xeon motherboard by Gigabyte with 12 RAM slots, which on used market costs just 100$.
Tested and worked in oobabooga launcher (text generation webui).
LM Studio launcher can't work with such large models still, with any updates, it's hopeless (crashing at loading at 500Gb Ram mark).
My review, unfortunately quantization of this model is not preserving it's strength, it downgraded seriously.
It's very talkative, even too much, that on Q5 quality observed notorius problem of "internal dialogue" with itself (first observed in Falcon 180B quants), non-stop,so R1 need to be precisely tuned in chat parameters (slightly helped frequency penalty 0.05, mirostat 1 kinda works, but i suspect mini_p 0 in deterministic preset is the key).
Q6 quality which is much better in V3 model here not improved it at all.
In test of repairing logical problem in Chuck code both Q5 and Q6 of R1 model failed.
In test or creating Bach melody in Chuck code - Q5 produced many examples but broken code, Q6 also failed (example below).
So, in the end i think V3 model of same size in Q6 is much more better than R1 model in Q6, for now.

R1-Q6-K 567Gb

You

undefined type Midiout at line 2

AI
My apologies for the oversight. The error occurs because the MidiOut class isn't properly capitalized. Here's the corrected version:

// Setup MIDI output
MidiOut mout;
if(!mout.open(0)) me.exit();

// Rest of the code remains the same...
The class name should be MidiOut (capital 'M', lowercase 'idi', capital 'O'). This should resolve the undefined type error. The rest of the code remains valid ChucK syntax for MIDI output.

You
<compiled.code>:2:1: error: undefined type 'MidiOut'...
[2] MidiOut mout;
^
<compiled.code>:2:1: error: ...in declaration
[2] MidiOut mout;
^

AI
My apologies for the confusion earlier. The error occurs because the MidiOut class name should be capitalized differently. Here's the corrected version:

// Setup MIDI output
MidiOut mout;
if(!mout.open(0)) me.exit();

// Rest of the code...
The correct class name is MidiOut (note the capitalization). This should resolve the "undefined type" error. The rest of the MIDI code will then work as intended with any MIDI output device.

You
not working

AI
Let's try a different approach using the ChucK language's built-in MIDI functionality. Here's a corrected and simplified version of the Bach Minuet:

// Set up MIDI output
MidiOut mout;
if(!mout.open(0)) me.exit();

hi ,any plans to test 4_k_m and q2 quants?

hi ,any plans to test 4_k_m and q2 quants?

I will try Unsloth Q2K-XL today, the non-distilled version, mainly to test quality.
But the main problem is that this "reasoning" not working in current LLM launchers like oobabooga, it produces a "diarrhea" of text non-stop. In Deepseek web-ui, they've made this process in 2 portions, first it thinks for specific time and secondly making the decision on the previous process results, there's no such mechanism in current LLM launchers, i'm not sure if they will implement such in updates.

Sign up or log in to comment