my-server
← All posts

Tagged “loch-nessh”

The First Machine We Didn't Own A friend brought a MacBook over for an evening. Eight minutes after enrolling it was serving claims; within a day it had found a bug that had been in our worker since August and was invisible on every machine we owned. T… Fourteen Cases, Three Defects: Letting the Workloads Tune the Scheduler We wrote the expected route for every kind of work the cluster does before sending a single request. The first run was 6 hits, 5 misses, 3 gaps. Every miss was a scheduler defect nobody had noticed for weeks — including … The Media Models Were Never Actually Tested A routine capability audit turned up a model actively crash-looping, a wrong-model bug hiding behind a right-looking filename, a deployment missing two-thirds of its own pipeline, and generation parameters that were bein… Who's Asking? Teaching loch-nessh Real Identity, Then Real Access Control loch-nessh went from zero auth to a real login flow to a full ownership-and-access-control pass in one sitting: three UX tiers, a hosted login redirect, node-name obfuscation, a Gantt-style timeline of what ran where, an… Small Models, One Semaphore: NPU Use-Cases, a Concurrency Rewrite, and Flux.2's Ghost Dependency The NPU bring-up from a few posts back finally got real workloads: a chat router and speech-to-text, live. Getting there meant reverting a concurrency design after review, which surfaced a genuine scheduler bug behind fl… The Cortex Grows Senses: ROCm for LLMs, Multimodal In and Out, and Four New Agents Six weeks since the flux2-dev ROCm debugging saga, the fix turned out to generalize far past image generation. A tour of what shipped: ROCm for LLM serving, the broker's first multimodal-input feature, four new agent rol… Scheduling GPU Workloads at Home: A Capacity Model That Scales A rigorous capacity model for home GPU clusters — one that works on a single node today and extends naturally when new hardware arrives. Built around three state vectors, six diagnostic metrics, and the actual implementa… Getting Wan2.2 to Actually Run: A Fox, a Single Frame, and a 4 GB Wall Every video request was returning a 1-frame WebM. Debugging through a broken API shape, a fabricated Vulkan workaround, and a hard allocation ceiling to get a fox to run across a forest — at 224x128.