Comment by Aurornis
9 hours ago
I’ve run 3.6-27B and 3.6-35B on 32GB locally for a lot of bulk non-code tasks. Let it run overnight and wake up to millions of output tokens worth of results without data having left my house, all for the price of electricity.
I haven’t found it very useful for code. It can do some code, but I’ve tried a dozen different quants and context lengths and the output is always bad enough that it has to be discarded for anything other than really easy tasks. It has been useful for exploring codebases for search and summary, though.
DS Flash is where local models begin to feel useful for coding, but the quants we run locally are sharply reduced in intelligence from the benchmarks for the full models.
For applications where data cannot leave the local network it’s good to have them. For actual coding work I can’t actually justify the power of electricity and cooling, let alone the expensive hardware, compared to hosted APIs.
But I admit I do enjoy playing with them anyway. I think it’s one of those hobbies where it’s most fun if you never do the math on how much you’re paying for the privilege. If someone has a requirement that data stay local then it’s different, of course.
> I’ve run 3.6-27B and 3.6-35B on 32GB locally for a lot of bulk non-code tasks.
Do you mind sharing your use cases?
Not OP, but I use it for a ton of smaller things. I have it hooked into Hermes and have been using it to help bulk rename my media folders so they all follow a common format, add titles that sort of thing which wouldn't be easy to 'script'. Another thing I use it for is comparing data sets, looking at my exported Spotify artists and compare to what I have locally, and letting me know where there are missing artists, or albums, and recommendations based on similar artists that I may not have locally.
Sure a lot of this could be done without AI, but it's certainly quicker and easier, and since my AI box is on solar, it's just the power of the sun to keep it going.
Not OP, but driving knowledge bases is the poster child use case for me https://github.com/aka-rider/llm-wiki
I started with Karpathy's LLM wiki, and did everything he said not to do - downgraded the model to mere tool usage and summarization, and it works great.
I am a data hoarder, and finally I can just dump all the content I remotely like, and get something interesting to browse for the price of electricity.
Agentic long-running tasks, as others have mentioned:
- Groom and triage tickets for agentic SWE workflows
- bug hunt — the probability of Qwen fixing a complex bug is 50/50 but often it is capable of identifying the root cause or at least laying the ground work for a more capable model to pick it up.
Love the workflow. Is there an existing way to do this inside Obsidian -- where I have all my knowledge?
1 reply →
Not OP, but I use it for personal tasks that are just not worth the claude tokens -- rooting through historical medical records to unify prescription history, super-OCR'ing thousands of PDF pages (i.e. beyond PDF dumping -- vision means it can look at tables, understand tricky things like a continuation of a block quote or aside on the next page, etc.), and when power is cheap I'll just let it noodle on little projects on my data. During my agent's "free time" I give it with a tremendously open ended prompt last week, it did a linguistic analysis of how my texting changes in the lead up to, initiation, maintenance, and ending of romantic relationships.