Live data from Hacker News

Qwen 3.7 Preview

twitter.com

61–70 of 100 posts

Re: Qwen 3.7 Preview

#61

Qwen 3.6 35B (finetuned) is so good that it became standard open weights for everyday use. Is not far at all from proprietary models if you give it tools, skills and agents etc, it can actually finish the job. (Thank you Qwen team, appreciated). Using opensource now we can definitely rely to design from scratch very complicated architecture and build pretty fast the full pack. Wish to see Europe AI unleashed, wake up…

Can you share the GGUF for this specific success story? I'd like to try it for myself.

Re: Qwen 3.7 Preview

#62
post #9
post #7

Vision has become totally underappreciated, whereas I believe it brings important advantages to a model Also, a big caveat in using Qwen models has always been its speech patterns. I do wonder how Google made the Gemma lineup so good at this Let's hope Alibaba continues to open source its models

Agreed. Incidentally, in my testing, qwen models (qwen3.6-35b-a3b and earlier 3.5) are WAY better with vision than gemma4-26b-a4b. I would normally want to stick with gemma4 only (I use it for spam filtering), but it just doesn't cut it for vision work, and qwen models do.

> qwen models (qwen3.6-35b-a3b and earlier 3.5) are WAY better with vision than gemma4-26b-a4b

Can you give an example? And/or is there a benchmark specifically for this?

Re: Qwen 3.7 Preview

#63
post #4

I am very interested in seeing new qwen models. Qwen3.6 27b is the first one that can do things and doesnt constantly loose "it's mind" and that can be run on a 3090 with a good context size. But it's sometimes getting into a loop.

I sort of thought this about qwen3.5 35b, finally a local model that isn't a complete waste of electricity, but "upgrading" to 3.6 35b left me disappointed. It seemed more like a downgrade. But honestly I've barely used either. Subjectively they still seem far from the frontier models, but for what they can do, it's great to be able to do locally.

Re: Qwen 3.7 Preview

#64
post #42

So glad they’re holding steady on open weights. At least for now. Worried the Chinese team will change their mind once they have parity

Of course they will.

Right now they want to prevent the US labs from gaining any sort of self-reinforcing oligopoly on the space, and to let the ecosystem in China flourish.

That will all die sooner or later.

Re: Qwen 3.7 Preview

#65

Earlier quoted context omitted.

Similar, but I'm using 35B A3B variation with experimental MTP support OpenCode is pretty good too

A3B is especially nice, MoE really shines on memory bandwidth contained platforms like the DGX Spark.

looks like MTP support has now been merged and also updated unsloth quants to go with it (not just the extras, all of 'em!)

Re: Qwen 3.7 Preview

#66
post #26

I love that open weight models are catching up so quickly. Also hilarious how far behind Grok is. I guess demand for Grok must be poor if Anthropic is able to rent resources from xAI.

Just to be clear, "Plus" and "Max" Qwen models are closed. Seems likely smaller open versions will be released, but that's not what was announced today

Re: Qwen 3.7 Preview

#67
post #59
post #50

Earlier quoted context omitted.

You can get all the Qwen 3.x models up to ~1 million tokens using YaRN with llama.cpp.[0] Personally I am using `--no-context-shift` and feeding in context back in on failure at the harness level. I have 2x1080ti + 1xTitanV that have a full 262,144 tokens context on 262,144 tokens with `-sm tensor` at 62.04 t/s which isn't so bad. But I also have a 1x3090 running unsloth/Qwen3.6-27B-MTP-GGUF:UD-Q4_K_XL at 41.89 t/s b…

How can you get it to run at 41 t/s? I also have a single 3090 and even with MTP can't break 20 t/s. HEre's my setup: llama-server --port 9999 --model /MODELS/LLMs/Qwen3.6-27B-UD-Q4_K_XL.gguf --ctx-size 128000 --threads 12 --flash-attn on --device CUDA0 --jinja --gpu-layers 52 --mmproj /MODELS/LLMs/Qwen3.6-27B-mmproj-F16.gguf --cache-type-k q8_0 --cache-type-v q8_0 --temp 0.6 --top-k 20 --top-p 0.95 --min-p 0.0 --rep…

(Note UPDATED config)

Ya, if you are using the CPU it may slowdown quick.

This may be a bit huge and overcomplicated, on this host I am running it on a AMD Ryzen 7 5700G so that I can use the APU to dedicate the 3090.

    podman run --device nvidia.com/gpu=all -d -v llama_qwen3.6mpt:/root/.cache -p 8080:8080 local/llama.cpp:full-cuda --server \
    -hf unsloth/Qwen3.6-27B-MTP-GGUF:UD-Q4_K_XL \
    -ngl 99 \
    --ctx-size 131072 \
    --no-mmproj-offload \
    --no-context-shift \
    --kv-unified \
    --spec-type draft-mtp \
    --spec-draft-n-max 6 \
    --spec-draft-p-min 0.75 \
    -fa on --jinja --no-mmap \
    --cache-ram -1 \
    --no-warmup -np 1 \
    -n 32768 \
    --cache-type-k q8_0 \
    --cache-type-v q8_0 \
    --temp 0.6 \
    --min-p 0.00 \
    --top-k 20 \
    --top-p 0.95 \
    --presence-penalty 0.0 \
    --repeat-penalty 1.05 \
    --fit off \
    --reasoning on \
    --chat-template-kwargs '{"preserve_thinking":true}' \
    --prio 3 \
    --poll 100 \
    --port 8080 \
    --host 0.0.0.0

I am just building the container with:

     podman build -t local/llama.cpp:full-cuda --target full -f .devops/cuda.Dockerfile .
And here is the logs from a 'make me a flappy bird program in python' webui prompt.

     prompt eval time =     105.86 ms /    19 tokens (    5.57 ms per token,   179.47 tokens per second)
       eval time =  100549.41 ms /  4608 tokens (   21.82 ms per token,    45.83 tokens per second)
      total time =  100655.28 ms /  4627 tokens
     draft acceptance rate = 0.47215 ( 3408 accepted /  7218 generated)
I am down to ~25.54 t/s with a 95% full context.

Re: Qwen 3.7 Preview

#69

Qwen 3.6 35B (finetuned) is so good that it became standard open weights for everyday use. Is not far at all from proprietary models if you give it tools, skills and agents etc, it can actually finish the job. (Thank you Qwen team, appreciated). Using opensource now we can definitely rely to design from scratch very complicated architecture and build pretty fast the full pack. Wish to see Europe AI unleashed, wake up…

> Is not far at all from proprietary models if you give it tools, skills and agents etc, I use Qwen 3.6 27B, the dense version of this model which is slightly better. I don't agree that it's close at all. Maybe for some small, easy tasks, but not for working on real codebases. It's amazing for something I can run at home, but the difference between it and Opus or GPT-5.5 is huge.

> not for working on real codebases

You don't pick just one model to "work on real codebases". You use a very advanced model to plan, and a not-very-advanced, cheaper, faster model to execute planned tasks. This saves money and speeds up work. This is the guidance from Anthropic & OpenAI.

Post reply on HN