<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AGmind Systems Lab — reports</title>
    <link>https://agmind.ru/</link>
    <description>Qualification research on local AI systems: evidence, limitations and negative results.</description>
    <language>en-US</language>
    <atom:link href="https://agmind.ru/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>We rewrote our benchmark to sound like a human</title>
      <link>https://agmind.ru/essays/benchmark-that-sounds-like-a-human/</link>
      <guid isPermaLink="true">https://agmind.ru/essays/benchmark-that-sounds-like-a-human/</guid>
      <description>Our first chat corpus asked the model about build digests and goodput. Nobody's users ask that. The same cell re-measured on sixteen everyday prompts gave a different failure rate on identical hardware, and we kept the old number anyway.</description>
      <pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A website where CI fails when a number drifts from its evidence</title>
      <link>https://agmind.ru/essays/ci-fails-when-a-number-drifts/</link>
      <guid isPermaLink="true">https://agmind.ru/essays/ci-fails-when-a-number-drifts/</guid>
      <description>Type a tokens-per-second figure into this site and CI fails. Every measured value is re-derived from raw run records, and a committed value that drifts from them stops the pipeline. How the gate works, what it enforces, and the class of error it cannot see.</description>
      <pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Independent proof or it didn't happen: DeepSeek just made its scoreboard fillable</title>
      <link>https://agmind.ru/essays/independent-proof-or-it-didnt-happen/</link>
      <guid isPermaLink="true">https://agmind.ru/essays/independent-proof-or-it-didnt-happen/</guid>
      <description>DeepSeek opened its agent harness and named the mode, effort and sampling behind V4-Pro's agent scores. Better disclosure than the norm, and still not proof: a vendor's number stays vendor-disclosed until a second party runs the same config and publishes the traces.</description>
      <pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Agentic coding is a prefill problem, and everyone is shopping for decode</title>
      <link>https://agmind.ru/essays/agentic-coding-prefill-problem/</link>
      <guid isPermaLink="true">https://agmind.ru/essays/agentic-coding-prefill-problem/</guid>
      <description>Ask how many tokens per second a local coding agent needs and every answer quotes decode speed. But an agent's turn is a huge prompt and a short reply — the wait lives in prefill, and the hardware conversation is optimizing the wrong half of the request.</description>
      <pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Agents-per-box: the capacity metric nobody prints on the box</title>
      <link>https://agmind.ru/essays/agents-per-box/</link>
      <guid isPermaLink="true">https://agmind.ru/essays/agents-per-box/</guid>
      <description>The agent-swarm conversation runs on single-stream decode numbers, which is the one metric that stops mattering the moment you run a swarm. What we learned sizing shared boxes, and the question buyers should be asking vendors instead.</description>
      <pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Everything our harness refuses to measure: a changelog of distrust</title>
      <link>https://agmind.ru/essays/harness-changelog-of-distrust/</link>
      <guid isPermaLink="true">https://agmind.ru/essays/harness-changelog-of-distrust/</guid>
      <description>A benchmark harness earns trust by what it declines to measure. Every version of ours is a scar with a commit message: the invalid first run we kept, the neighbor check, the fallback detector, the word that matched inside another word.</description>
      <pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Beelink GTR9 Pro for local LLMs: what two units measured over a month of serving</title>
      <link>https://agmind.ru/reports/beelink-gtr9-pro-local-llm/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/beelink-gtr9-pro-local-llm/</guid>
      <description>Reviews of this box benchmark it for a week. We bought two, froze the workloads, and have been serving from them since: the software stack that works, what the numbers look like, how the two units compare, and the parts we still cannot vouch for.</description>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>vLLM at 256K context on DGX Spark: the configuration hunt, and the NVFP4 path that was broken in mainline</title>
      <link>https://agmind.ru/reports/dgx-spark-256k-vllm/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/dgx-spark-256k-vllm/</guid>
      <description>The 256K-context configuration hunt on a single GB10: which vLLM attention and MoE backends survived SM_121, why NVFP4 decoded slower than FP8 in the mainline build we pinned, the patched setup that held 260K — and the measured numbers, dated to the versions named inside.</description>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>Local LLM homelab hardware, measured: what to buy for what workload</title>
      <link>https://agmind.ru/reports/local-llm-homelab-hardware/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/local-llm-homelab-hardware/</guid>
      <description>Every hardware guide for local AI is a spec sheet, a vendor reviewing itself, or an affiliate listicle recycling VRAM tiers. This one starts from the workload, uses only numbers we measured on hardware we own, and marks unmeasured lanes as gaps.</description>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>A Russian retrieval embedder in 24M parameters — and the one number that nearly ruined it</title>
      <link>https://agmind.ru/reports/russian-embedder-24m-params/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/russian-embedder-24m-params/</guid>
      <description>The story behind strizh-ru-retriever: layer-pruning RuModernBERT-small into a four-layer encoder, the distillation shortcut that produced a beautiful loss and dead retrieval, what the compression kept — and the leftover config value that silently truncated every input.</description>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>A Russian RAG splitter that cuts documents by indices, not by rewriting the text</title>
      <link>https://agmind.ru/reports/russian-rag-splitter/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/russian-rag-splitter/</guid>
      <description>The story behind agmind-rag-splitter-ru: why a chunker that rewrites text is dangerous for RAG, how a LoRA fine-tune learned to return boundary indices as JSON, the training corpus published alongside it — and the honest gap between teacher agreement and retrieval quality.</description>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>Strix Halo memory allocation: why ROCm sees a fraction of your 128 GB, and what to set instead</title>
      <link>https://agmind.ru/reports/strix-halo-memory-allocation/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/strix-halo-memory-allocation/</guid>
      <description>The classic first failure on a Ryzen AI Max+ 395 box: the model does not fit, or the runtime reports a few gigabytes of VRAM on a 128 GB machine. The BIOS split is usually the wrong lever. Here is what our serving node actually reports, and the setting that matters.</description>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>One box dirty, one box clean: the two-node home AI lab that keeps its numbers honest</title>
      <link>https://agmind.ru/reports/two-node-home-ai-lab/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/two-node-home-ai-lab/</guid>
      <description>Our two identical Strix Halo units live opposite lives: one carries the whole containerized service stack, the other serves a single model and stays otherwise empty. The split is not tidiness — the benchmark harness invalidates any run that finds a GPU neighbor on the host.</description>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>llama.cpp, vLLM or Ollama: which inference engine for a home server?</title>
      <link>https://agmind.ru/reports/which-inference-engine-local-llm/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/which-inference-engine-local-llm/</guid>
      <description>The advice circulating is written from datacenter GPU benchmarks and rarely survives contact with a single box. What each engine is actually for, which one we run where and why, and the defaults question that matters more than the choice itself.</description>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>Do local LLMs invent answers when the document doesn't contain them? We measured it</title>
      <link>https://agmind.ru/reports/do-local-llms-invent-answers/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/do-local-llms-invent-answers/</guid>
      <description>Everyone asks whether a local model hallucinates over their documents; almost nobody measures it. Our workload has an unanswerable control built in: questions the document cannot answer, graded on whether the model admits it. Two model families, two ways to not know.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>How many tokens per second is enough for a local LLM?</title>
      <link>https://agmind.ru/reports/how-many-tokens-per-second-is-enough/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/how-many-tokens-per-second-is-enough/</guid>
      <description>The most asked and least measured question in local AI, usually answered with invented round numbers. What speed actually feels like on a real box: the wait before the first useful word, the flow after it, and the failure that makes tokens per second irrelevant.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>How to benchmark a local LLM so the numbers survive scrutiny</title>
      <link>https://agmind.ru/reports/how-to-benchmark-local-llm/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/how-to-benchmark-local-llm/</guid>
      <description>Most published local-LLM speeds cannot even be disagreed with: they carry no configuration. A practical protocol from a lab that publishes raw runs — what to pin, what to ask the running server, which tokens to count, and why failures belong in the denominator.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>Can a local LLM reliably return strict JSON? Measured across quants, backends and models</title>
      <link>https://agmind.ru/reports/local-llm-json-reliability/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/local-llm-json-reliability/</guid>
      <description>Strict-JSON output is the load-bearing wall of local automation, and its reliability is usually asserted, not measured. On one box: quantization did not move it, the backend did not move it, reasoning mode did not move it — switching the model family did.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>Should you turn thinking off? What reasoning mode costs on a local LLM, measured</title>
      <link>https://agmind.ru/reports/should-you-disable-thinking-local-llm/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/should-you-disable-thinking-local-llm/</guid>
      <description>Reasoning mode on a local model delays the first visible word from a blink to a wait and multiplies the cost of automation — and on every task with a hard right answer in our gates it bought nothing. The measured trade, and where it does not apply.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>Strix Halo or DGX Spark for local AI? What we measured on both boxes</title>
      <link>https://agmind.ru/reports/strix-halo-vs-dgx-spark/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/strix-halo-vs-dgx-spark/</guid>
      <description>The most searched comparison in the local-AI mini-box class is answered everywhere by spec sheets and nowhere by one lab measuring both. We own both platforms. Here is what each one demonstrably did, which workload belongs on which box, and the comparison we refuse to fake.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>What 128 GB of unified memory actually runs: local LLMs, measured</title>
      <link>https://agmind.ru/reports/what-128gb-unified-memory-runs/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/what-128gb-unified-memory-runs/</guid>
      <description>The 128 GB unified-memory class is the current sweet spot for local LLM boxes, and almost everything written about it is spec-sheet arithmetic. Here is what one such box measurably does: which model class it serves, how fast, for how many people, and where 128 GB ends.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>Every benchmark number is a config in disguise</title>
      <link>https://agmind.ru/essays/benchmark-number-config-in-disguise/</link>
      <guid isPermaLink="true">https://agmind.ru/essays/benchmark-number-config-in-disguise/</guid>
      <description>Two honest people measure the same model on the same hardware and disagree hard. Nobody lied: a published speed is a compressed configuration, and the compression is lossy. What a number must carry to be worth quoting, and how to read one that carries nothing.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The dashboard lied twice in one day, in opposite directions</title>
      <link>https://agmind.ru/essays/dashboard-lies-both-directions/</link>
      <guid isPermaLink="true">https://agmind.ru/essays/dashboard-lies-both-directions/</guid>
      <description>One box, one afternoon: a model returning empty answers under HTTP 200, and two healthy containers marked unhealthy by a probe aimed at the wrong port. Green-but-broken and red-but-fine are the same disease, and the cure is the same too.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>DeepSeek-V4-Flash 0731 on two DGX Sparks: the recipe, with its traps marked</title>
      <link>https://agmind.ru/reports/deepseek-v4-flash-0731-dgx-spark-recipe/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/deepseek-v4-flash-0731-dgx-spark-recipe/</guid>
      <description>The exact serving recipe behind our published GB10 numbers: weights and image pinned, the head-first launch order that avoids a TCPStore hang, the MoE backend flag auto-selection skips, what to monitor when NVML goes silent — and the numbers to expect.</description>
      <pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>GPU monitoring on DGX Spark: when dcgm-exporter is dead and NVML answers N/A</title>
      <link>https://agmind.ru/reports/dgx-spark-gpu-monitoring/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/dgx-spark-gpu-monitoring/</guid>
      <description>The standard GPU observability stack half-works on GB10 unified memory: dcgm-exporter does not run and NVML returns N/A on a large share of queries, so Grafana stays green and empty. The collector we actually serve vLLM with, and how to build it.</description>
      <pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>Is the DGX Spark worth it for local LLM work? A measured answer</title>
      <link>https://agmind.ru/reports/dgx-spark-worth-it/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/dgx-spark-worth-it/</guid>
      <description>The highest-volume buyer question in this niche is answered almost entirely by spec-sheet arithmetic. Here is what a pair of GB10 nodes actually did in our lab — serving a 284B MoE, walking a context curve to a million tokens — and who should and should not buy one.</description>
      <pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>Why chatting with a document is slow once, then instant: the llama.cpp prompt cache, measured</title>
      <link>https://agmind.ru/reports/llamacpp-prompt-cache-strix-halo/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/llamacpp-prompt-cache-strix-halo/</guid>
      <description>A document Q&amp;A session on a Ryzen AI Max+ 395 box: what the first question over a 32k-token file costs, what the second one costs with the prompt cache on and off, and the one condition the cache needs before it saves you anything.</description>
      <pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>Q8_0 or Q4_K_M? What the bigger quant actually buys you, measured on one box</title>
      <link>https://agmind.ru/reports/q8-0-vs-q4-k-m-strix-halo/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/q8-0-vs-q4-k-m-strix-halo/</guid>
      <description>Same model, same llama.cpp build, same Strix Halo box, only the quantization changed: what Q8_0 costs in decode pace against Q4_K_M, what our quality gates saw, and which shortage should actually drive the choice.</description>
      <pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>Three hours under load: does a Strix Halo mini PC slow down over a workday?</title>
      <link>https://agmind.ru/reports/strix-halo-sustained-load-3-hours/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/strix-halo-sustained-load-3-hours/</guid>
      <description>A continuous three-hour serving pass on two identical Ryzen AI Max+ 395 units at concurrency four: how far the decode pace drifted between the first five minutes and the last, and what share of requests came back complete.</description>
      <pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>HTTP 200, empty answer: the failure mode your monitoring cannot see</title>
      <link>https://agmind.ru/reports/answerless-http-200/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/answerless-http-200/</guid>
      <description>A reasoning model can consume its entire token budget thinking and return a successful response with zero user-visible text. We measured how often that happens on two model families — and why TTFT dashboards look perfect while it does.</description>
      <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>The Cyrillic tax: what Russian text actually costs in tokens, measured</title>
      <link>https://agmind.ru/reports/cyrillic-token-cost/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/cyrillic-token-cost/</guid>
      <description>Our long-context corpus was cut by a chars-per-token estimate that held for English and missed Russian by a third. The per-item measured counts are published — here is what they say about planning context windows for Cyrillic, and how we caught our own mislabel.</description>
      <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>I use AI every day. And I think the Luddites were right</title>
      <link>https://agmind.ru/essays/luddites-were-right/</link>
      <guid isPermaLink="true">https://agmind.ru/essays/luddites-were-right/</guid>
      <description>A year of journal entries: every time AI lied to me and every time it genuinely came through. The verification protocol that grew out of it, and why the real Luddite story is about quality and the price of the transition, not fear of machines.</description>
      <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why published DeepSeek-on-DGX-Spark speeds disagree with each other</title>
      <link>https://agmind.ru/reports/dspark-speed-numbers-disagree/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/dspark-speed-numbers-disagree/</guid>
      <description>The same model on the same two GB10 nodes is reported anywhere from the high fifties to the low seventies of tokens per second. Every one of those figures can be correct — here is the configuration behind each, and which number to quote for which question.</description>
      <pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>How many people can actually share one 128 GB local AI box?</title>
      <link>https://agmind.ru/reports/concurrency-capacity-strix-halo/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/concurrency-capacity-strix-halo/</guid>
      <description>A measured concurrency ladder on one Strix Halo unit: what the wait looks like at one, four and eight simultaneous chats, what stayed correct, and why 'tokens per second' cannot answer the sizing question at all.</description>
      <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>DSpark speculative decoding on two DGX Spark: the 1M-token depth curve</title>
      <link>https://agmind.ru/reports/dspark-speculative-1m-dgx-spark/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/dspark-speculative-1m-dgx-spark/</guid>
      <description>Our fp8 DSpark bring-up on GB10, an independent reproduction of the community NVFP4 build, and the depth data nobody had published: the single-stream curve to a real million-token prompt — plus two negative results, stated as such.</description>
      <pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>vLLM auto picked the wrong MoE kernel for DeepSeek-V4-Flash on GB10</title>
      <link>https://agmind.ru/reports/dsv4-flash-moe-backend-dgx-spark/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/dsv4-flash-moe-backend-dgx-spark/</guid>
      <description>Serving DeepSeek-V4-Flash-0731 across two DGX Spark nodes: the image ships a MoE kernel built for this model's MXFP4 experts on this silicon — and auto-selection skips it. Picking it by hand is worth double-digit percent of decode. Recipe and raw outputs are public.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>Second model, second quant, second backend: what transfers on one box</title>
      <link>https://agmind.ru/reports/model-quant-backend-strix-halo/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/model-quant-backend-strix-halo/</guid>
      <description>Same Strix Halo unit, three swaps measured one at a time: a second model family reproduces the empty-answer failure mode; Q8_0 buys nothing measurable on these workloads; ROCm works on gfx1151 but decodes slower than Vulkan.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>Strix Halo × llama.cpp Vulkan × Qwen3.6-35B-A3B — document session cache</title>
      <link>https://agmind.ru/tested-configurations/strix-halo-qwen36-llamacpp-vulkan-docsession/</link>
      <guid isPermaLink="true">https://agmind.ru/tested-configurations/strix-halo-qwen36-llamacpp-vulkan-docsession/</guid>
      <description>The second question over the same pasted document: with the server prompt cache off it pays the full half-minute prefill again; with the cache on it answers in under a second. One setting turns a document workflow from unusable into fluid.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>Strix Halo × llama.cpp Vulkan × Qwen3.6-35B-A3B — three hours under sustained load</title>
      <link>https://agmind.ru/tested-configurations/strix-halo-qwen36-llamacpp-vulkan-endurance/</link>
      <guid isPermaLink="true">https://agmind.ru/tested-configurations/strix-halo-qwen36-llamacpp-vulkan-endurance/</guid>
      <description>A continuous 3-hour closed-loop pass at concurrency 4 on both units: all requests answered, decode pace held between the first and the last five minutes, no thermal collapse — with the two units running at visibly different die temperatures.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_single_run</category>
    </item>
    <item>
      <title>Strix Halo × llama.cpp Vulkan × Qwen3.6-35B-A3B — everyday assistant</title>
      <link>https://agmind.ru/tested-configurations/strix-halo-qwen36-llamacpp-vulkan-interactive/</link>
      <guid isPermaLink="true">https://agmind.ru/tested-configurations/strix-halo-qwen36-llamacpp-vulkan-interactive/</guid>
      <description>Single-user everyday chat on a Beelink GTR9 Pro: instant answers with reasoning disabled, a broken configuration at the default reasoning budget, and a verbosity limit that never fully clears.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>Strix Halo × llama.cpp Vulkan × Qwen3.6-35B-A3B — pasted-document retrieval</title>
      <link>https://agmind.ru/tested-configurations/strix-halo-qwen36-llamacpp-vulkan-longcontext/</link>
      <guid isPermaLink="true">https://agmind.ru/tested-configurations/strix-halo-qwen36-llamacpp-vulkan-longcontext/</guid>
      <description>Needle retrieval across a context ladder up to 30k measured tokens with unanswerable controls: retrieval and honesty both held everywhere measured — while time to the first token grew linearly into tens of seconds.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>Strix Halo × llama.cpp Vulkan × Qwen3.6-35B-A3B — strict JSON automation</title>
      <link>https://agmind.ru/tested-configurations/strix-halo-qwen36-llamacpp-vulkan-structured/</link>
      <guid isPermaLink="true">https://agmind.ru/tested-configurations/strix-halo-qwen36-llamacpp-vulkan-structured/</guid>
      <description>Deterministic extraction, classification and structured generation in strict JSON: a perfect task-success rate in both reasoning modes on this corpus — with a seventeenfold end-to-end time difference between them.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>Time-to-first-token does not describe a thinking model</title>
      <link>https://agmind.ru/reports/ttft-thinking-model-strix-halo/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/ttft-thinking-model-strix-halo/</guid>
      <description>On a Strix Halo box the conventional TTFT figure looked excellent while most requests returned an empty answer with HTTP 200. Client-side measurement, three operating settings, evidence bundles included.</description>
      <pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate>
      <category>lab_repeated</category>
    </item>
    <item>
      <title>DeepSeek-V4-Flash DSpark on 2× DGX Spark: 1M context — legacy results</title>
      <link>https://agmind.ru/reports/dspark-dgx-spark-1m-legacy/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/dspark-dgx-spark-1m-legacy/</guid>
      <description>Bring-up of DSpark speculative decoding on GB10 (sm_121) over 200G RoCE, the 1M-token depth curve nobody had published, an independent reproduction of a community build, and two honest negative results.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
      <category>legacy</category>
    </item>
    <item>
      <title>Multi-slot LLM inference on Strix Halo — legacy results</title>
      <link>https://agmind.ru/reports/strix-halo-multislot-legacy/</link>
      <guid isPermaLink="true">https://agmind.ru/reports/strix-halo-multislot-legacy/</guid>
      <description>What one 128 GB Strix Halo mini-PC did under 32 concurrent chat streams: recipes, an 8→10 concurrency cliff in every tested configuration, and where speculative decoding stops helping. Pre-methodology evidence.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
      <category>legacy</category>
    </item>
  </channel>
</rss>
