cd /news/large-language-models/more-ram-changed-what-matters-in-my-… · home › topics › large-language-models › article
[ARTICLE · art-140097] src=dev.to ↗ pub= topic=large-language-models verified=true sentiment=· neutral

More RAM Changed What Matters in My Local AI Setup

A developer documented six months of running local LLMs for coding-agent work, reporting that upgrading from 16 GB to 48 GB of unified memory on a Mac shifted the main constraint from whether a model fits to how long a session can run before the workflow breaks down. The stack pairs LM Studio with Qwen3.8 and Splash models driven by the OpenCode agentic coding workflow, where context length, compaction timing and thinking-mode latency now dominate the trade-offs.

by read2 min views2 publishedSep 26, 2026

Six months ago, I started running local LLMs seriously on a Mac with 16 GB of unified memory. Most of my decisions were dictated by memory: which models fit, which quantization to use, and how much context I could afford.

Moving to 48 GB changed that.

Models such as Qwen3.8-27B became practical for everyday use, and my attention shifted toward a different problem: how well does the model work during a real coding-agent session?

My current setup uses LM Studio with Qwen3.8 and Splash, while OpenCode provides the agentic coding workflow.

With enough memory to run larger models comfortably, other constraints became much more visible.

Context length has a direct cost. Longer sessions accumulate tool output and code. Compaction can interrupt the flow earlier than expected. Thinking improves some tasks while adding latency to others.

A model that looks impressive in a short prompt can therefore feel quite different when it has to navigate a repository, inspect several files, use tools, make changes, and preserve enough context to continue reasoning about them.

That changed how I evaluate local models.

I care less about whether a model technically fits on my machine. I care more about how long I can work with it before the workflow starts getting in the way.

After quite a bit of experimentation, the stack has become relatively small:

Mac with 48 GB unified memory → LM Studio → Qwen3.8 / Splash → OpenCode

The interesting optimization work now happens around that stack: choosing a sensible context size, deciding when thinking is worth enabling, understanding why compaction happens, and balancing model capability against interactive speed.

There is still plenty to experiment with, but having more memory has made the trade-offs much clearer.

I documented my current configuration, what changed since the original 16 GB setup, and the lessons from using it for actual development work in the full article:

[https://ammar-najjar.com/blog/local-ai-setup-six-months-later/](https://ammar-najjar.com/blog/local-ai-setup-six-months-later/)

If you use local LLMs with coding agents, I would be interested in comparing experiences. Once model size and memory stopped being your main constraint, what became the next bottleneck?
── more in #large-language-models 4 stories · sorted by recency
── more on @lm studio 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/more-ram-changed-wha…] indexed:0 read:2min 2026-09-26 · —