logoalt Hacker News

peri-cltoday at 4:41 PM1 replyview on HN

You find Q3 to be usable quality for your purposes? (I assume Q3 if you're squeezing it into 16 GiB)


Replies

noloktoday at 5:03 PM

Yes, the generic system I built has unsloth/qwen3.8-27b with a 48000 context size running on each employee system with lmstudio, with a simple runner to watch folders and pass it to the llm alongside all context (our company design rules, our legal documents, our contractual rules, our applicable local law and reglementation, ...), return is then mailed to them or added to their personal dashboard event list, depending on their settings.

This is clearly pushing it memory wise and the gpu offloading is only partial but LM studio deal with it automatically and it's being fine even on the 4071 Ti desks (Ryzen 7500F and 32 GB of ram), employees get any feedback in ~20 minutes after they dropped a file (it's much smoother on the 5080 desks obivously), for live it's useless but as background helper it's great and the very large context allows us to fit all the rules we want in there.

One caveat has been to not ask it if everything is ok, but to find what's wrong - but always source and explain it and justify itself, never drown the user in warning in suggestions; goal is to help and provide a second pair of eyes not make them feel annoyed or unsecure.

And I found people to genuinely enjoy something that works for them on their own machine and is not tracked "by the boss", thus the assistant reference, than than a centralized mothership like we also have and they have access to. I also allow them to disable it if they want, I trust them with their work, but a second pair of eyes is always great.

(my previous workhorse for this was Qwen3-14b but it's missing a lot more edge cases)

show 1 reply