Request for MTP version

#2
by hondaru - opened

Hello XReyRobert,

Could you please provide the model card for the model mentioned:
XReyRobert/Qwopus3.6-27B-v2-MTP-GPTQ-Pro-v1?

While 131K might impose some limitations, I believe it could still be useful for shorter context sizes. Thank you for your assistance.

Hi there,
Kind of depressing that I finally get some feedback after 5K+ downloads but only for a model I scraped because it wasn't delivering what I expected :)

Let me see if I can rebuild this for you, as those aren't quantized I can probably do some patching... stay tuned...

Just please confirm your need bellow so that I don't do it for nothing if you lost interest since yesterday !

Dear XReyRobert,
Since there are relatively few contributors creating AWQ and/or GPTQ models, I believe your work is receiving significant attention!
Actually, with another Qwen3.6-27B model, I'm getting around 60 TPS on an RTX 3090 with MTP, which made me wonder if this model might perform similarly well.
Thank you for your hard work.

Published! (untested) Let me know how it goes. (this is a patch so MTP are BF16 but that shouldn't have much of an impact)
https://huggingface.co/XReyRobert/Qwopus3.6-27B-v2-GPTQ-Pro-MTP-BF16

Dear XReyRobert,
After comparing the two models, the NON-MTP model achieved an average throughput of 45 TPS, while the MTP(2) model reached approximately 55 TPS. While the non-MTP model maintained consistent performance around 45, the MTP model produced results between 50-60 TPS. Based on these results, it appears the MTP enhancement does indeed provide measurable benefits.
Also MTP(2) with turboquant dropped to 40TPS with eager mode but 131k cache.

Regarding accuracy, however, the MTP model produced more distorted text. Why might this be?
Could it be an effect of the GPTQ quantization process?

Regardless, I've gained invaluable experience through this experiment, and I'm truly grateful for the opportunity.

Sounds great. On my tests MTP didn't bring anything, please share your configuration details (vllm command line) .

As for your distorded text it might more be an effect of MTP than quantization as I patched this model with an unquantized MTP head...

Here's how I configure the Docker command:

docker run -d --gpus all
--name vllm-server
--ipc=host
-v ~/.cache/huggingface:/root/.cache/huggingface
-e HF_TOKEN="********"
-e VLLM_ATTENTION_BACKEND=TRITON_ATTN
vllm/vllm-openai:latest
XReyRobert/Qwopus3.6-27B-v2-GPTQ-Pro-MTP-BF16
--gpu-memory-utilization 0.97
--max-model-len 42280
--max-num-seqs 1
--reasoning-parser qwen3
--kv-cache-dtype fp8
--max-num-batched-tokens 2048
--enable-chunked-prefill
--enable-prefix-caching
--language-model-only
--no-enable-flashinfer-autotune
--speculative-config '{"method":"mtp","num_speculative_tokens":2}'

:)

Thanks for sharing. 42280 of context is really low for agentic use, that why I came to the conclusion of not using it.
I think I managed to use higher context that 42K but tok/s were on pare with the non MTP anyway so it wasn't worth it.
Again that's on a single 3090 if you have 2 thats' a different story.

Thanks for the message!
You're right - with Agentic use, context size becomes crucial.
However, having MTP enabled lets you easily increase context size in TurboQuant with minimal performance degradation, which is definitely beneficial. Even with higher prediction buffer sizes, throughput shouldn't decrease significantly.
Having a single RTX 3090 is incredibly versatile - I'm really glad I have it!

Sign up or log in to comment