no comments (yet)

sorted by: hot top controversial new old
there doesn't seem to be anything here
22 comments in c/localllama@sh.itjust.works view that post
[–] 11 points 2 months ago (1 child)

Cheers for the new local GOAT!

Also on ModelScope in case you-know-who bribes huggingface takedown because model is too dangerous.

  • source
  • hideshow 1 child comment
  • [–] 3 points 2 months ago

    I’m not sure why there’s so much focus on comparing Qwen’s 27B models with older Opus versions. 3.6 was pretty comparable to Sonnet 4.6 for coding, and now 3.8 gets it to around Sonnet 5 level (SWE Bench Pro 61.7 vs. S5’s 63.2). That’s pretty a awesome achievement and I think comparing it to Sonnet sets more realistic expectations.

  • source
  • parent
  • [–] 7 points 2 months ago (8 children)

    Qwen3.6 with 4-bit quant was hallucinating HARD. When asked to summarize the plot of obscure, cheesy 80s books, it confidently made up plot and characters. Not a single statement was correct. It was glorious.

    Any higher quant and it would take 30-90 seconds before first token. Both MLX and GGUF on an M3Max with 128G combined RAM. Will have to try it with this one.

  • source
  • hideshow 8 child comments
  • [–] [S] 7 points 2 months ago

    In my testing so far, it seems to lean more into "I don't know" type answers, but I haven't poked at it that much yet.

    One of the queries that used to consistently trip up Qwen 3.5/3.6 was asking directly about a plausible sounding (but non-existent) work (e.g. Are you familiar with "A Valiant Effort (1989)"?); stock Qwen 3.8 will say it doesn't know or isn't sure and ask me for context.

  • source
  • parent
  • [–] 7 points 2 months ago (5 children)

    27b fits easily into 128 unified RAM, even unquantized. So something was definitely wrong.

    Running 3.8-27b on my Strix Halo box right now.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 2 months ago (3 children)

    Hey, I also have a Strix Halo box. Which model are you running exactly? The Q8 and BF16 are half the size of Qwen3-Coder-Next-UD-Q8 I have been running before. I tested 3.8-BF16 and UD-Q8 but both run at abysmal speed in comparison to Coder Next (around 8 t/s during chat). Which one gives you best results?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 8 points 2 months ago* (2 children)

    You need to use MTP (Multi token prediction) to get acceptable speeds on a Strix Halo. On llama.cpp you just need to add --spec-type draft-mtp --spec-draft-n-max 3 -np 1 to your arguments.

    You should see around 15-20 t/s in coding tasks at Q8, which will still be much slower than Qwen3-Coder-Next-UD-Q8 since it's 27b active parameters instead of 3b.

    As for Q8 vs BF16, it usually makes barely to no difference in quality. Speed is higher on Q8 though. Still testing with 3.8 since it just released.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 months ago

    On a DGX with 128G unified I could push Qwen3.6-27B to 8-bit and it had pretty decent response. It just croaked with MLX on the Mac.

    Waiting to see what Apple announces next month. Judging by RAM prices, it'll be waaay outside my budget.

  • source
  • parent
  • [–] 4 points 2 months ago (1 child)

    Has anyone here really pushed the multimodal stuff with this yet? Been running this on a 4090 for over 24 hours and have been meaning to try out if its able to summarize images well, especially compared to something like qwen3vl on the same hardware

  • source
  • hideshow 1 child comment
  • [–] 3 points 2 months ago (5 children)

    Having issues with it (Unsloth's gguf).

    0.27.136.404 I srv  proxy_reques: proxying request to model unsloth/Qwen3.8-27B-GGUF:Q4_K_M on port 55741
    [55741] 0.14.424.772 W srv    operator(): got exception: {"error":{"code":500,"message":"\n------------\nWhile executing CallExpression at line 106, column 32 in source:\n...first %}↵            {{- raise_exception('System message must be at the beginnin...\n                                           ^\nError: Jinja Exception: System message must be at the beginning.","type":"server_error"}}
    
    
  • source
  • hideshow 5 child comments
  • [–] 7 points 2 months ago* (3 children)

    Got an answer - there were indeed issue with some quants

    Actually edit - UD-Q4_K_XL and all UD-* has our corrected chat teaplate

    We need to update the non UD-* ones with our chat template - stay tuned

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 2 months ago

    Anybody tried it on MLX? I was really skeptical about them releasing 27b, after they skipped it for 3.7 but I'm pleasantly surprised.

  • source
  • [–] 3 points 2 months ago

    Goddamn, number go up in many benches.

  • source
  • [–] 5 points 2 months ago

    So far, I’ve had 3.8 do a code review and also review some creative writing. It’s quite a bit more thorough than 3.6.

  • source