This size is not suitable for adding mmproj.

#1
by jian2023 - opened

Bundling it into mmproj is pointless. If you have enough VRAM, why not use a higher-precision quantized version? The greatest value lies in removing MTP and mmproj so that the model can run smoothly on 16GB of VRAM, since the closest matching graphics card specification is 16GB.

A couple of practical points to clarify here:

  1. mmproj is a separate, optional file. In llama.cpp, vision isn't baked into the main GGUF. If you don't pass --mmproj, it uses 0 MB of VRAM. If you have a 16GB card and only care about text/code, just load the main model and you get plenty of room for context. Removing the projector from the repo makes no sense because it would just break vision for anyone who wants it.

  2. Occamy doesn't have MTP. It's a 35B hybrid model with 30 linear attention layers and native vision; Iris and Apodex are the ones with MTP heads.

  3. Why this over Q4 on 24GB VRAM:
    A standard Q4_K_M weighs ~19.5 GB. On a 24GB card (RTX 3090/4090), that leaves barely ~4 GB for KV cache and CUDA buffers. Try running a 64k or 256k context on that and you'll OOM immediately.

The entire purpose of this build is keeping the weights at 13.6 GB without the quality collapse of flat automated 3-bit quants. The router gates (ffn_gate_inp) are kept in uncompressed F32 so the 256 micro-experts don't drift, output.weight is isolated in Q6_K so vocabulary classification doesn't break syntax, and the shared expert uses IQ4_NL. It matches the reasoning and output quality of a much heavier Q4, but leaves enough VRAM headroom to actually run large contexts.

Also, don't confuse APEX-I-MiniPlus-V2 with a generic baseline APEX-I-Mini. Traditional APEX-I-Mini drops core experts aggressively to 2-bit IQ2_S and leaves output.weight at 3-bit Q3_K_M, which creates a noticeable perplexity hit on complex reasoning tasks. V2 was specifically re-engineered to avoid that quality floor (keeping core experts at calibrated IQ3_XXS, output in Q6_K, and routers in F32).

To put the numbers in perspective: this cuts nearly 2 GB off a flat 3-bit quant (15.6 GB), and weighs only about ~1 GB more than a generic APEX-I-Mini (12.5 GB). For that single extra gigabyte of VRAM, you get a massive jump in reasoning and syntactic stability.

Take a look at the tensor-by-tensor comparison table in the model card above if you want to check out the exact architectural differences and why this specific allocation is optimal.

That's specifically what this was built for.

Thank you for your help. It loaded completely and performed well on my 4060ti 16G graphics card, currently only using 64K of context.

Sign up or log in to comment