I Blamed the Model for Months. The Bug Was My Sampler.
The author discusses their experience running a local language model on an M1 Max machine. Initially, they blamed the model's architecture for poor output quality, but later discovered that the issue stemmed from a flawed sampler configuration in their code. After making adjustments, the model's performance improved significantly, demonstrating the importance of proper configuration in machine learning applications.
- ▪The author ran a 35B Mixture-of-Experts model that consumed around 40GB of memory.
- ▪They initially assumed the model's architecture was the problem due to poor output quality.
- ▪After diagnosing the issue, they found that a custom repetition penalty processor was causing incoherence in the generated text.
- ▪By changing the model and adjusting the sampler configuration, the output quality improved dramatically.
- ▪The system's free memory increased significantly after switching to a smaller model, enhancing overall performance.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/sleepyquant/i-blamed-the-model-for-months-the-bug-was-my-sampler-3dne |
| Publication time | Fri, 29 May 2026 09:35:03 +0000 |
| Retrieval time | 2026-05-29T09:50:00.154Z |
| Last seen | 2026-05-29T09:50:00.154Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | xbpCSwfsSW4A |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3885340) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } SleepyQuant Posted on May 29 • Originally published at sleepyquant.rest I Blamed the Model for Months. The Bug Was My Sampler. #applesilicon #mlx #localai #m1max I Blamed the Model for Months. The Bug Was My Sampler. 40GB In, Word Salad Out Running local LLMs on M1 Max hardware is one of those setups that looks great on paper — unified memory, no PCIe bottleneck, offline and private.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).