<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Retrivium — field notes and retrospectives</title><description>Retrivium develops GPU infrastructure for LLM inference across Europe, CIS and Asia. Our GPU pool is being integrated with OpenRouter as an inference provider.</description><link>https://retrivium.ai/</link><language>en</language><item><title>Qwen3-30B-A3B Instruct vs Thinking: choose by task</title><link>https://retrivium.ai/journal/qwen3-30b-instruct-vs-thinking-tasks/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen3-30b-instruct-vs-thinking-tasks/</guid><description>Compare the Qwen3-30B-A3B 2507 Instruct and Thinking checkpoints using task acceptance, answer limits and a reproducible evaluation record.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3-4B-Thinking-2507 for math: verify answers and failure cases</title><link>https://retrivium.ai/journal/qwen3-4b-thinking-math-verification/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen3-4b-thinking-math-verification/</guid><description>Evaluate Qwen3-4B-Thinking-2507 on math with checked final answers, valid alternative solutions, output limits and a reproducible failure record.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3-4B-Instruct-2507 for text classification</title><link>https://retrivium.ai/journal/qwen3-4b-instruct-text-classification/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen3-4b-instruct-text-classification/</guid><description>Test Qwen3-4B-Instruct-2507 for fixed-label classification using an explicit taxonomy, abstention cases, confusion records and stable output checks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3-Coder-Next vs 30B-A3B for repository work</title><link>https://retrivium.ai/journal/qwen3-coder-next-vs-30b-repository-tasks/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen3-coder-next-vs-30b-repository-tasks/</guid><description>Compare Qwen3-Coder-Next and 30B-A3B on repository issue localization, cross-file edits, acceptance tests and declared evaluation budgets.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3-Coder 480B vs 30B: when to escalate a coding task</title><link>https://retrivium.ai/journal/qwen3-coder-480b-vs-30b-task-escalation/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen3-coder-480b-vs-30b-task-escalation/</guid><description>Choose when to escalate from Qwen3-Coder 30B to 480B using a documented failure, a fresh attempt budget and unchanged patch acceptance checks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3-Coder-Next after a failed test: evaluate recovery</title><link>https://retrivium.ai/journal/qwen3-coder-next-failed-test-recovery/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen3-coder-next-failed-test-recovery/</guid><description>Evaluate Qwen3-Coder-Next after a failed test with a preserved transcript, protected acceptance checks and separate repair and regression evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen2.5-Coder FIM vs chat: choose the right checkpoint and prompt</title><link>https://retrivium.ai/journal/qwen25-coder-fim-vs-chat-completion/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen25-coder-fim-vs-chat-completion/</guid><description>Choose Qwen2.5-Coder Base for fill-in-the-middle or Instruct for chat coding, then verify suffix preservation and the generated insertion.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3-Next vs Qwen3-32B for long text instructions</title><link>https://retrivium.ai/journal/qwen3-next-vs-32b-long-text-instructions/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen3-next-vs-32b-long-text-instructions/</guid><description>Compare Qwen3-Next and Qwen3-32B on distant text constraints while separating native context, length extension and actual instruction accuracy.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3-Next Gated DeltaNet: what changes for text inference</title><link>https://retrivium.ai/journal/qwen3-next-gated-deltanet-explained/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen3-next-gated-deltanet-explained/</guid><description>Understand Qwen3-Next Gated DeltaNet, gated attention and sparse experts, then test distant requirements without inferring universal accuracy or speed.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3-Next Thinking vs Instruct: separate checkpoints and answer budgets</title><link>https://retrivium.ai/journal/qwen3-next-thinking-vs-instruct-checkpoints/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen3-next-thinking-vs-instruct-checkpoints/</guid><description>Choose Qwen3-Next Thinking or Instruct by task, checkpoint identity, completed final answers and explicit reasoning and response budgets.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.6 preserve_thinking for iterative code changes</title><link>https://retrivium.ai/journal/qwen36-preserve-thinking-code-iterations/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen36-preserve-thinking-code-iterations/</guid><description>Evaluate Qwen3.6 preserve_thinking on iterative code edits with intact historical messages, a fixed transcript and explicit final-answer checks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.6-27B vs 35B-A3B for text coding tasks</title><link>https://retrivium.ai/journal/qwen36-27b-vs-35b-a3b-coding/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen36-27b-vs-35b-a3b-coding/</guid><description>Compare Qwen3.6-27B and 35B-A3B on function repair and cross-file code requirements without equating active parameters with quality or speed.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.8 reasoning_effort: test deeper reasoning on text tasks</title><link>https://retrivium.ai/journal/qwen38-reasoning-effort-text-tasks/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen38-reasoning-effort-text-tasks/</guid><description>Test Qwen3.8 reasoning_effort on a bounded text problem while distinguishing the open checkpoint, hosted Qwen-Max features and answer completion.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.8 FP8 vs original weights: validate coding quality</title><link>https://retrivium.ai/journal/qwen38-fp8-vs-original-checkpoint-quality/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen38-fp8-vs-original-checkpoint-quality/</guid><description>Validate the official Qwen3.8 FP8 checkpoint against its original weights using quantization metadata, code acceptance tests and matched generation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3-Coder-Next vs Qwen3.6: specialist or general model for code</title><link>https://retrivium.ai/journal/qwen3-coder-next-vs-qwen36-code-specialization/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen3-coder-next-vs-qwen36-code-specialization/</guid><description>Compare Qwen3-Coder-Next and Qwen3.6 on code repair, requirements interpretation and final explanations using a shared text-only task.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DeepSeek-V3.2 vs Speciale: reasoning tasks and tool-use limits</title><link>https://retrivium.ai/journal/deepseek-v32-vs-speciale-reasoning-tools/</link><guid isPermaLink="true">https://retrivium.ai/journal/deepseek-v32-vs-speciale-reasoning-tools/</guid><description>Choose DeepSeek-V3.2 or Speciale by tool requirements and checked reasoning tasks while separating downloadable checkpoints from historical API offers.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DeepSeek-V3.2 thinking with tools: preserve the right history</title><link>https://retrivium.ai/journal/deepseek-v32-thinking-tool-history/</link><guid isPermaLink="true">https://retrivium.ai/journal/deepseek-v32-thinking-tool-history/</guid><description>Understand DeepSeek-V3.2 thinking history through its reference encoder, separating a new user turn from continuation after a tool result.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DeepSeek-V4 Flash vs Pro: choose by coding and reasoning task</title><link>https://retrivium.ai/journal/deepseek-v4-flash-vs-pro-task-choice/</link><guid isPermaLink="true">https://retrivium.ai/journal/deepseek-v4-flash-vs-pro-task-choice/</guid><description>Compare DeepSeek-V4 Flash and Pro through code repair, constraint solving and task acceptance, keeping checkpoint identity separate from Max effort.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DeepSeek-V4 Max effort: compare reasoning with a fair budget</title><link>https://retrivium.ai/journal/deepseek-v4-max-effort-evaluation/</link><guid isPermaLink="true">https://retrivium.ai/journal/deepseek-v4-max-effort-evaluation/</guid><description>Separate DeepSeek-V4 model variants from Max reasoning effort and compare completed answers under declared output, retry and time budgets.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DeepSeek-V4.1-Flash-1017: validate a coding-model upgrade</title><link>https://retrivium.ai/journal/deepseek-v41-flash-1017-coding-migration/</link><guid isPermaLink="true">https://retrivium.ai/journal/deepseek-v41-flash-1017-coding-migration/</guid><description>Evaluate DeepSeek-V4.1-Flash-1017 as a coding upgrade with identical fixtures, prompt encoding and acceptance tests, keeping vendor benchmarks attributed.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DeepSeek-V4.1 prompt encoding: local text messages and effort</title><link>https://retrivium.ai/journal/deepseek-v41-prompt-encoding-reference/</link><guid isPermaLink="true">https://retrivium.ai/journal/deepseek-v41-prompt-encoding-reference/</guid><description>Understand DeepSeek-V4.1 text encoding, numeric reasoning effort, changed DSML tags and system-message boundaries using the published reference.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM-4.7-Flash vs Qwen3-30B-A3B for coding and tools</title><link>https://retrivium.ai/journal/glm47-flash-vs-qwen3-30b-coding/</link><guid isPermaLink="true">https://retrivium.ai/journal/glm47-flash-vs-qwen3-30b-coding/</guid><description>Compare GLM-4.7-Flash and exact Qwen3 30B checkpoints on code repair and tool tasks, accounting for mode and prompt-format differences.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM-4.7 preserved thinking and turn-level control</title><link>https://retrivium.ai/journal/glm47-preserved-turn-level-thinking/</link><guid isPermaLink="true">https://retrivium.ai/journal/glm47-preserved-turn-level-thinking/</guid><description>Separate GLM-4.7 preserved, interleaved and turn-level thinking using the documented history rules and a concrete iterative coding conversation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM-5 vs GLM-4.7 for long-horizon engineering tasks</title><link>https://retrivium.ai/journal/glm5-vs-glm47-long-horizon-code/</link><guid isPermaLink="true">https://retrivium.ai/journal/glm5-vs-glm47-long-horizon-code/</guid><description>Compare GLM-5 and GLM-4.7 on a staged repository migration, checking interface continuity, milestones and full-task completion rather than one function.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM-5.2 vs GLM-5.3: what changes when the base model stays the same</title><link>https://retrivium.ai/journal/glm52-vs-glm53-post-training-choice/</link><guid isPermaLink="true">https://retrivium.ai/journal/glm52-vs-glm53-post-training-choice/</guid><description>Compare GLM-5.2 and GLM-5.3 as post-training variants of the same base, using requirement adherence, patch acceptance and stopping behavior.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM-5.3 thinking controls: API policy and local checkpoint behavior</title><link>https://retrivium.ai/journal/glm53-thinking-api-vs-local-controls/</link><guid isPermaLink="true">https://retrivium.ai/journal/glm53-thinking-api-vs-local-controls/</guid><description>Understand GLM-5.3 forced thinking in the documented API, separate it from local checkpoint controls and diagnose incomplete final answers.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM-5.2 long context: test repository dependency reasoning</title><link>https://retrivium.ai/journal/glm52-million-context-code-dependencies/</link><guid isPermaLink="true">https://retrivium.ai/journal/glm52-million-context-code-dependencies/</guid><description>Evaluate GLM-5.2 long context on distant code definitions, callers and stale notes using a self-contained repository bundle and checked changes.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Kimi K2 Thinking vs Instruct-0905 for text tasks</title><link>https://retrivium.ai/journal/kimi-k2-thinking-vs-instruct-0905/</link><guid isPermaLink="true">https://retrivium.ai/journal/kimi-k2-thinking-vs-instruct-0905/</guid><description>Compare Kimi K2 Thinking and Instruct-0905 by final text requirements, reasoning depth and declared output limits rather than variant names alone.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Kimi K2 Thinking INT4: native QAT and unpacked weights differ</title><link>https://retrivium.ai/journal/kimi-k2-native-int4-vs-unpacked-weights/</link><guid isPermaLink="true">https://retrivium.ai/journal/kimi-k2-native-int4-vs-unpacked-weights/</guid><description>Read Kimi K2 Thinking native INT4 QAT and compressed-tensors metadata correctly, distinguishing unpacked wider weights from an original master checkpoint.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Kimi K3 KDA and Attention Residuals: a text-model architecture guide</title><link>https://retrivium.ai/journal/kimi-k3-kda-attention-residuals-text/</link><guid isPermaLink="true">https://retrivium.ai/journal/kimi-k3-kda-attention-residuals-text/</guid><description>Understand Kimi K3 KDA, Attention Residuals and sparse experts as different architectural mechanisms, then define a bounded text reasoning check.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Kimi K3 vs K2 Thinking for long coding sessions</title><link>https://retrivium.ai/journal/kimi-k3-vs-k2-thinking-code-sessions/</link><guid isPermaLink="true">https://retrivium.ai/journal/kimi-k3-vs-k2-thinking-code-sessions/</guid><description>Compare Kimi K3 and K2 Thinking on text-only long coding sessions with retained requirements, recoverable failures and final repository acceptance.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>MiniMax-M2.5 for code repair: judge tests and patch quality</title><link>https://retrivium.ai/journal/minimax-m25-test-driven-code-repair/</link><guid isPermaLink="true">https://retrivium.ai/journal/minimax-m25-test-driven-code-repair/</guid><description>Evaluate MiniMax-M2.5 code repair by checking its proposed specification, protected tests, patch behavior and regressions on a bounded example.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>MiniMax-M2.5 tool errors: evaluate argument repair and stopping</title><link>https://retrivium.ai/journal/minimax-m25-tool-error-recovery/</link><guid isPermaLink="true">https://retrivium.ai/journal/minimax-m25-tool-error-recovery/</guid><description>Test MiniMax-M2.5 recovery from a tool validation error, separating XML parsing, argument types, schema violations and repeated invalid proposals.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>MiniMax-M2.5 vs GLM-4.7 for repository maintenance</title><link>https://retrivium.ai/journal/minimax-m25-vs-glm47-repository-maintenance/</link><guid isPermaLink="true">https://retrivium.ai/journal/minimax-m25-vs-glm47-repository-maintenance/</guid><description>Compare MiniMax-M2.5 and GLM-4.7 on routine repository maintenance, including small patches, repeated changes, tool observations and collateral edits.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Devstral 2 vs Small 2 for multi-file code changes</title><link>https://retrivium.ai/journal/devstral2-vs-small2-multifile-code/</link><guid isPermaLink="true">https://retrivium.ai/journal/devstral2-vs-small2-multifile-code/</guid><description>Compare Devstral 2 and Devstral Small 2 on linked code edits, caller consistency and regression tests while preserving exact 2512 artifact identities.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Devstral 2 vs Qwen3-Coder-Next: compare patch workflows</title><link>https://retrivium.ai/journal/devstral2-vs-qwen-coder-next-patches/</link><guid isPermaLink="true">https://retrivium.ai/journal/devstral2-vs-qwen-coder-next-patches/</guid><description>Compare dense Devstral 2 and hybrid Qwen3-Coder-Next on patch application, requirement retention and final tests without translating architecture into a ranking.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Devstral Small 2: a deprecated API and downloadable weights</title><link>https://retrivium.ai/journal/devstral-small2-deprecated-api-open-weights/</link><guid isPermaLink="true">https://retrivium.ai/journal/devstral-small2-deprecated-api-open-weights/</guid><description>Understand Devstral Small 2 API deprecation separately from its versioned open-weight artifact, local evaluation and replacement-model decisions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Ministral 3 Instruct vs Reasoning for short text and math</title><link>https://retrivium.ai/journal/ministral3-instruct-vs-reasoning-text/</link><guid isPermaLink="true">https://retrivium.ai/journal/ministral3-instruct-vs-reasoning-text/</guid><description>Choose Ministral 3 8B Instruct or Reasoning using their distinct post-training, precision, sampling guidance and checked text-task requirements.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Ministral 3 3B, 8B or 14B for bounded text tasks</title><link>https://retrivium.ai/journal/ministral3-3b-8b-14b-text-selection/</link><guid isPermaLink="true">https://retrivium.ai/journal/ministral3-3b-8b-14b-text-selection/</guid><description>Choose among Ministral 3 3B, 8B and 14B for bounded text tasks using a fixed variant, clear labels, counterexamples and accepted outcomes.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mistral Small 4 reasoning_effort: none vs high</title><link>https://retrivium.ai/journal/mistral-small4-reasoning-none-high/</link><guid isPermaLink="true">https://retrivium.ai/journal/mistral-small4-reasoning-none-high/</guid><description>Use Mistral Small 4 reasoning_effort none and high as separate operating conditions, checking final answers, sampling settings and completion.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mistral Small 4 vs Devstral 2 for mixed text and code work</title><link>https://retrivium.ai/journal/mistral-small4-vs-devstral2-code-generalist/</link><guid isPermaLink="true">https://retrivium.ai/journal/mistral-small4-vs-devstral2-code-generalist/</guid><description>Choose Mistral Small 4 or Devstral 2 for mixed text and code work by evaluating requirements interpretation, patch correctness and final explanations.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mistral Small 4 NVFP4 vs original checkpoint: test task quality</title><link>https://retrivium.ai/journal/mistral-small4-nvfp4-checkpoint-choice/</link><guid isPermaLink="true">https://retrivium.ai/journal/mistral-small4-nvfp4-checkpoint-choice/</guid><description>Evaluate Mistral Small 4 NVFP4 against its original checkpoint through artifact provenance, matched reasoning settings and bounded text and code checks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Ministral 3 vs Gemma 4: reasoning history rules differ</title><link>https://retrivium.ai/journal/ministral3-vs-gemma4-thinking-history/</link><guid isPermaLink="true">https://retrivium.ai/journal/ministral3-vs-gemma4-thinking-history/</guid><description>Compare Ministral 3 and Gemma 4 reasoning-history rules, separating ordinary completed turns from tool continuations and final-answer fields.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Gemma 4 26B-A4B vs 31B for text coding tasks</title><link>https://retrivium.ai/journal/gemma4-26b-a4b-vs-31b-coding/</link><guid isPermaLink="true">https://retrivium.ai/journal/gemma4-26b-a4b-vs-31b-coding/</guid><description>Compare Gemma 4 26B-A4B and 31B for text coding tasks using their documented MoE and dense designs, matched thinking and independent patch checks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Moving from Gemma 3 to Gemma 4: system roles and text prompts</title><link>https://retrivium.ai/journal/gemma3-to-gemma4-system-prompt-roles/</link><guid isPermaLink="true">https://retrivium.ai/journal/gemma3-to-gemma4-system-prompt-roles/</guid><description>Migrate Gemma 3 text prompts to Gemma 4 by separating structured message roles, rendered control tokens and duplicated system instructions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Gemma 4 thinking mode and empty thought blocks</title><link>https://retrivium.ai/journal/gemma4-thinking-channel-empty-block/</link><guid isPermaLink="true">https://retrivium.ai/journal/gemma4-thinking-channel-empty-block/</guid><description>Explain Gemma 4 empty thought blocks and enable_thinking behavior, separating template-supplied prefixes, generated tokens and final-answer parsing.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Gemma 4 QAT unquantized vs GGUF: choose the right artifact</title><link>https://retrivium.ai/journal/gemma4-qat-unquantized-vs-gguf/</link><guid isPermaLink="true">https://retrivium.ai/journal/gemma4-qat-unquantized-vs-gguf/</guid><description>Distinguish Gemma 4 unquantized QAT weights from ready-to-run GGUF Q4_0 artifacts, their intended uses and task-quality acceptance.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Gemma 4 vs Qwen3.6 for Russian and English text instructions</title><link>https://retrivium.ai/journal/gemma4-vs-qwen36-russian-english-text/</link><guid isPermaLink="true">https://retrivium.ai/journal/gemma4-vs-qwen36-russian-english-text/</guid><description>Compare Gemma 4 and Qwen3.6 on matched Russian and English text instructions, terminology, negation and code explanations with independent references.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Granite 4.0 Hybrid vs Granite 4.2 Dense: identify the model first</title><link>https://retrivium.ai/journal/granite4-hybrid-vs-granite42-dense/</link><guid isPermaLink="true">https://retrivium.ai/journal/granite4-hybrid-vs-granite42-dense/</guid><description>Distinguish Granite 4.0 H-Small hybrid MoE from Granite 4.2 dense models using exact architecture metadata, model scale and task acceptance.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Granite 4.2 full, low-effort and non-thinking modes</title><link>https://retrivium.ai/journal/granite42-thinking-low-effort-selection/</link><guid isPermaLink="true">https://retrivium.ai/journal/granite42-thinking-low-effort-selection/</guid><description>Use Granite 4.2 full, low-effort and non-thinking modes through their actual template controls, then check final answers and history behavior.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Granite 4.2 in Russian: test beyond the published language list</title><link>https://retrivium.ai/journal/granite42-russian-language-evaluation/</link><guid isPermaLink="true">https://retrivium.ai/journal/granite42-russian-language-evaluation/</guid><description>Evaluate Granite 4.2 for Russian text without treating its published tested-language list as either a guarantee of accuracy or proof of impossibility.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron 3 Nano thinking budget: understand the actual mechanism</title><link>https://retrivium.ai/journal/nemotron3-nano-thinking-budget-mechanism/</link><guid isPermaLink="true">https://retrivium.ai/journal/nemotron3-nano-thinking-budget-mechanism/</guid><description>Understand Nemotron 3 Nano reasoning-budget control through its documented client mechanism, continuation request and remaining final-answer allowance.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron 3 Nano vs Qwen3-Next: different hybrid text models</title><link>https://retrivium.ai/journal/nemotron3-nano-vs-qwen3-next-hybrid/</link><guid isPermaLink="true">https://retrivium.ai/journal/nemotron3-nano-vs-qwen3-next-hybrid/</guid><description>Compare Nemotron 3 Nano and Qwen3-Next as different hybrid text models, separating Mamba-based sequence processing, Gated DeltaNet and task outcomes.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron 3 Super vs Nano: choose by reasoning task</title><link>https://retrivium.ai/journal/nemotron3-super-vs-nano-task-escalation/</link><guid isPermaLink="true">https://retrivium.ai/journal/nemotron3-super-vs-nano-task-escalation/</guid><description>Choose Nemotron 3 Super or Nano using checked reasoning tasks while separating LatentMoE design, training precision and downloaded checkpoint dtype.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SmolLM3 /think vs /no_think for small text tasks</title><link>https://retrivium.ai/journal/smollm3-thinking-vs-no-think-tasks/</link><guid isPermaLink="true">https://retrivium.ai/journal/smollm3-thinking-vs-no-think-tasks/</guid><description>Evaluate SmolLM3 /think and /no_think on concise text and checked reasoning, preserving the documented system-prompt controls and language scope.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Best local LLM for coding in 2026: choose by the task</title><link>https://retrivium.ai/journal/best-local-llm-coding-2026-task-shortlist/</link><guid isPermaLink="true">https://retrivium.ai/journal/best-local-llm-coding-2026-task-shortlist/</guid><description>Build a practical 2026 local coding LLM shortlist from verified Qwen, Devstral, GLM and Gemma checkpoints using task-specific acceptance criteria.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5 vs LFM2 for narrow text tasks: respect the task boundary</title><link>https://retrivium.ai/journal/lfm25-vs-lfm2-narrow-text-tasks/</link><guid isPermaLink="true">https://retrivium.ai/journal/lfm25-vs-lfm2-narrow-text-tasks/</guid><description>Compare LFM2.5 and LFM2 on narrow text decisions while respecting the model cards&apos; limits on programming and knowledge-intensive workloads.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>BitNet b1.58 vs four-bit PTQ: native training and runtime matter</title><link>https://retrivium.ai/journal/bitnet-native-158-vs-post-training-quantization/</link><guid isPermaLink="true">https://retrivium.ai/journal/bitnet-native-158-vs-post-training-quantization/</guid><description>Distinguish BitNet b1.58 native ternary training from four-bit post-training quantization, packed artifacts and runtime-specific efficiency claims.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Falcon-H1: evaluate a parallel attention and SSM text model</title><link>https://retrivium.ai/journal/falcon-h1-parallel-hybrid-text-evaluation/</link><guid isPermaLink="true">https://retrivium.ai/journal/falcon-h1-parallel-hybrid-text-evaluation/</guid><description>Understand Falcon-H1 parallel attention and SSM design, identify the exact 1.5B Instruct checkpoint and evaluate a bounded text requirement chain.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Olmo 3 Think vs Instruct: choose a task and a model-flow checkpoint</title><link>https://retrivium.ai/journal/olmo3-think-vs-instruct-model-flow/</link><guid isPermaLink="true">https://retrivium.ai/journal/olmo3-think-vs-instruct-model-flow/</guid><description>Choose Olmo 3 Think or Instruct by task while distinguishing final releases from Base, SFT, DPO and intermediate model-flow checkpoints.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LM Studio: start a local desktop assistant</title><link>https://retrivium.ai/journal/lm-studio-first-local-assistant/</link><guid isPermaLink="true">https://retrivium.ai/journal/lm-studio-first-local-assistant/</guid><description>Set up a first LM Studio conversation, identify the local model, and separate desktop chat from optional tools and editor connections.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LM Studio vs Ollama: choose a local coding workflow</title><link>https://retrivium.ai/journal/lm-studio-vs-ollama-coding-workflow/</link><guid isPermaLink="true">https://retrivium.ai/journal/lm-studio-vs-ollama-coding-workflow/</guid><description>Compare LM Studio and Ollama by model management, editor handoff, and code review workflow without unsupported speed rankings.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Use the LM Studio local API from an editor</title><link>https://retrivium.ai/journal/lm-studio-local-api-app-onboarding/</link><guid isPermaLink="true">https://retrivium.ai/journal/lm-studio-local-api-app-onboarding/</guid><description>Connect an editor to the LM Studio local server, verify the selected model, and test explanation before allowing file edits.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>llmster: local AI without the LM Studio desktop window</title><link>https://retrivium.ai/journal/llmster-without-lm-studio-gui/</link><guid isPermaLink="true">https://retrivium.ai/journal/llmster-without-lm-studio-gui/</guid><description>Understand llmster, lms, and the desktop app, then verify a local editor workflow without keeping the graphical window open.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Jan vs LM Studio: choose a local desktop assistant</title><link>https://retrivium.ai/journal/jan-vs-lm-studio-local-desktop/</link><guid isPermaLink="true">https://retrivium.ai/journal/jan-vs-lm-studio-local-desktop/</guid><description>Compare Jan and LM Studio for desktop conversations, project organization, local API access, and separately configured agent workflows.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Jan Desktop: a first local project and model source</title><link>https://retrivium.ai/journal/jan-first-local-project/</link><guid isPermaLink="true">https://retrivium.ai/journal/jan-first-local-project/</guid><description>Create a first Jan Desktop project and distinguish conversation organization from the local or remote source of generated answers.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Jan Agent with a local model: a first reviewed edit</title><link>https://retrivium.ai/journal/jan-agent-local-coding-workflow/</link><guid isPermaLink="true">https://retrivium.ai/journal/jan-agent-local-coding-workflow/</guid><description>Use Jan Agent with a verified local model endpoint for a small coding task, with explicit action scope and reviewed file changes.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Open WebUI with Ollama: connect an existing local runtime</title><link>https://retrivium.ai/journal/open-webui-with-ollama-local-chat/</link><guid isPermaLink="true">https://retrivium.ai/journal/open-webui-with-ollama-local-chat/</guid><description>Connect an existing Ollama runtime to Open WebUI and verify model selection, account visibility, and a follow-up conversation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Open WebUI with vLLM: backend models and workspace wrappers</title><link>https://retrivium.ai/journal/open-webui-vllm-model-workspace/</link><guid isPermaLink="true">https://retrivium.ai/journal/open-webui-vllm-model-workspace/</guid><description>Connect Open WebUI to an existing vLLM endpoint and distinguish backend model identity, Workspace wrappers, and user access.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Open WebUI vs AnythingLLM vs LibreChat for local AI</title><link>https://retrivium.ai/journal/open-webui-anythingllm-librechat-choice/</link><guid isPermaLink="true">https://retrivium.ai/journal/open-webui-anythingllm-librechat-choice/</guid><description>Compare Open WebUI, AnythingLLM Desktop, and LibreChat by workspace ownership, model wrappers, reusable agents, and access requirements.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Open WebUI Desktop or server UI: choose the local workflow</title><link>https://retrivium.ai/journal/open-webui-native-desktop-workflow/</link><guid isPermaLink="true">https://retrivium.ai/journal/open-webui-native-desktop-workflow/</guid><description>Start with Open WebUI’s native desktop option and a working model connection, then verify conversations and optional Workspace wrappers.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LibreChat with local models: build a first reusable agent</title><link>https://retrivium.ai/journal/librechat-local-model-agent-start/</link><guid isPermaLink="true">https://retrivium.ai/journal/librechat-local-model-agent-start/</guid><description>Create a minimal LibreChat agent with a working local model, required builder fields, narrow instructions, and a repeatable trial.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AnythingLLM Desktop: built-in inference or a local server</title><link>https://retrivium.ai/journal/anythingllm-desktop-local-model-start/</link><guid isPermaLink="true">https://retrivium.ai/journal/anythingllm-desktop-local-model-start/</guid><description>Configure AnythingLLM Desktop’s language model provider and verify a plain conversation before adding documents or optional agent tools.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AnythingLLM Desktop vs server: personal and shared workspaces</title><link>https://retrivium.ai/journal/anythingllm-desktop-vs-server-users/</link><guid isPermaLink="true">https://retrivium.ai/journal/anythingllm-desktop-vs-server-users/</guid><description>Choose AnythingLLM Desktop or its server product by personal ownership, independent accounts, invitations, and workspace access requirements.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Continue vs Cline vs Aider for local coding</title><link>https://retrivium.ai/journal/continue-cline-aider-coding-choice/</link><guid isPermaLink="true">https://retrivium.ai/journal/continue-cline-aider-coding-choice/</guid><description>Compare Continue, Cline, and Aider for local coding by IDE assistance, agent actions, Git integration, and the way changes are reviewed.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Continue with a local model: chat and autocomplete roles</title><link>https://retrivium.ai/journal/continue-local-vscode-chat-completion/</link><guid isPermaLink="true">https://retrivium.ai/journal/continue-local-vscode-chat-completion/</guid><description>Configure Continue in VS Code with a local model and separate chat and autocomplete roles, then verify each editor operation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Cline with LM Studio or Ollama: a reviewed local edit</title><link>https://retrivium.ai/journal/cline-local-server-reviewed-edit/</link><guid isPermaLink="true">https://retrivium.ai/journal/cline-local-server-reviewed-edit/</guid><description>Make a first local Cline edit through a verified runtime, a small repository task, visible tool actions, and an inspected diff.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Cline Desktop vs IDE extension for local models</title><link>https://retrivium.ai/journal/cline-desktop-vs-ide-local-models/</link><guid isPermaLink="true">https://retrivium.ai/journal/cline-desktop-vs-ide-local-models/</guid><description>Compare Cline Desktop and IDE workflows by local model management, runtime selection, repository context, and review of the same small edit.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Aider with local models: make and review a repository edit</title><link>https://retrivium.ai/journal/aider-local-model-editing-start/</link><guid isPermaLink="true">https://retrivium.ai/journal/aider-local-model-editing-start/</guid><description>Start Aider with a local Ollama model, an understood Git state, explicitly selected files, and a small change that can be reviewed.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenCode custom provider: local model configuration in V2</title><link>https://retrivium.ai/journal/opencode-v2-custom-local-provider/</link><guid isPermaLink="true">https://retrivium.ai/journal/opencode-v2-custom-local-provider/</guid><description>Configure an OpenCode V2 custom local provider with the correct package, endpoint, model entry, and explicit provider/model selection.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenHands Agent Canvas: local workspace, backend and model</title><link>https://retrivium.ai/journal/openhands-agent-canvas-local-workflow/</link><guid isPermaLink="true">https://retrivium.ai/journal/openhands-agent-canvas-local-workflow/</guid><description>Use OpenHands Agent Canvas with an existing local model, a local backend, an explicit workspace, and a small reviewed coding task.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Zed with a local model: start the native agent workflow</title><link>https://retrivium.ai/journal/zed-native-local-ai-start/</link><guid isPermaLink="true">https://retrivium.ai/journal/zed-native-local-ai-start/</guid><description>Connect a local model to Zed’s native Agent, verify model discovery, and distinguish agent tools from edit prediction and external agents.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>goose with a local model: validate a first project task</title><link>https://retrivium.ai/journal/goose-local-model-first-task/</link><guid isPermaLink="true">https://retrivium.ai/journal/goose-local-model-first-task/</guid><description>Configure Goose with Ollama or LM Studio for a first local task, distinguishing model generation from extension tools and their permissions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Cherry Studio: local chat providers versus helper models</title><link>https://retrivium.ai/journal/cherry-studio-local-chat-model-choice/</link><guid isPermaLink="true">https://retrivium.ai/journal/cherry-studio-local-chat-model-choice/</guid><description>Choose a conversational local model in Cherry Studio through Model Provider settings and avoid confusing it with built-in auxiliary models.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Dify with a local LLM: connect a provider and build an app</title><link>https://retrivium.ai/journal/dify-local-llm-first-app/</link><guid isPermaLink="true">https://retrivium.ai/journal/dify-local-llm-first-app/</guid><description>Connect a local language model to an existing Dify workspace, select it in a minimal app, and distinguish provider setup from node defaults.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>n8n with a local LLM: a bounded chat-model workflow</title><link>https://retrivium.ai/journal/n8n-local-ai-chat-workflow/</link><guid isPermaLink="true">https://retrivium.ai/journal/n8n-local-ai-chat-workflow/</guid><description>Build a first local AI workflow in an existing n8n instance using Ollama credentials, a chat model connection, and explicit input mapping.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Flowise with Ollama: build and test a local Chatflow</title><link>https://retrivium.ai/journal/flowise-local-chatflow-first-run/</link><guid isPermaLink="true">https://retrivium.ai/journal/flowise-local-chatflow-first-run/</guid><description>Create a first Flowise chatflow using an existing Ollama model, the ChatOllama node, and a minimal conversational path before adding agents.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Langflow with a local model: a first conversational flow</title><link>https://retrivium.ai/journal/langflow-local-model-first-flow/</link><guid isPermaLink="true">https://retrivium.ai/journal/langflow-local-model-first-flow/</guid><description>Build a local Langflow conversation with Model Providers, a Language Model component, explicit input/output connections, and Playground verification.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>n8n vs Dify vs Flowise vs Langflow for local AI workflows</title><link>https://retrivium.ai/journal/n8n-dify-flowise-langflow-choice/</link><guid isPermaLink="true">https://retrivium.ai/journal/n8n-dify-flowise-langflow-choice/</guid><description>Compare n8n, Dify, Flowise, and Langflow for local AI applications by workflow structure, model ownership, and the first useful output.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Choose a local AI stack: desktop chat, shared UI or coding agent</title><link>https://retrivium.ai/journal/local-ai-app-stack-selection/</link><guid isPermaLink="true">https://retrivium.ai/journal/local-ai-app-stack-selection/</guid><description>Choose a minimal local AI application stack by separating the model runtime, conversation interface, coding client, and optional tools.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Local coding assistants: first read, edit, review and test</title><link>https://retrivium.ai/journal/local-coding-app-read-edit-review-test/</link><guid isPermaLink="true">https://retrivium.ai/journal/local-coding-app-read-edit-review-test/</guid><description>Complete a first local coding task through explicit reading, a small edit, diff review, and actual test output across coding applications.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LM Studio chat works but an editor cannot use the model</title><link>https://retrivium.ai/journal/lm-studio-chat-works-editor-cannot-connect/</link><guid isPermaLink="true">https://retrivium.ai/journal/lm-studio-chat-works-editor-cannot-connect/</guid><description>Diagnose an editor that cannot use LM Studio despite a working desktop chat by separating runtime state, local serving, and client model selection.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Jan server will not start: check the local startup model</title><link>https://retrivium.ai/journal/jan-local-server-startup-model-required/</link><guid isPermaLink="true">https://retrivium.ai/journal/jan-local-server-startup-model-required/</guid><description>Fix Jan API server startup by selecting a loadable local default model, while keeping later remote-provider routing as a separate behavior.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Open WebUI model is visible to admin but not another user</title><link>https://retrivium.ai/journal/open-webui-model-visible-admin-only/</link><guid isPermaLink="true">https://retrivium.ai/journal/open-webui-model-visible-admin-only/</guid><description>Diagnose Open WebUI models visible only to an administrator by separating backend inventory, hidden entries, base access, and Workspace sharing.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Open WebUI Tools, Functions and Pipes: choose an extension</title><link>https://retrivium.ai/journal/open-webui-tools-functions-pipes-choice/</link><guid isPermaLink="true">https://retrivium.ai/journal/open-webui-tools-functions-pipes-choice/</guid><description>Choose an Open WebUI extension by its job: callable Tool, selectable Pipe, message Filter, user-triggered Action, or existing HTTP integration.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LibreChat MCP connects but the agent has no tool</title><link>https://retrivium.ai/journal/librechat-agent-mcp-tool-not-visible/</link><guid isPermaLink="true">https://retrivium.ai/journal/librechat-agent-mcp-tool-not-visible/</guid><description>Find a missing LibreChat MCP tool by checking ordinary chat selection, Agent Builder bindings, per-user authentication, and model capabilities.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LibreChat Code Interpreter: execute code and retrieve files</title><link>https://retrivium.ai/journal/librechat-code-interpreter-files-workflow/</link><guid isPermaLink="true">https://retrivium.ai/journal/librechat-code-interpreter-files-workflow/</guid><description>Use LibreChat Code Interpreter on a configured instance, attach files to its code environment, inspect execution output, and retrieve generated files.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AnythingLLM Desktop MCP tools do not start or get called</title><link>https://retrivium.ai/journal/anythingllm-desktop-mcp-not-starting/</link><guid isPermaLink="true">https://retrivium.ai/journal/anythingllm-desktop-mcp-not-starting/</guid><description>Fix AnythingLLM Desktop MCP startup through Agent Skills, host command availability, configuration refresh, and supported tool capabilities.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Continue chat works but autocomplete does not appear</title><link>https://retrivium.ai/journal/continue-chat-works-autocomplete-missing/</link><guid isPermaLink="true">https://retrivium.ai/journal/continue-chat-works-autocomplete-missing/</guid><description>Diagnose missing Continue inline suggestions by checking the active autocomplete role, selected model, invocation behavior, and output filtering.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Undo Cline edits: checkpoints, Git history and side effects</title><link>https://retrivium.ai/journal/cline-checkpoints-restore-boundaries/</link><guid isPermaLink="true">https://retrivium.ai/journal/cline-checkpoints-restore-boundaries/</guid><description>Understand Cline checkpoint restore options, the shadow Git repository, conversation history, and effects that file restoration does not reverse.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Aider commits and undo with existing repository changes</title><link>https://retrivium.ai/journal/aider-git-dirty-tree-undo/</link><guid isPermaLink="true">https://retrivium.ai/journal/aider-git-dirty-tree-undo/</guid><description>Use Aider with existing repository changes by separating user work, automatic commits, diff review, and the actual boundary of undo.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Aider repo map versus files added for editing</title><link>https://retrivium.ai/journal/aider-repomap-editable-files/</link><guid isPermaLink="true">https://retrivium.ai/journal/aider-repomap-editable-files/</guid><description>Distinguish Aider’s repository map from editable files, then supply the right implementation and reference context for a focused local change.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenCode V2 responds but a tool is denied</title><link>https://retrivium.ai/journal/opencode-v2-tool-permission-denied/</link><guid isPermaLink="true">https://retrivium.ai/journal/opencode-v2-tool-permission-denied/</guid><description>Diagnose OpenCode V2 tool denials through ordered permission rules, actual action names, agent overrides, and multi-resource decisions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenCode V1 to V2: keep a local coding workflow</title><link>https://retrivium.ai/journal/opencode-v1-v2-local-migration/</link><guid isPermaLink="true">https://retrivium.ai/journal/opencode-v1-v2-local-migration/</guid><description>Move an existing local OpenCode workflow from V1 to V2 by checking the executable generation, provider schema, permissions, and one small task.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenHands Canvas cannot find project files: locate the backend workspace</title><link>https://retrivium.ai/journal/openhands-canvas-workspace-file-location/</link><guid isPermaLink="true">https://retrivium.ai/journal/openhands-canvas-workspace-file-location/</guid><description>Locate missing project files in OpenHands Agent Canvas by distinguishing the browser, execution backend, active workspace, and model endpoint.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Zed native or ACP agent: which settings apply?</title><link>https://retrivium.ai/journal/zed-native-vs-acp-settings-owner/</link><guid isPermaLink="true">https://retrivium.ai/journal/zed-native-vs-acp-settings-owner/</guid><description>Find the owner of Zed AI settings by distinguishing its native Agent, external ACP processes, forwarded MCP tools, and agent-native configuration.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Roo Code is retired: preserve a local workflow before migrating</title><link>https://retrivium.ai/journal/roo-code-retired-local-workflow-migration/</link><guid isPermaLink="true">https://retrivium.ai/journal/roo-code-retired-local-workflow-migration/</guid><description>Preserve an existing Roo Code local workflow after its official retirement by inventorying rules and model choices before evaluating a replacement.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>goose connects to a model but a local extension is unavailable</title><link>https://retrivium.ai/journal/goose-local-extension-not-found/</link><guid isPermaLink="true">https://retrivium.ai/journal/goose-local-extension-not-found/</guid><description>Diagnose unavailable Goose extensions through activation, process startup, command availability, tool permissions, and local model tool support.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LM Studio presets do not restore model load settings</title><link>https://retrivium.ai/journal/lm-studio-presets-load-defaults/</link><guid isPermaLink="true">https://retrivium.ai/journal/lm-studio-presets-load-defaults/</guid><description>Separate LM Studio chat presets from per-model load defaults, then save reusable instructions and model loading choices in the correct places.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Jan Agent fork and rewind: history versus file restoration</title><link>https://retrivium.ai/journal/jan-agent-fork-rewind-files/</link><guid isPermaLink="true">https://retrivium.ai/journal/jan-agent-fork-rewind-files/</guid><description>Use Jan Agent fork and rewind with clear boundaries between saved sessions, Git-based file restoration, project identity, and durable memory.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Jan Agent safe mode and shell sandbox are different controls</title><link>https://retrivium.ai/journal/jan-safe-mode-shell-sandbox/</link><guid isPermaLink="true">https://retrivium.ai/journal/jan-safe-mode-shell-sandbox/</guid><description>Separate Jan Agent approval prompts from shell confinement, inspect effective project settings and account for memory tools that follow their own policy.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Export Open WebUI chats and workspace items with the right scope</title><link>https://retrivium.ai/journal/open-webui-chat-vs-workspace-export/</link><guid isPermaLink="true">https://retrivium.ai/journal/open-webui-chat-vs-workspace-export/</guid><description>Move Open WebUI conversations and workspace definitions using separate exports, account for fresh import IDs and verify attached resources on the target instance.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Open WebUI prompt variables: reusable task forms</title><link>https://retrivium.ai/journal/open-webui-prompt-template-variables/</link><guid isPermaLink="true">https://retrivium.ai/journal/open-webui-prompt-template-variables/</guid><description>Build Open WebUI slash-command prompts with typed inputs, distinguish system substitutions from user fields and keep prompt templates separate from model wrappers.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Share a LibreChat agent without assuming tools share access</title><link>https://retrivium.ai/journal/librechat-share-agent-tool-permissions/</link><guid isPermaLink="true">https://retrivium.ai/journal/librechat-share-agent-tool-permissions/</guid><description>Share a LibreChat agent through explicit roles while keeping model access, MCP credentials and tool approval separate for each user.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Continue project rules and current configuration</title><link>https://retrivium.ai/journal/continue-project-rules-current-config/</link><guid isPermaLink="true">https://retrivium.ai/journal/continue-project-rules-current-config/</guid><description>Use Continue project rules alongside current YAML model configuration, distinguish instructions from enforcement and migrate legacy examples with their scope intact.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Aider architect and editor roles with local models</title><link>https://retrivium.ai/journal/aider-architect-editor-local-workflow/</link><guid isPermaLink="true">https://retrivium.ai/journal/aider-architect-editor-local-workflow/</guid><description>Configure Aider architect and editor responsibilities for local models, distinguish discussion from editing, and review the resulting repository changes.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenHands repository skills: migrate older instruction examples</title><link>https://retrivium.ai/journal/openhands-repository-skills-current-layout/</link><guid isPermaLink="true">https://retrivium.ai/journal/openhands-repository-skills-current-layout/</guid><description>Migrate OpenHands repository instructions into concise AGENTS.md guidance and current Agent Skills locations while separating hooks, setup and tool permissions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Zed Agent Profiles: availability is not tool approval</title><link>https://retrivium.ai/journal/zed-agent-profiles-tool-availability/</link><guid isPermaLink="true">https://retrivium.ai/journal/zed-agent-profiles-tool-availability/</guid><description>Configure Zed native Agent Profiles separately from tool approval policy, identify the active profile and keep external ACP agent settings in their own scope.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>goose recipes: repeat a local task with explicit inputs</title><link>https://retrivium.ai/journal/goose-recipes-local-task-reuse/</link><guid isPermaLink="true">https://retrivium.ai/journal/goose-recipes-local-task-reuse/</guid><description>Create reusable goose recipes with explicit parameters, compatible extensions and a verified local model, then test missing inputs before trusting repeated runs.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Cherry Studio backup versus archive: what is restored?</title><link>https://retrivium.ai/journal/cherry-studio-backup-archive-local-data/</link><guid isPermaLink="true">https://retrivium.ai/journal/cherry-studio-backup-archive-local-data/</guid><description>Separate Cherry Studio backups from its Archive, compare full and Lite content, and verify restore dependencies before relying on a local data recovery plan.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qdrant RRF versus DBSF: choose fusion with a held-out query set</title><link>https://retrivium.ai/journal/qdrant-rrf-dbsf-fusion-selection/</link><guid isPermaLink="true">https://retrivium.ai/journal/qdrant-rrf-dbsf-fusion-selection/</guid><description>RRF and DBSF answer different fusion questions in Qdrant: one combines positions, while the other preserves information about score gaps.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qdrant filtered HNSW: payload indexes are part of the search plan</title><link>https://retrivium.ai/journal/qdrant-payload-index-filtered-hnsw/</link><guid isPermaLink="true">https://retrivium.ai/journal/qdrant-payload-index-filtered-hnsw/</guid><description>A metadata filter changes the search problem in Qdrant, rather than merely hiding rows after retrieval.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>ColBERT in Qdrant: preserve token vectors and MaxSim semantics</title><link>https://retrivium.ai/journal/qdrant-colbert-maxsim-multivectors/</link><guid isPermaLink="true">https://retrivium.ai/journal/qdrant-colbert-maxsim-multivectors/</guid><description>A ColBERT representation is a matrix of token vectors, not a longer ordinary embedding to average before searching.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qdrant document grouping: stop one document from filling every result</title><link>https://retrivium.ai/journal/qdrant-document-grouping-chunk-diversity/</link><guid isPermaLink="true">https://retrivium.ai/journal/qdrant-document-grouping-chunk-diversity/</guid><description>Document grouping in Qdrant answers a different question from returning the nearest chunks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>pgvector halfvec indexing: retain full vectors for final scoring</title><link>https://retrivium.ai/journal/pgvector-halfvec-expression-index-rerank/</link><guid isPermaLink="true">https://retrivium.ai/journal/pgvector-halfvec-expression-index-rerank/</guid><description>A halfvec expression index can use a reduced-precision search representation without replacing the original vectors stored in the table.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>pgvector binary quantization: Hamming candidates need full-vector reranking</title><link>https://retrivium.ai/journal/pgvector-binary-hamming-candidate-rerank/</link><guid isPermaLink="true">https://retrivium.ai/journal/pgvector-binary-hamming-candidate-rerank/</guid><description>Binary quantization in pgvector is a candidate-generation technique, not a replacement for checking final relevance with the intended vector metric.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>pgvector cosine and inner product: normalization and ORDER BY must agree</title><link>https://retrivium.ai/journal/pgvector-cosine-inner-product-ordering/</link><guid isPermaLink="true">https://retrivium.ai/journal/pgvector-cosine-inner-product-ordering/</guid><description>Cosine distance and inner product can produce compatible rankings under particular normalization conditions, but their SQL operators do not have the same sign or meaning.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Milvus BM25 functions: combine server-generated sparse and dense retrieval</title><link>https://retrivium.ai/journal/milvus-bm25-function-dense-sparse-fusion/</link><guid isPermaLink="true">https://retrivium.ai/journal/milvus-bm25-function-dense-sparse-fusion/</guid><description>Milvus can generate BM25 sparse vectors from raw text through a declared function while searching a separate dense representation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Milvus consistency: why a newly inserted document is not yet found</title><link>https://retrivium.ai/journal/milvus-consistency-new-document-visibility/</link><guid isPermaLink="true">https://retrivium.ai/journal/milvus-consistency-new-document-visibility/</guid><description>An acknowledged insert and a searchable document are different observations in Milvus.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Milvus partition keys: tenant routing is not an authorization policy</title><link>https://retrivium.ai/journal/milvus-partition-key-tenant-query-boundary/</link><guid isPermaLink="true">https://retrivium.ai/journal/milvus-partition-key-tenant-query-boundary/</guid><description>A Milvus partition key helps organize and route data, but it is not an application authorization policy.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Weaviate hybrid fusion: alpha and score gaps change different decisions</title><link>https://retrivium.ai/journal/weaviate-hybrid-fusion-alpha-score-gaps/</link><guid isPermaLink="true">https://retrivium.ai/journal/weaviate-hybrid-fusion-alpha-score-gaps/</guid><description>Weaviate hybrid fusion combines lexical and vector results, but changing the fusion strategy is not the same intervention as changing alpha.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Weaviate filtered search: compare sweeping, ACORN and PathSeer</title><link>https://retrivium.ai/journal/weaviate-filter-strategies-acorn-pathseer/</link><guid isPermaLink="true">https://retrivium.ai/journal/weaviate-filter-strategies-acorn-pathseer/</guid><description>Filtered HNSW in Weaviate has several traversal strategies, so choosing ACORN is not simply enabling a generic filter.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Weaviate BM25F: rank titles and body text without filtering evidence away</title><link>https://retrivium.ai/journal/weaviate-bm25f-field-weighting/</link><guid isPermaLink="true">https://retrivium.ai/journal/weaviate-bm25f-field-weighting/</guid><description>BM25F field weights in Weaviate change how lexical evidence contributes to ranking; they do not replace the decision about which evidence is searchable.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Elasticsearch hybrid search: RRF versus normalized linear retrieval</title><link>https://retrivium.ai/journal/elasticsearch-rrf-linear-hybrid-retrievers/</link><guid isPermaLink="true">https://retrivium.ai/journal/elasticsearch-rrf-linear-hybrid-retrievers/</guid><description>Elasticsearch RRF and linear retrievers combine signals through different contracts: rank positions versus normalized weighted scores.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenSearch hybrid search: normalization and score-ranker pipelines</title><link>https://retrivium.ai/journal/opensearch-hybrid-normalization-score-ranker/</link><guid isPermaLink="true">https://retrivium.ai/journal/opensearch-hybrid-normalization-score-ranker/</guid><description>OpenSearch score normalization and reciprocal rank fusion belong to different search-pipeline configurations.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LanceDB phrase search: preserve positions before hybrid retrieval</title><link>https://retrivium.ai/journal/lancedb-phrase-search-hybrid-candidates/</link><guid isPermaLink="true">https://retrivium.ai/journal/lancedb-phrase-search-hybrid-candidates/</guid><description>Phrase retrieval in LanceDB requires an index and query contract that preserves word positions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RAG chunking strategies: document structure versus fixed token windows</title><link>https://retrivium.ai/journal/rag-chunking-structure-token-boundaries/</link><guid isPermaLink="true">https://retrivium.ai/journal/rag-chunking-structure-token-boundaries/</guid><description>A RAG chunking strategy defines which evidence can be retrieved together, not just how many tokens enter an embedding call.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Late chunking for RAG: embed context before pooling fragments</title><link>https://retrivium.ai/journal/rag-late-chunking-contextual-embeddings/</link><guid isPermaLink="true">https://retrivium.ai/journal/rag-late-chunking-contextual-embeddings/</guid><description>Late chunking encodes broader document context before pooling token ranges into chunk embeddings.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RAG chunk overlap: measure lost boundaries and duplicated evidence</title><link>https://retrivium.ai/journal/rag-chunk-overlap-duplicate-evidence/</link><guid isPermaLink="true">https://retrivium.ai/journal/rag-chunk-overlap-duplicate-evidence/</guid><description>Increasing chunk overlap changes both boundary coverage and repeated evidence in a RAG index.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Chunk tables for RAG without losing column headers and units</title><link>https://retrivium.ai/journal/rag-table-chunks-headers-units/</link><guid isPermaLink="true">https://retrivium.ai/journal/rag-table-chunks-headers-units/</guid><description>A retrievable table fragment needs enough structure to explain what each value means, not merely the characters from one row.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>EmbeddingGemma retrieval: query and document prompts must stay distinct</title><link>https://retrivium.ai/journal/embeddinggemma-query-document-prompts/</link><guid isPermaLink="true">https://retrivium.ai/journal/embeddinggemma-query-document-prompts/</guid><description>EmbeddingGemma retrieval uses different input roles for a query and a source document, so a shared text-encoding call needs an explicit prompt contract.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Jina embeddings v4: dense and multi-vector outputs are different index contracts</title><link>https://retrivium.ai/journal/jina-v4-dense-multivector-task-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/jina-v4-dense-multivector-task-contract/</guid><description>Jina embeddings v4 can expose dense and multi-vector representations, but those outputs are different index contracts rather than interchangeable serialization options.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron 3.5 Embed: evaluate text and page-image retrieval together</title><link>https://retrivium.ai/journal/nemotron-35-embed-multimodal-retrieval/</link><guid isPermaLink="true">https://retrivium.ai/journal/nemotron-35-embed-multimodal-retrieval/</guid><description>Nemotron 3.5 Embed should be evaluated with matched text and page-image queries, because changing the document representation changes the retrieval problem.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>ColPali document search: migrate to Sentence Transformers without changing scores</title><link>https://retrivium.ai/journal/colpali-sentence-transformers-v6-migration/</link><guid isPermaLink="true">https://retrivium.ai/journal/colpali-sentence-transformers-v6-migration/</guid><description>Migrating ColPali to Sentence Transformers requires a score-parity fixture, because replacing imports alone can silently change query processing and similarity.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>ColPali similarity maps: model focus is not an OCR citation box</title><link>https://retrivium.ai/journal/colpali-similarity-maps-source-grounding/</link><guid isPermaLink="true">https://retrivium.ai/journal/colpali-similarity-maps-source-grounding/</guid><description>ColPali similarity maps explain which image patches match query tokens, but they do not establish an OCR quotation or a verified citation box.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>BEIR qrels: an unjudged passage is not a verified negative</title><link>https://retrivium.ai/journal/beir-qrels-unjudged-retrieval-evaluation/</link><guid isPermaLink="true">https://retrivium.ai/journal/beir-qrels-unjudged-retrieval-evaluation/</guid><description>A missing BEIR relevance judgment does not establish that a passage is a verified negative.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>MTEB and MMTEB: choose tasks before ranking embedding models</title><link>https://retrivium.ai/journal/mteb-mmteb-domain-task-selection/</link><guid isPermaLink="true">https://retrivium.ai/journal/mteb-mmteb-domain-task-selection/</guid><description>MTEB and MMTEB scores become useful only after selecting tasks and languages that match the intended retrieval workload.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Ragas context precision, recall and faithfulness measure different failures</title><link>https://retrivium.ai/journal/ragas-retrieval-faithfulness-metric-boundaries/</link><guid isPermaLink="true">https://retrivium.ai/journal/ragas-retrieval-faithfulness-metric-boundaries/</guid><description>Ragas context precision, context recall and faithfulness answer different questions about a RAG pipeline.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Synthetic RAG test sets: keep document leakage out of the holdout</title><link>https://retrivium.ai/journal/rag-synthetic-testset-leakage-controls/</link><guid isPermaLink="true">https://retrivium.ai/journal/rag-synthetic-testset-leakage-controls/</guid><description>Synthetic RAG questions should be generated after separating source documents into development and holdout groups.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RAG noise sensitivity: test distractors without changing the answer target</title><link>https://retrivium.ai/journal/rag-noise-sensitivity-distractor-tests/</link><guid isPermaLink="true">https://retrivium.ai/journal/rag-noise-sensitivity-distractor-tests/</guid><description>RAG noise tests should change the surrounding context while keeping the question and answer target fixed.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RAG citations: measure support and completeness separately</title><link>https://retrivium.ai/journal/rag-citation-precision-completeness/</link><guid isPermaLink="true">https://retrivium.ai/journal/rag-citation-precision-completeness/</guid><description>Citation quality has separate dimensions: whether attached sources support a claim and whether important claims receive citations at all.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Matryoshka embeddings: truncate and normalize both sides consistently</title><link>https://retrivium.ai/journal/matryoshka-truncation-query-index-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/matryoshka-truncation-query-index-contract/</guid><description>Matryoshka embeddings can be shortened only under the selected model&apos;s supported representation contract, with matching treatment of queries and indexed documents.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron 3.5 Rerank: interpret scores before choosing a relevance threshold</title><link>https://retrivium.ai/journal/nemotron-35-rerank-score-thresholds/</link><guid isPermaLink="true">https://retrivium.ai/journal/nemotron-35-rerank-score-thresholds/</guid><description>Nemotron 3.5 Rerank scores should be interpreted under the checkpoint&apos;s output contract before setting any rejection threshold.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>PDF to Markdown for RAG: fix reading order before indexing</title><link>https://retrivium.ai/journal/pdf-to-markdown-reading-order-rag/</link><guid isPermaLink="true">https://retrivium.ai/journal/pdf-to-markdown-reading-order-rag/</guid><description>PDF-to-Markdown conversion should preserve reading order before a RAG index is built, because perfectly recognized words can still form the wrong document.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Extract PDF tables for RAG: merged cells and repeated headers</title><link>https://retrivium.ai/journal/pdf-table-extraction-merged-cells/</link><guid isPermaLink="true">https://retrivium.ai/journal/pdf-table-extraction-merged-cells/</guid><description>PDF tables need their header relationships and merged-cell scope preserved before they become RAG evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Unstructured PDF parsing: fast, hi_res and ocr_only solve different inputs</title><link>https://retrivium.ai/journal/unstructured-pdf-strategy-selection/</link><guid isPermaLink="true">https://retrivium.ai/journal/unstructured-pdf-strategy-selection/</guid><description>Unstructured PDF strategies should be selected by the document&apos;s actual content and required structure, rather than treating fast, hi_res and ocr_only as quality levels.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>PyMuPDF text extraction: a text layer does not guarantee reading order</title><link>https://retrivium.ai/journal/pymupdf-digital-pdf-text-order/</link><guid isPermaLink="true">https://retrivium.ai/journal/pymupdf-digital-pdf-text-order/</guid><description>A selectable PDF text layer does not guarantee that extracted words follow human reading order.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mixed PDF OCR: avoid duplicating an existing text layer</title><link>https://retrivium.ai/journal/pdf-ocr-overlay-duplicate-text/</link><guid isPermaLink="true">https://retrivium.ai/journal/pdf-ocr-overlay-duplicate-text/</guid><description>Mixed PDFs require an OCR policy that distinguishes existing digital text from text contained only in images.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>PDF citations: keep page coordinates correct after rotation and cropping</title><link>https://retrivium.ai/journal/pdf-citation-coordinates-rotation-crop/</link><guid isPermaLink="true">https://retrivium.ai/journal/pdf-citation-coordinates-rotation-crop/</guid><description>PDF citation boxes must use an explicit coordinate system, especially after page rotation, cropping or rendering.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Documents to Markdown or JSON: preserve evidence provenance for RAG</title><link>https://retrivium.ai/journal/document-markdown-json-provenance/</link><guid isPermaLink="true">https://retrivium.ai/journal/document-markdown-json-provenance/</guid><description>Markdown and structured JSON serve different roles in a document-to-RAG pipeline: readable text is useful for retrieval, while structured provenance is needed to reconstruct evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Excel to RAG: formulas, cached values and merged cells need explicit rules</title><link>https://retrivium.ai/journal/excel-rag-formulas-merged-hidden-cells/</link><guid isPermaLink="true">https://retrivium.ai/journal/excel-rag-formulas-merged-hidden-cells/</guid><description>Excel ingestion for RAG must distinguish formulas, cached values and workbook structure before turning cells into prose.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Web pages for RAG: remove navigation without losing source evidence</title><link>https://retrivium.ai/journal/webpage-clean-text-rag-trafilatura/</link><guid isPermaLink="true">https://retrivium.ai/journal/webpage-clean-text-rag-trafilatura/</guid><description>Clean webpage text for RAG should retain the article&apos;s actual evidence while excluding navigation and unrelated page furniture.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Search meeting recordings: preserve speaker turns and audio evidence</title><link>https://retrivium.ai/journal/meeting-search-transcript-speaker-evidence/</link><guid isPermaLink="true">https://retrivium.ai/journal/meeting-search-transcript-speaker-evidence/</guid><description>Meeting search needs evidence tied to the recording, not just a polished transcript with speaker names attached.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>WhisperX alignment gaps: numbers and symbols may lack word timestamps</title><link>https://retrivium.ai/journal/whisperx-forced-alignment-missing-words/</link><guid isPermaLink="true">https://retrivium.ai/journal/whisperx-forced-alignment-missing-words/</guid><description>WhisperX can leave recognized words without reliable alignment when its alignment model cannot map their characters or sounds.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>pyannote diarization: speaker turns, overlap and identity are different outputs</title><link>https://retrivium.ai/journal/pyannote-exclusive-diarization-speaker-identity/</link><guid isPermaLink="true">https://retrivium.ai/journal/pyannote-exclusive-diarization-speaker-identity/</guid><description>Pyannote exclusive diarization can simplify assigning transcript words to speakers, but it does not identify real people.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Silero VAD before ASR: sample rate and speech boundaries must agree</title><link>https://retrivium.ai/journal/silero-vad-resampling-speech-boundaries/</link><guid isPermaLink="true">https://retrivium.ai/journal/silero-vad-resampling-speech-boundaries/</guid><description>Voice activity detection depends on correct audio sampling and timestamp mapping before it can safely remove silence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>faster-whisper batching: check VAD defaults before comparing transcripts</title><link>https://retrivium.ai/journal/faster-whisper-batched-vad-output-differences/</link><guid isPermaLink="true">https://retrivium.ai/journal/faster-whisper-batched-vad-output-differences/</guid><description>Moving faster-whisper transcription to a batched pipeline can change the preprocessing contract, including voice activity detection defaults.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>WER and CER for speech recognition: normalize text without hiding errors</title><link>https://retrivium.ai/journal/asr-wer-cer-normalization-russian/</link><guid isPermaLink="true">https://retrivium.ai/journal/asr-wer-cer-normalization-russian/</guid><description>WER and CER compare transcripts only under a declared normalization policy, especially for Russian text containing numbers, punctuation and spelling variants.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Transcript cleanup: punctuation must not break word-time alignment</title><link>https://retrivium.ai/journal/asr-punctuation-word-timestamp-integrity/</link><guid isPermaLink="true">https://retrivium.ai/journal/asr-punctuation-word-timestamp-integrity/</guid><description>Punctuation restoration should change transcript presentation without silently rewriting word identity or timing provenance.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Speech to subtitles: validate SRT and WebVTT cue boundaries</title><link>https://retrivium.ai/journal/speech-subtitles-srt-vtt-cue-validation/</link><guid isPermaLink="true">https://retrivium.ai/journal/speech-subtitles-srt-vtt-cue-validation/</guid><description>Subtitle export needs its own validation even when the underlying transcript is correct.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Video retrieval timestamps: use PTS rather than frame-number arithmetic</title><link>https://retrivium.ai/journal/video-vfr-pts-frame-indexing/</link><guid isPermaLink="true">https://retrivium.ai/journal/video-vfr-pts-frame-indexing/</guid><description>Variable-frame-rate video should be indexed with presentation timestamps and time bases rather than assuming that frame number divided by nominal frame rate gives exact time.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Index video keyframes: scene detection versus fixed-rate sampling</title><link>https://retrivium.ai/journal/video-keyframes-scene-detection-indexing/</link><guid isPermaLink="true">https://retrivium.ai/journal/video-keyframes-scene-detection-indexing/</guid><description>Scene detection and periodic frame sampling solve different video-indexing problems, so neither should be adopted as a universal keyframe strategy.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Local video search: join transcript evidence with visual keyframes</title><link>https://retrivium.ai/journal/local-video-search-transcript-keyframes/</link><guid isPermaLink="true">https://retrivium.ai/journal/local-video-search-transcript-keyframes/</guid><description>Local video search should join transcript spans and selected frames through source time, while preserving each modality&apos;s evidence separately.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Russian keyword retrieval: stemming must not destroy exact identifiers</title><link>https://retrivium.ai/journal/russian-bm25-analyzer-exact-identifiers/</link><guid isPermaLink="true">https://retrivium.ai/journal/russian-bm25-analyzer-exact-identifiers/</guid><description>Russian BM25 search should separate linguistic matching from exact identifier matching rather than forcing both into one analyzed field.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Elasticsearch passage retrieval: nested kNN and supporting inner hits</title><link>https://retrivium.ai/journal/elasticsearch-nested-passage-inner-hits/</link><guid isPermaLink="true">https://retrivium.ai/journal/elasticsearch-nested-passage-inner-hits/</guid><description>Elasticsearch nested passage retrieval should return the passage that produced a document&apos;s match, not only the parent document.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Neural sparse search in OpenSearch: token weights are not ordinary BM25</title><link>https://retrivium.ai/journal/opensearch-neural-sparse-vocabulary-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/opensearch-neural-sparse-vocabulary-contract/</guid><description>Learned sparse retrieval requires matching document and query vocabularies, not merely accepting arrays of token identifiers and weights.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qdrant sparse IDF: corpus changes can alter query scoring</title><link>https://retrivium.ai/journal/qdrant-sparse-idf-corpus-updates/</link><guid isPermaLink="true">https://retrivium.ai/journal/qdrant-sparse-idf-corpus-updates/</guid><description>Qdrant sparse IDF scores can change when the indexed corpus changes even if the query text and stored document vectors remain unchanged.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Milvus text matching versus BM25: filtering is not relevance ranking</title><link>https://retrivium.ai/journal/milvus-text-match-bm25-filter-ranking/</link><guid isPermaLink="true">https://retrivium.ai/journal/milvus-text-match-bm25-filter-ranking/</guid><description>Milvus TEXT_MATCH filters documents by analyzed terms, while a BM25 Function supplies a ranked full-text retrieval path.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Update RAG documents without leaving stale chunks and citations</title><link>https://retrivium.ai/journal/rag-document-updates-stale-chunk-citations/</link><guid isPermaLink="true">https://retrivium.ai/journal/rag-document-updates-stale-chunk-citations/</guid><description>Version RAG documents and their chunks explicitly, remove superseded search evidence, and retain citation provenance without confusing historical and active content.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>ColBERT PLAID: index compression and candidate pruning are separate checks</title><link>https://retrivium.ai/journal/colbert-plaid-late-interaction-index/</link><guid isPermaLink="true">https://retrivium.ai/journal/colbert-plaid-late-interaction-index/</guid><description>Separate ColBERTv2 residual compression from PLAID candidate pruning, then evaluate index footprint, candidate recall and final late-interaction ranking independently.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LMCache vs vLLM prefix caching: choose the cache boundary</title><link>https://retrivium.ai/journal/lmcache-vs-vllm-prefix-caching/</link><guid isPermaLink="true">https://retrivium.ai/journal/lmcache-vs-vllm-prefix-caching/</guid><description>Compare engine-local prefix reuse with an external KV cache, including native vLLM offloading, cache lifetime and the cost of moving cached blocks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LMCache CPU offload: size a reusable KV working set</title><link>https://retrivium.ai/journal/lmcache-cpu-kv-offload/</link><guid isPermaLink="true">https://retrivium.ai/journal/lmcache-cpu-kv-offload/</guid><description>Plan CPU memory for reusable KV blocks, distinguish cache offload from weight offload, and test transfer pressure alongside the inference workload.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Persistent KV cache invalidation: when a prefix stops being reusable</title><link>https://retrivium.ai/journal/persistent-kv-cache-invalidation/</link><guid isPermaLink="true">https://retrivium.ai/journal/persistent-kv-cache-invalidation/</guid><description>Define cache namespaces across weight revisions, tokenizers, layouts and tenant boundaries before reusing KV blocks after an inference deployment changes.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CacheBlend for RAG: reuse document chunks beyond an exact prefix</title><link>https://retrivium.ai/journal/cacheblend-rag-non-prefix-reuse/</link><guid isPermaLink="true">https://retrivium.ai/journal/cacheblend-rag-non-prefix-reuse/</guid><description>Understand selective recomputation in CacheBlend, why reordered retrieved chunks challenge ordinary prefix reuse, and how to evaluate answer quality.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>FP8 KV cache: precision, calibration and long-context quality</title><link>https://retrivium.ai/journal/fp8-kv-cache-calibration-quality/</link><guid isPermaLink="true">https://retrivium.ai/journal/fp8-kv-cache-calibration-quality/</guid><description>Separate KV-cache precision from weight quantization, verify backend and scale support, and evaluate long-context accuracy before allocating more concurrency.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Dynamo vs vLLM: orchestration and inference are different layers</title><link>https://retrivium.ai/journal/nvidia-dynamo-vs-vllm-serving-layer/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-dynamo-vs-vllm-serving-layer/</guid><description>Place Dynamo routing, planning and cache movement around an inference engine, and identify when a simpler vLLM service is sufficient for the workload.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Dynamo KV-aware routing: balance cached context against queueing</title><link>https://retrivium.ai/journal/dynamo-kv-aware-routing-cache-queue/</link><guid isPermaLink="true">https://retrivium.ai/journal/dynamo-kv-aware-routing-cache-queue/</guid><description>Evaluate cache-aware worker selection using prefix locality, queue delay and stale state, without confusing it with application-level model routing.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Dynamo KVBM: budget GPU, host and storage tiers separately</title><link>https://retrivium.ai/journal/dynamo-kvbm-memory-tiers/</link><guid isPermaLink="true">https://retrivium.ai/journal/dynamo-kvbm-memory-tiers/</guid><description>Read the KV Block Manager as a memory hierarchy, including block movement, pinned host capacity, storage latency and version-specific integration limits.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM prefill-decode disaggregation: when separate pools help</title><link>https://retrivium.ai/journal/vllm-prefill-decode-disaggregation-architecture/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-prefill-decode-disaggregation-architecture/</guid><description>Evaluate separate prefill and decode workers through phase interference, KV transfer, replica balance and useful completions under latency constraints.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NIXL vs NCCL: KV movement and collective communication</title><link>https://retrivium.ai/journal/nixl-vs-nccl-data-movement/</link><guid isPermaLink="true">https://retrivium.ai/journal/nixl-vs-nccl-data-movement/</guid><description>Distinguish a heterogeneous data-movement layer from GPU communication primitives, and map their complementary roles in distributed LLM serving.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LMCache vs Mooncake: compare the component, not just the project</title><link>https://retrivium.ai/journal/lmcache-vs-mooncake-kv-cache/</link><guid isPermaLink="true">https://retrivium.ai/journal/lmcache-vs-mooncake-kv-cache/</guid><description>Compare LMCache integration with Mooncake transfer and storage components, including overlaps, composable paths and workload-specific evaluation criteria.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RoCE vs InfiniBand for LLM serving: qualify the full fabric</title><link>https://retrivium.ai/journal/roce-vs-infiniband-llm-serving/</link><guid isPermaLink="true">https://retrivium.ai/journal/roce-vs-infiniband-llm-serving/</guid><description>Compare RDMA over Ethernet with InfiniBand through adapters, switches, congestion and real inference transfers, without treating link speed as an SLO.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Expert parallel vs tensor parallel for MoE inference</title><link>https://retrivium.ai/journal/expert-parallel-vs-tensor-parallel-moe/</link><guid isPermaLink="true">https://retrivium.ai/journal/expert-parallel-vs-tensor-parallel-moe/</guid><description>Separate expert placement from tensor sharding, map attention and MoE groups, and test dispatch imbalance before choosing a multi-GPU topology.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Data parallel vs tensor parallel: replicas or a split model?</title><link>https://retrivium.ai/journal/data-parallel-vs-tensor-parallel-serving/</link><guid isPermaLink="true">https://retrivium.ai/journal/data-parallel-vs-tensor-parallel-serving/</guid><description>Choose between independent serving replicas and tensor-sharded execution using model fit, cache locality, failure boundaries and measured communication.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>FlashAttention vs PagedAttention: different attention problems</title><link>https://retrivium.ai/journal/flashattention-vs-pagedattention/</link><guid isPermaLink="true">https://retrivium.ai/journal/flashattention-vs-pagedattention/</guid><description>Distinguish efficient attention computation from paged KV memory management, and understand why a serving backend can combine ideas from both.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>FlashInfer vs FlashAttention: compare the actual kernel path</title><link>https://retrivium.ai/journal/flashinfer-vs-flashattention-kernel-stack/</link><guid isPermaLink="true">https://retrivium.ai/journal/flashinfer-vs-flashattention-kernel-stack/</guid><description>Place FlashInfer kernel collections and FlashAttention implementations within a serving backend, then compare supported operations rather than brand names.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CUDA Graphs vs torch.compile: replay and compilation can coexist</title><link>https://retrivium.ai/journal/cuda-graphs-vs-torch-compile/</link><guid isPermaLink="true">https://retrivium.ai/journal/cuda-graphs-vs-torch-compile/</guid><description>Separate kernel replay from graph compilation, compare startup and steady-state costs, and test shape diversity before selecting an inference optimization.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LLM goodput vs tokens per second: count requests meeting the objective</title><link>https://retrivium.ai/journal/llm-goodput-vs-tokens-per-second/</link><guid isPermaLink="true">https://retrivium.ai/journal/llm-goodput-vs-tokens-per-second/</guid><description>Define useful serving capacity through completed requests meeting first-token and token-pacing limits, then keep that measure separate from raw throughput.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SGLang HiCache vs RadixAttention: a hierarchy around prefix reuse</title><link>https://retrivium.ai/journal/sglang-hicache-vs-radixattention/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-hicache-vs-radixattention/</guid><description>Separate radix-based prefix reuse from the host and storage hierarchy, then evaluate cache movement, model-state compatibility and working-set churn.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Gateway API Inference Extension vs ordinary load balancing</title><link>https://retrivium.ai/journal/gateway-api-inference-extension-vs-load-balancer/</link><guid isPermaLink="true">https://retrivium.ai/journal/gateway-api-inference-extension-vs-load-balancer/</guid><description>Understand InferencePool and endpoint picking for LLM workers, including compatibility, stale metrics and the boundary between routing and model execution.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How digitizing planning records prepared the way for PlanAssist</title><link>https://retrivium.ai/retrospectives/planassist-digitization-before-assistance/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/planassist-digitization-before-assistance/</guid><description>How the earlier Extract programme and planning-data digitization prepared the context for PlanAssist, with different roles for records and recommendations.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why PlanAssist separates assessment time from planning outcomes</title><link>https://retrivium.ai/retrospectives/planassist-assessment-time-vs-outcome/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/planassist-assessment-time-vs-outcome/</guid><description>Why the PlanAssist pilot calls for separate measures of officer assessment time, total application duration and the quality of the final decision.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How local policy became the scaling test for public-sector AI</title><link>https://retrivium.ai/retrospectives/planassist-local-policy-portability/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/planassist-local-policy-portability/</guid><description>How PlanAssist’s expansion makes local policy, record quality and qualified review the practical test of scaling an administrative AI assistant.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Large4 weights: why the October29 checkpoint is not merely the preview download</title><link>https://retrivium.ai/retrospectives/large4-improved-weights-not-preview-snapshot/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/large4-improved-weights-not-preview-snapshot/</guid><description>The Large4 weight release is significant because it publishes an improved artifact after the earlier preview, rather than merely exposing a download of the same observed service.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Large4 open weights: the published model-as-a-service license boundary</title><link>https://retrivium.ai/retrospectives/large4-open-weight-maas-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/large4-open-weight-maas-boundary/</guid><description>Mistral Large4&apos;s open-weight release uses a modified license with a model-as-a-service condition, so it should not be archived under an ordinary unrestricted MIT label.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mistral Large 4 (Le Chonk) is now open weight: internal use and model-as-a-service</title><link>https://retrivium.ai/retrospectives/retro-mistral-large4-weights-maas-license/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-large4-weights-maas-license/</guid><description>For Mistral Large4, an internal application and a model-serving offering are different deployment descriptions, so an inventory should identify the actual relationship before interpreting release terms.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mistral Large 4 (Le Chonk) is now open weight: additional post-training after a preview</title><link>https://retrivium.ai/retrospectives/retro-mistral-large4-weights-checkpoint-delta/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-large4-weights-checkpoint-delta/</guid><description>Mistral Large4&apos;s published weights followed additional post-training, so an earlier preview evaluation cannot be treated as direct acceptance of the later artifact.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Carbon shortened the evaluation window after Argon GA</title><link>https://retrivium.ai/retrospectives/carbon-after-argon-evaluation-window/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/carbon-after-argon-evaluation-window/</guid><description>How Carbon&apos;s announcement soon after Argon GA illustrates the need for evaluation cutoffs and explicit reasons to reopen a model-selection study.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A trusted-partner announcement is not a deployable default</title><link>https://retrivium.ai/retrospectives/carbon-trusted-access-procurement/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/carbon-trusted-access-procurement/</guid><description>Why Carbon&apos;s trusted-partner announcement belongs in conditional architecture planning rather than an unverified current deployment default.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Carbon&apos;s cyber evidence spans different task boundaries</title><link>https://retrivium.ai/retrospectives/carbon-cyber-benchmark-boundaries/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/carbon-cyber-benchmark-boundaries/</guid><description>How to read Carbon&apos;s discovery, validation and patching evidence as different task outcomes rather than one end-to-end security guarantee.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Persistent Carbon work needs honest blocker handling</title><link>https://retrivium.ai/retrospectives/carbon-long-horizon-avoid-shortcuts/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/carbon-long-horizon-avoid-shortcuts/</guid><description>Why Carbon&apos;s long-work claims should be tested through useful partial artifacts, explicit blocked dependencies and honest final limitations.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why input-token price stopped being the whole routing decision</title><link>https://retrivium.ai/retrospectives/retro-openrouter-effective-routing-cost/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-effective-routing-cost/</guid><description>OpenRouter’s October routing rebuild followed earlier provider-quality work. The useful comparison is billed usage plus execution consequences, not a nominal rate alone.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What the new OpenRouter router leaves under caller control</title><link>https://retrivium.ai/retrospectives/retro-openrouter-routing-explicit-constraints/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-routing-explicit-constraints/</guid><description>The October router separates provider eligibility from provider selection. Ordered routes, explicit sorts and candidate filters have different effects.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How routing signals change the incentive to add reliable capacity</title><link>https://retrivium.ai/retrospectives/retro-openrouter-provider-incentives/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-provider-incentives/</guid><description>OpenRouter’s routing rebuild connects provider selection to observed service. Installed GPUs, usable route capacity and allocated traffic remain different quantities.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron Transcribe and Granaryv2: a speech model plus its adaptation path</title><link>https://retrivium.ai/retrospectives/nemotron-transcribe-granary-model-data-split/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/nemotron-transcribe-granary-model-data-split/</guid><description>Nemotron Transcribe and Granaryv2 form a model-and-adaptation release, not just a new transcription endpoint.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron3.5 Transcribe and Granaryv2: held-out speakers and adaptation claims</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-transcribe-speaker-holdout/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-transcribe-speaker-holdout/</guid><description>NemotronTranscribe&apos;s adaptation workflow needs speaker-separated acceptance when the claim concerns unfamiliar voices, because familiar-speaker success can overstate generalization.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron3.5 Transcribe and Granaryv2: prompted vocabulary and faithful transcription</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-transcribe-prompted-asr/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-transcribe-prompted-asr/</guid><description>NemotronTranscribe&apos;s prompted vocabulary can help a recognizer consider rare terms, but it should not make supplied words count as evidence that they were actually spoken.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron3.5 Transcribe and Granaryv2: open data workflow and reproducibility</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-transcribe-data-recipe/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-transcribe-data-recipe/</guid><description>Granary&apos;s open workflow and NemotronTranscribe&apos;s available model are different reproducibility artifacts, so obtaining one does not automatically reproduce the other&apos;s full training history.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Meta Helios testing versus a six-gigawatt agreement</title><link>https://retrivium.ai/retrospectives/retro-meta-helios-testing-vs-capacity/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-meta-helios-testing-vs-capacity/</guid><description>Meta’s initial Helios installation and testing marks deployment progress. The February commitment, platform release and usable application capacity remain separate milestones.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why Meta’s AMD milestone spans ROCm, CPUs, and networking</title><link>https://retrivium.ai/retrospectives/retro-meta-amd-co-design-software/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-meta-amd-co-design-software/</guid><description>The AMD–Meta chronology makes co-design an interface question. A system-level result depends on qualified combinations, workload feedback and the operator’s environment.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Day-zero support is not the end of infrastructure validation</title><link>https://retrivium.ai/retrospectives/retro-meta-day-zero-support-validation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-meta-day-zero-support-validation/</guid><description>Day-zero model support and rack acceptance validate different layers. The Helios chronology shows why software readiness cannot stand in for system testing.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Installed, tested and accepted are separate Helios milestones</title><link>https://retrivium.ai/retrospectives/retro-meta-helios-acceptance-ladder/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-meta-helios-acceptance-ladder/</guid><description>Helios testing makes acceptance a scoped decision about a named configuration. A useful record preserves workload, observed result, exceptions and the decision owner.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why a GPU cloud’s backbone matters for model and dataset movement</title><link>https://retrivium.ai/retrospectives/retro-global-ai-backbone-model-artifacts/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-global-ai-backbone-model-artifacts/</guid><description>CoreWeave’s backbone expands artifact-staging options across locations. Useful deployment still requires a coherent version, validated arrival and a separate activation step.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A network point of presence is not a new GPU region</title><link>https://retrivium.ai/retrospectives/retro-network-pop-is-not-compute-region/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-network-pop-is-not-compute-region/</guid><description>CoreWeave’s network and facility announcements have different clocks. A new PoP describes connectivity; GPU service and customer allocation require separate evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Backbone encryption and the remaining trust boundaries of an AI cloud</title><link>https://retrivium.ai/retrospectives/retro-ai-backbone-encryption-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-ai-backbone-encryption-boundary/</guid><description>CoreWeave’s MACsec claim concerns network-path protection. Application termination, plaintext access, retention and runtime integrity remain separate trust questions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Moving model artifacts and serving tokens need different network evidence</title><link>https://retrivium.ai/retrospectives/retro-ai-backbone-artifact-inference/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-ai-backbone-artifact-inference/</guid><description>CoreWeave’s backbone can affect preparation and live response through different paths. A measurement needs explicit start and end events before it can explain either benefit.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>ECS moves from whole-GPU assignment to shared scheduling</title><link>https://retrivium.ai/retrospectives/retro-ecs-gpu-granularity-mps/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-ecs-gpu-granularity-mps/</guid><description>ECS GPU sharing introduces per-task budgets on a shared device. Finer allocation enables packing choices, while workload fit and useful performance still need application evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>ECS MPS limits versus isolation: different questions</title><link>https://retrivium.ai/retrospectives/retro-ecs-mps-memory-compute-isolation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-ecs-mps-memory-compute-isolation/</guid><description>ECS GPU budgets describe allocation, while isolation requires a separate property and mechanism. The MPS announcement does not identify its daemon interface version or equate MPS with MIG.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why managed MPS daemon recovery changes operational ownership</title><link>https://retrivium.ai/retrospectives/retro-managed-mps-daemon-lifecycle/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-managed-mps-daemon-lifecycle/</guid><description>ECS sharing spans two deployment modes, but the announced daemon monitoring and automatic instance replacement are scoped to Managed Instances. Recovery ownership must preserve that distinction.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Shared GPU service adds a daemon lifecycle to the task lifecycle</title><link>https://retrivium.ai/retrospectives/retro-ecs-mps-daemon-lifecycle/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-ecs-mps-daemon-lifecycle/</guid><description>ECS shared-GPU recovery spans task, daemon and host lifecycles. Moving a task to healthy capacity is distinct from preserving its application and in-flight GPU state.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>An OCI TPU announcement is not an allocatable TPU region</title><link>https://retrivium.ai/retrospectives/retro-oci-tpu-announcement-availability/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-oci-tpu-announcement-availability/</guid><description>Google and Oracle planned OCI TPU capacity from 2027 with a multiyear ramp. The October announcement is a distribution milestone rather than current inventory.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why bringing an accelerator to the data differs from connecting two clouds</title><link>https://retrivium.ai/retrospectives/retro-oci-tpu-data-proximity/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-oci-tpu-data-proximity/</guid><description>The OCI TPU plan proposes accelerator execution inside OCI after an earlier multicloud interconnect partnership. Data proximity remains a workload-specific question.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>TPU software portability and datacenter readiness run on different clocks</title><link>https://retrivium.ai/retrospectives/retro-oci-tpu-software-physical/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-oci-tpu-software-physical/</guid><description>OCI TPU software adoption and physical delivery have different dependencies. Familiar tooling can reduce porting work without making future capacity immediately usable.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Multiple accelerators in one cloud do not eliminate workload qualification</title><link>https://retrivium.ai/retrospectives/retro-oci-tpu-architecture-choice/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-oci-tpu-architecture-choice/</guid><description>Adding TPUs to OCI would broaden architecture choice from 2027. Model support, operational fit and cost per acceptable result still require workload qualification.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CoreWeave Denmark: Why most of 22.5 MW is not the same as all of 22.5 MW</title><link>https://retrivium.ai/retrospectives/retro-denmark-majority-online/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-denmark-majority-online/</guid><description>CoreWeave’s Denmark update followed future regional expansion plans. Why reporting most of a planned 22.5 MW online requires preserving the commissioning fraction.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CoreWeave Denmark: A colocation operator and a GPU cloud deliver different parts of capacity</title><link>https://retrivium.ai/retrospectives/retro-denmark-colocation-cloud-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-denmark-colocation-cloud-boundary/</guid><description>CoreWeave’s deployment at atNorth DEN01 followed platform and regional expansion milestones. Why colocation capacity and a GPU cloud are complementary deliverables.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CoreWeave Denmark: A heat-reuse agreement is not a per-token energy measurement</title><link>https://retrivium.ai/retrospectives/retro-denmark-heat-reuse-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-denmark-heat-reuse-boundary/</guid><description>CoreWeave’s Denmark announcement connects GPU infrastructure with district heating. Why a heat-reuse agreement is a new system boundary rather than a per-token energy result.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CoreWeave Denmark: A local GPU site and a global backbone solve different placement problems</title><link>https://retrivium.ai/retrospectives/retro-denmark-local-global-network/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-denmark-local-global-network/</guid><description>CoreWeave announced Danish compute capacity alongside a network backbone. How earlier regional plans lead to two different placement questions: local requests and inter-site movement.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM3: why one backbone produced several modality contracts</title><link>https://retrivium.ai/retrospectives/lfm3-shared-backbone-retrospective/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/lfm3-shared-backbone-retrospective/</guid><description>The LFM3 announcement matters because a shared model backbone does not produce a shared application interface.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM3 announcement versus runtime support: what shipped together</title><link>https://retrivium.ai/retrospectives/lfm3-announcement-runtime-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/lfm3-announcement-runtime-boundary/</guid><description>LFM3&apos;s family announcement and a runtime&apos;s support record answer different availability questions, especially when several modality contracts share one backbone.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing LFM3: checkpoint publication and license identity</title><link>https://retrivium.ai/retrospectives/retro-liquid-lfm3-license-artifact/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-lfm3-license-artifact/</guid><description>LFM3&apos;s shared backbone does not replace an artifact-specific license record, because technical lineage and distribution permissions describe different relationships.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing LFM3: decision outputs versus generated answers</title><link>https://retrivium.ai/retrospectives/retro-liquid-lfm3-decision-interface/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-lfm3-decision-interface/</guid><description>LFM3&apos;s decision and conversational variants need different response contracts, even when a shared backbone makes them appear to be interchangeable family members.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why the sleep framework makes memory a lifecycle problem</title><link>https://retrivium.ai/retrospectives/sleep-framework-memory-lifecycle/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sleep-framework-memory-lifecycle/</guid><description>A retrospective on the sleep framework, persistent adaptation and why useful model memory needs admission, consolidation and deletion rules.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How forgetting became the real test of continual learning</title><link>https://retrivium.ai/retrospectives/sleep-framework-evaluation-forgetting/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sleep-framework-evaluation-forgetting/</guid><description>How continual learning reached a harder evaluation question: preserving old capabilities while adding new ones, beyond a fresh-task score.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why a learning model needs a version boundary in serving</title><link>https://retrivium.ai/retrospectives/sleep-framework-serving-version-boundaries/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sleep-framework-serving-version-boundaries/</guid><description>A retrospective on continual learning and inference operations: checkpoint identity, cache isolation and the boundary between learning and serving.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How retrieval and weight updates reached different memory roles</title><link>https://retrivium.ai/retrospectives/sleep-framework-rag-weight-updates/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sleep-framework-rag-weight-updates/</guid><description>How the sleep-framework discussion clarifies different jobs for retrieval, context and persistent model adaptation, with a counterfactual test.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Terra 6.1 and the economics of repeated visual actions</title><link>https://retrivium.ai/retrospectives/terra61-visual-action-economics/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/terra61-visual-action-economics/</guid><description>Terra expanded efficient computer-use options, but completed visual tasks still include observation, browser execution, waiting and recovery costs.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What the Terra factuality claim leaves for application tests</title><link>https://retrivium.ai/retrospectives/terra61-factuality-evaluation-slices/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/terra61-factuality-evaluation-slices/</guid><description>Terra factuality claims motivate a trial; review entity identity, values, qualifications and source revisions separately on the application corpus.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why better visual reasoning still needs screen-state verification</title><link>https://retrivium.ai/retrospectives/terra61-screen-state-verification/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/terra61-screen-state-verification/</guid><description>Terra can interpret a screenshot accurately while a stale screen still causes the wrong action; separate observation quality from state freshness.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Clearer Terra writing changes the human review interface</title><link>https://retrivium.ai/retrospectives/terra61-writing-and-agent-reviews/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/terra61-writing-and-agent-reviews/</guid><description>Terra pairs clearer writing with computer use; review reports for retained outcome evidence and uncertainty rather than polish alone.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SGLang isolation disclosure: when a rejected request still crossed a handoff</title><link>https://retrivium.ai/retrospectives/sglang-rejection-handoff-security-history/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sglang-rejection-handoff-security-history/</guid><description>The SGLang isolation disclosure shows why rejecting a request must settle its resource lifecycle, rather than merely produce an error response.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SGLang isolation disclosure: configured context is not processable capacity</title><link>https://retrivium.ai/retrospectives/retro-sglang-isolation-disclosure-admission/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-sglang-isolation-disclosure-admission/</guid><description>The SGLang disclosure in historical context: how longer context and distributed serving exposed a gap between configuration, admission and worker handoff.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SGLang cache lifetime: what a transfer acknowledgment must actually prove</title><link>https://retrivium.ai/retrospectives/retro-sglang-isolation-disclosure-lifetime-acks/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-sglang-isolation-disclosure-lifetime-acks/</guid><description>A retrospective on the SGLang isolation update, asynchronous cache ownership and why a control-plane acknowledgment is not automatically proof of safe reuse.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Kimi K3.1 Pro: product rollout and the still-future weight promise</title><link>https://retrivium.ai/retrospectives/kimi31-pro-launch-before-weight-date/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/kimi31-pro-launch-before-weight-date/</guid><description>Kimi K3.1 Pro&apos;s rollout and its promised weight publication are separate historical facts at the review cutoff.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>BoltE4B: Gemma lineage inside the Nemotron release family</title><link>https://retrivium.ai/retrospectives/bolt-e4b-gemma-lineage-not-moe-scale/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/bolt-e4b-gemma-lineage-not-moe-scale/</guid><description>BoltE4B&apos;s release shows why product-family naming cannot substitute for model lineage.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>K3.1 Pro Series is live: thinking-only access and client migration</title><link>https://retrivium.ai/retrospectives/retro-kimi31-pro-thinking-only/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-kimi31-pro-thinking-only/</guid><description>Kimi K3.1Pro&apos;s thinking-only access requires a compatible client request, so rejecting an unsupported reasoning-mode option is not evidence that the model cannot perform the task.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>K3.1 Pro Series is live: future weights at the review cutoff</title><link>https://retrivium.ai/retrospectives/retro-kimi31-pro-weight-promise/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-kimi31-pro-weight-promise/</guid><description>Kimi&apos;s commitment to publish K3.1Pro weights by November 4 remained a future statement at the November 3 review cutoff, so it cannot be recorded as completed availability.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>K3.1 Pro Series is live: session transitions across model generations</title><link>https://retrivium.ai/retrospectives/retro-kimi31-pro-session-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-kimi31-pro-session-boundary/</guid><description>Kimi K3.1Pro&apos;s session-transition guidance makes migration a state decision, because carrying an old conversation into a new model changes the effective evaluation input.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Nemotron3.5 Bolt E4B 4GB: memory branding and actual session state</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-bolt-e4b-footprint-name/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-bolt-e4b-footprint-name/</guid><description>NemotronBoltE4B&apos;s 4GB branding describes a targeted footprint, not a guarantee that arbitrary context, concurrent sessions and every application component fit inside that total.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Nemotron3.5 Bolt E4B 4GB: speech-ready output and tool arguments</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-bolt-e4b-conversational-mode/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-bolt-e4b-conversational-mode/</guid><description>NemotronBoltE4B&apos;s concise conversational role does not make spoken-friendly wording and machine tool arguments interchangeable outputs, even when one specialist produces both in an application.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Nemotron3.5 Bolt E4B 4GB: base-model lineage and post-trained behavior</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-bolt-e4b-gemma-adaptation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-bolt-e4b-gemma-adaptation/</guid><description>NemotronBoltE4B&apos;s Gemma lineage and Nemotron post-training describe complementary parts of its identity, not a reason to assume identical prompts and behaviour across product families.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why a bounded answer needed a different API</title><link>https://retrivium.ai/retrospectives/decisions-ga-bounded-answer-contract/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/decisions-ga-bounded-answer-contract/</guid><description>Decisions GA made bounded outputs an explicit API contract; category design, application mapping and unresolved cases still require separate acceptance checks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Typed decisions do not establish the right rejection policy</title><link>https://retrivium.ai/retrospectives/decisions-ga-rejection-policy/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/decisions-ga-rejection-policy/</guid><description>Decisions GA narrows output syntax, while rejection and escalation still need labeled evidence, explicit unresolved cases and a versioned action policy.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>More questions per request change failure coupling</title><link>https://retrivium.ai/retrospectives/decisions-ga-batch-question-coupling/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/decisions-ga-batch-question-coupling/</guid><description>Decisions GA doubled the question limit; larger batches still need per-question evidence scope, result identity and an observed recovery contract.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Decisions and GPT-Live separate dialogue from action selection</title><link>https://retrivium.ai/retrospectives/decisions-ga-voice-action-separation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/decisions-ga-voice-action-separation/</guid><description>Decisions GA joined bounded inference with GPT-Live; preserve request identity so a delayed choice cannot silently act on an outdated spoken intention.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Google Agent Compute Engine: Why the model server and the agent’s computer need different lifecycles</title><link>https://retrivium.ai/retrospectives/retro-agent-compute-brain-hands/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-agent-compute-brain-hands/</guid><description>Google’s Agent Compute Engine follows inference routing and confidential-computing milestones. Why model serving and an agent’s working computer need different lifecycles.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Google Agent Compute Engine: Pausing an agent is a state problem before it is a density claim</title><link>https://retrivium.ai/retrospectives/retro-agent-compute-pause-state/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-agent-compute-pause-state/</guid><description>Google’s Agent Compute Engine announcement follows earlier routing and trust primitives. Why checkpointing an idle agent requires coherent state before it supports efficiency claims.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Google Agent Compute Engine: Keeping secrets outside a sandbox changes the failure boundary</title><link>https://retrivium.ai/retrospectives/retro-agent-compute-egress-secrets/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-agent-compute-egress-secrets/</guid><description>Google’s Agent Compute Engine keeps long-lived credentials outside the sandbox. How earlier confidential-computing work leads to a different boundary around authorized actions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Google Agent Compute Engine: Internal deployment and external preview are different release states</title><link>https://retrivium.ai/retrospectives/retro-agent-compute-internal-preview/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-agent-compute-internal-preview/</guid><description>Google’s Agent Compute Engine announcement describes internal use and a future external preview. How earlier infrastructure milestones explain the difference between those release states.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How forest AI moved from counting trees to understanding land use</title><link>https://retrivium.ai/retrospectives/forest-ai-land-cover-to-land-use/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/forest-ai-land-cover-to-land-use/</guid><description>How the path to AI forest-type maps exposed the difference between observing tree cover and interpreting the land use behind a green pixel.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why forest mapping needed better labels as much as finer pixels</title><link>https://retrivium.ai/retrospectives/forest-ai-labels-before-resolution/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/forest-ai-labels-before-resolution/</guid><description>Why AI forest mapping requires trustworthy reference labels alongside high-resolution observations, and how to separate those contributions in evaluation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How changing forest maps exposed the need for temporal comparability</title><link>https://retrivium.ai/retrospectives/forest-ai-temporal-comparability/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/forest-ai-temporal-comparability/</guid><description>How AI forest maps reveal a temporal evaluation problem: distinguishing actual landscape change from changes in categories, observations and model versions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Duet made attention selection part of the agent product</title><link>https://retrivium.ai/retrospectives/duet-proactive-attention-policy/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/duet-proactive-attention-policy/</guid><description>Why Claude Duet&apos;s proactive preview adds an attention-selection problem, with justified silence and notification tested separately from source access.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A Duet preview announcement is not broad availability</title><link>https://retrivium.ai/retrospectives/duet-preview-access-vs-capability/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/duet-preview-access-vs-capability/</guid><description>How to read Claude Duet&apos;s October research preview without confusing waitlisted access, product capability and later announcement updates.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Background Duet work needs evidence-bearing completion signals</title><link>https://retrivium.ai/retrospectives/duet-background-work-completion-signals/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/duet-background-work-completion-signals/</guid><description>Why Duet background notifications need to distinguish discovery, preparation, attempts and supported completion through inspectable outcomes.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Connected business actions require explicit transaction intent</title><link>https://retrivium.ai/retrospectives/duet-actions-vs-financial-intent/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/duet-actions-vs-financial-intent/</guid><description>How Claude Duet&apos;s connected-business direction separates reversible preparation, a stable approved proposal and evidence of the eventual operation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why AI cloud trust spans keys, support access, and runtime</title><link>https://retrivium.ai/retrospectives/retro-zero-trust-key-authority-runtime/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-zero-trust-key-authority-runtime/</guid><description>CoreWeave’s framework links customer key authority, support approval and runtime verification. Their value depends on the decision path connecting protected data to authorized execution.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Confidential compute: announced extension versus deployed coverage</title><link>https://retrivium.ai/retrospectives/retro-confidential-compute-announced-versus-deployed/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-confidential-compute-announced-versus-deployed/</guid><description>CoreWeave’s confidential-computing extension has named hardware, intended timing and an initial deployment scope. Those dimensions must remain separate from completed workload coverage.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How to read a zero-trust framework without turning it into a guarantee</title><link>https://retrivium.ai/retrospectives/retro-zero-trust-ai-framework-verification/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-zero-trust-ai-framework-verification/</guid><description>CoreWeave’s framework groups several trust boundaries. Technical mechanisms, operating policies and future extensions need different evidence before supporting a workload-specific conclusion.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Support access and runtime trust are separate zero-trust layers</title><link>https://retrivium.ai/retrospectives/retro-zero-trust-support-runtime-separation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-zero-trust-support-runtime-separation/</guid><description>Support approval and runtime verification govern different decisions. Maintenance authority, environment evidence and workload continuation should remain separate but connected records.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>From Confidential G4 preview to a documented GA boundary</title><link>https://retrivium.ai/retrospectives/retro-confidential-g4-preview-ga/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-confidential-g4-preview-ga/</guid><description>Confidential G4 moved from preview to GA with a stated hardware and zone scope. Related Confidential Space integration retained a separate rollout status.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why attestation belongs before release of model secrets</title><link>https://retrivium.ai/retrospectives/retro-confidential-g4-attestation-release/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-confidential-g4-attestation-release/</guid><description>Remote attestation can condition model-secret release on environment evidence. Confidential G4 GA does not remove the need for key policy or application authorization.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Thirty-six zones are not thirty-six independent cloud regions</title><link>https://retrivium.ai/retrospectives/retro-confidential-g4-zones-regions/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-confidential-g4-zones-regions/</guid><description>Confidential G4 GA reported 36 zones. Preserving that unit avoids exaggerating regional diversity or implying account-level capacity guarantees.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Confidential G4 and Confidential Space had different rollout states</title><link>https://retrivium.ai/retrospectives/retro-confidential-g4-space-rollout/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-confidential-g4-space-rollout/</guid><description>Confidential G4 reached GA while Confidential Space integration had a separate coming-weeks rollout. Component maturity and composition maturity require distinct evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A live-network AI-RAN call does not mean a nationwide deployment</title><link>https://retrivium.ai/retrospectives/retro-airan-pilot-commercial-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-airan-pilot-commercial-boundary/</guid><description>The AI-RAN update reported a live-network call, field trials and future pilots with different scopes. Those milestones do not establish a nationwide deployment.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radio processing and edge inference share hardware but not deadlines</title><link>https://retrivium.ai/retrospectives/retro-airan-inference-radio-coexistence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-airan-inference-radio-coexistence/</guid><description>AI-RAN combines radio and AI on shared infrastructure, but their timing and isolation needs differ. Apparent spare compute is not automatically an inference-service commitment.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>New ARC configurations complicate the meaning of network edge</title><link>https://retrivium.ai/retrospectives/retro-airan-central-edge-placement/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-airan-central-edge-placement/</guid><description>New ARC configurations include centralized high-capacity sites. Network-edge claims need an actual placement and request path rather than a uniform edge label.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why telecom land, power and fiber are only the first AI layer</title><link>https://retrivium.ai/retrospectives/retro-airan-operator-assets-stack/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-airan-operator-assets-stack/</guid><description>Telecom assets enable deployment but do not themselves provide model serving. ARC adds compute and software layers whose operational readiness remains site specific.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron3.5 retrieval launch: three stages of the evidence pipeline</title><link>https://retrivium.ai/retrospectives/nemotron35-three-evidence-stages-release/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/nemotron35-three-evidence-stages-release/</guid><description>The Nemotron retrieval launch matters because it presents extraction, candidate retrieval and reranking as separate evidence stages.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Granite Speech5: transcription,TurboCTC and attribution are separate release roles</title><link>https://retrivium.ai/retrospectives/granite-speech5-three-contracts/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/granite-speech5-three-contracts/</guid><description>Granite Speech5 separates transcription, speech-language generation and attribution, so the October announcement cannot be reduced to a single recognition ranking.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Humming: why a unified quantization format still needs a device-specific kernel</title><link>https://retrivium.ai/retrospectives/humming-format-kernel-contract-release/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/humming-format-kernel-contract-release/</guid><description>Humming unifies quantization representation, but a common representation does not remove the need for kernels specialized to devices and workloads.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron3.5 Embed,Rerank and Parse: page-image evidence in dense retrieval</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-retriever-page-images/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-retriever-page-images/</guid><description>Nemotron&apos;s visual dense retrieval can make page-image information searchable, but finding a relevant page is not the same as producing a coordinate-grounded citation for an answer.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron3.5 Embed,Rerank and Parse: reranking and missing candidates</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-retriever-rerank-contract/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-retriever-rerank-contract/</guid><description>Nemotron&apos;s reranker can reorder the candidates it receives, but it cannot recover a relevant document that the preceding retrieval stage never supplied.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron3.5 Embed,Rerank and Parse: document parsing before embeddings</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-retriever-parser-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-retriever-parser-boundary/</guid><description>Releasing a parser beside Nemotron&apos;s retrieval models makes ingestion a separate evidence boundary, because correct search cannot recover document relationships already lost before indexing.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Granite Speech5.0: CTC decoding and speech-language generation</title><link>https://retrivium.ai/retrospectives/retro-ibm-speech5-ctc-versus-slm/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-ibm-speech5-ctc-versus-slm/</guid><description>Granite Speech5.0 contains different speech inference paths. Trace why CTC transcription and speech-language generation need distinct acceptance criteria.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Granite Speech5.0: speaker attribution beyond word accuracy</title><link>https://retrivium.ai/retrospectives/retro-ibm-speech5-attribution/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-ibm-speech5-attribution/</guid><description>Granite Speech attribution addresses who spoke and when. Reconstruct why accurate words alone became insufficient for meeting and call applications.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Granite Speech5.0: keyword biasing and unsupported terms</title><link>https://retrivium.ai/retrospectives/retro-ibm-speech5-keyword-bias/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-ibm-speech5-keyword-bias/</guid><description>Granite Speech keyword biasing helps domain vocabulary, but prompts are not acoustic evidence. Trace the distinction and a practical acceptance approach.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM Humming: why shared quantization still needs specialized kernels</title><link>https://retrivium.ai/retrospectives/retro-vllm-humming-representation-jit/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-vllm-humming-representation-jit/</guid><description>A retrospective on Humming, quantization integration and the boundary between a common tensor representation and execution tuned to a particular GPU workload.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM Humming benchmarks: from a fast kernel to a complete request</title><link>https://retrivium.ai/retrospectives/retro-vllm-humming-kernel-benchmark/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-vllm-humming-kernel-benchmark/</guid><description>How to read Humming performance results retrospectively: isolate kernel work, request scheduling and the conditions needed for a useful end-to-end comparison.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why llm-d 1.0 was an operations milestone as well as a serving release</title><link>https://retrivium.ai/retrospectives/retro-llmd-day-two-milestone/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-llmd-day-two-milestone/</guid><description>llm-d 1.0 emphasized stable configuration, coordinated upgrades and traffic policy. Those features make ongoing operations a distinct part of distributed inference.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Cache locality and tenant fairness can pull a router in different directions</title><link>https://retrivium.ai/retrospectives/retro-llmd-cache-fairness/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-llmd-cache-fairness/</guid><description>llm-d 1.0 combined cache-aware serving with priority and fairness controls. Reuse efficiency and allocation policy solve connected but different problems.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why prefill and decode upgrades need a shared lifecycle</title><link>https://retrivium.ai/retrospectives/retro-llmd-coordinated-upgrades/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-llmd-coordinated-upgrades/</guid><description>Disaggregated prefill and decode can scale separately while retaining shared compatibility requirements. llm-d 1.0 made coordinated upgrades an explicit lifecycle concern.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>TorchTPU changes the unit of TPU model porting</title><link>https://retrivium.ai/retrospectives/retro-torchtpu-porting-unit/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-torchtpu-porting-unit/</guid><description>TorchTPU offers native PyTorch execution on TPUs. It can reduce model-definition rewrites while moving qualification toward backend behavior and supported execution paths.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Eager debugging and compiled serving answer different TPU questions</title><link>https://retrivium.ai/retrospectives/retro-torchtpu-eager-compile/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-torchtpu-eager-compile/</guid><description>TorchTPU exposes eager and compiled execution paths. Correct eager output does not establish warm compiled latency, preparation cost or coverage of every input shape.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why an out-of-tree TPU plugin can preserve the vLLM control plane</title><link>https://retrivium.ai/retrospectives/retro-torchtpu-vllm-plugin/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-torchtpu-vllm-plugin/</guid><description>The TorchTPU vLLM plugin separates shared serving logic from TPU-specific execution. A common interface does not establish parity for every backend feature.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Open-source TPU support makes compatibility inspectable, not automatic</title><link>https://retrivium.ai/retrospectives/retro-torchtpu-open-source-validation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-torchtpu-open-source-validation/</guid><description>Open-sourcing TorchTPU makes native TPU implementation and integration boundaries inspectable. Exact model and serving combinations still need their own compatibility evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Voxtral3: a family release, not one monolithic speech model</title><link>https://retrivium.ai/retrospectives/voxtral3-four-stage-voice-release/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/voxtral3-four-stage-voice-release/</guid><description>The Voxtral3 launch should be read as a family and pipeline release rather than one universal speech model.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DeepInfer release: why an open inference engine is not a complete service</title><link>https://retrivium.ai/retrospectives/deepinfer-public-engine-not-service/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/deepinfer-public-engine-not-service/</guid><description>DeepInfer published an inference implementation, but the public code did not turn an offline model runner into a complete hosted service.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM TorchTPU: model-code reuse is not kernel portability</title><link>https://retrivium.ai/retrospectives/torchtpu-model-code-versus-kernel-portability/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/torchtpu-model-code-versus-kernel-portability/</guid><description>vLLM TorchTPU reuses model-serving code while keeping platform-specific execution explicit, so source reuse cannot be treated as automatic kernel portability.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Voxtral 3: separate speech stages in a voice agent</title><link>https://retrivium.ai/retrospectives/retro-mistral-voxtral3-voice-stages/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-voxtral3-voice-stages/</guid><description>Voxtral3&apos;s voice-agent framing combines separate speech stages, so a successful conversation cannot be attributed to one model without identifying the chain that produced it.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Voxtral 3: interruptions and end-of-turn decisions</title><link>https://retrivium.ai/retrospectives/retro-mistral-voxtral3-interruption/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-voxtral3-interruption/</guid><description>Voxtral3&apos;s conversational framing makes interruptions and turn boundaries evaluation targets, because transcription accuracy alone cannot explain when a voice agent should act or stop speaking.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Voxtral 3: self-deployment and public weight availability</title><link>https://retrivium.ai/retrospectives/retro-mistral-voxtral3-private-deployment/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-voxtral3-private-deployment/</guid><description>Voxtral3&apos;s self-deployment offering and publicly downloadable weights are different access contracts, so one should not be used as evidence that every family component has the other.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DeepInfer initial public commit: offline inference and service completeness</title><link>https://retrivium.ai/retrospectives/retro-deepinfer-public-offline-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-deepinfer-public-offline-boundary/</guid><description>DeepInfer published offline inference building blocks. Trace why an open engine and a complete multi-user service remain different engineering deliverables.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DeepInfer initial public commit: initial commit versus repository creation</title><link>https://retrivium.ai/retrospectives/retro-deepinfer-public-commit-date/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-deepinfer-public-commit-date/</guid><description>DeepInfer’s public commit anchors code availability more precisely than repository creation. Reconstruct why different project timestamps answer different questions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM TorchTPU startup: compilation is a different phase from serving</title><link>https://retrivium.ai/retrospectives/retro-vllm-torchtpu-compilation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-vllm-torchtpu-compilation/</guid><description>A retrospective on TorchTPU model reuse, graph compilation and why a serving comparison must distinguish first startup, restarts and warmed requests.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM TorchTPU compatibility: a common API still needs a feature matrix</title><link>https://retrivium.ai/retrospectives/retro-vllm-torchtpu-feature-matrix/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-vllm-torchtpu-feature-matrix/</guid><description>How TorchTPU reached a common vLLM interface, and why model families, precision choices and validated deployment combinations need separate evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The Indiana SMR announcement was a feasibility gate, not delivered power</title><link>https://retrivium.ai/retrospectives/retro-indiana-smr-feasibility-gate/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-indiana-smr-feasibility-gate/</guid><description>The Indiana SMR agreement explores a site-specific project. Its reactor and power targets describe feasibility scope rather than delivered electricity or completed investment approval.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why a second SMR site tests a deployment model as well as a reactor</title><link>https://retrivium.ai/retrospectives/retro-indiana-smr-repeat-site/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-indiana-smr-repeat-site/</guid><description>Indiana extends the X-energy deployment program to another site and utility. Repeated proposals test transferability without proving realized learning-curve cost savings.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Amazon Indiana: A former coal site offers infrastructure context, not automatic nuclear approval</title><link>https://retrivium.ai/retrospectives/retro-indiana-coal-site-reuse/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-indiana-coal-site-reuse/</guid><description>Amazon’s Indiana nuclear announcement followed reactor financing and another site plan. A retrospective on what former coal infrastructure can and cannot establish.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Amazon Indiana: Development funding and electricity offtake play different roles</title><link>https://retrivium.ai/retrospectives/retro-indiana-offtake-development/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-indiana-offtake-development/</guid><description>How Amazon’s earlier reactor investment led to an Indiana agreement combining development support with prospective electricity purchasing, with different obligations at each stage.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>MiniMax M3.1Flash: what the SpaceBunny reveal established and what remained pending</title><link>https://retrivium.ai/retrospectives/minimax-m31-spacebunny-to-named-release/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/minimax-m31-spacebunny-to-named-release/</guid><description>MiniMax M3.1Flash turned the SpaceBunny preview into a named API release, while the announcement still treated downloadable weights as a later step.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>MiniMax M3.1Flash: anonymous preview and named-model evidence</title><link>https://retrivium.ai/retrospectives/retro-minimax-m31-api-stealth-evidence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-minimax-m31-api-stealth-evidence/</guid><description>MiniMax identified SpaceBunny as an early M3.1Flash version. Trace what anonymous preview feedback establishes and what still needs controlled evaluation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>MiniMax M3.1Flash: API launch before checkpoint terms</title><link>https://retrivium.ai/retrospectives/retro-minimax-m31-api-checkpoint-release/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-minimax-m31-api-checkpoint-release/</guid><description>The M3.1Flash launch separated API availability from a later weight release. Reconstruct why interface access and self-hosting artifacts have different dates.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Timestral: why covariates are not chat context</title><link>https://retrivium.ai/retrospectives/timestral-covariates-not-chat-context/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/timestral-covariates-not-chat-context/</guid><description>Timestral&apos;s release matters because forecasting has a different evidence contract from language generation, even when both are called foundation models.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron SuperVL: the October expansion from text execution to visual agents</title><link>https://retrivium.ai/retrospectives/super-vl-october-agent-modality-expansion/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/super-vl-october-agent-modality-expansion/</guid><description>SuperVL expands an agent-model family into visual execution without making its members interchangeable.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Timestral: known-future inputs and leakage</title><link>https://retrivium.ai/retrospectives/retro-mistral-timestral-future-covariates/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-timestral-future-covariates/</guid><description>Timestral&apos;s known-future covariates are inputs available at forecast time, not permission to include future outcomes that the forecasting system would not yet know.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Timestral: probabilistic forecasts and point answers</title><link>https://retrivium.ai/retrospectives/retro-mistral-timestral-uncertainty/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-timestral-uncertainty/</guid><description>Timestral&apos;s probabilistic forecasts should be evaluated as uncertainty-bearing predictions, not reduced to fluent answers or a single point that discards the release&apos;s task contract.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Timestral: chronological holdouts after the release</title><link>https://retrivium.ai/retrospectives/retro-mistral-timestral-forecast-splits/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-timestral-forecast-splits/</guid><description>A chronological holdout for Timestral must preserve the information available at each forecast origin, because zero-shot use does not automatically make a retrospective evaluation leakage-free.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron 3.5 SuperVL: visual documents versus video tasks</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-super-vl-visual-evidence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-super-vl-visual-evidence/</guid><description>NemotronSuperVL&apos;s multimodal release needs separate document and video fixtures, because identifying a still page is different from understanding an event across time.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron 3.5 SuperVL: execution and orchestration roles</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-super-vl-role-complement/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-super-vl-role-complement/</guid><description>NemotronSuperVL and the announced Bolt roles should be evaluated as different workflow choices, rather than treating a new visual model as a universal replacement for orchestration.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nemotron 3.5 SuperVL: customization and retained acceptance tests</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-super-vl-posttraining/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-super-vl-posttraining/</guid><description>Customizing NemotronSuperVL creates a new behavioural artifact, so access to an adaptable model does not remove the need to retain acceptance tests for the behaviour that must survive.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Voice 3.0: Support-call resolution is different from fluent speech</title><link>https://retrivium.ai/retrospectives/grok-voice3-support-resolution/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-voice3-support-resolution/</guid><description>Grok Voice 3.0 emphasizes support-call outcomes. This retrospective separates successful resolution, tool-state correctness and caller satisfaction with the speech.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Voice 3.0: Low audio latency does not guarantee good turn-taking</title><link>https://retrivium.ai/retrospectives/grok-voice3-latency-vs-turn-taking/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-voice3-latency-vs-turn-taking/</guid><description>Why Grok Voice 3.0’s responsiveness discussion needs separate tests for first audio, complete caller intent, interruptions and recovery of the conversation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Voice 3.0: A voice-model upgrade needs an audio regression artifact</title><link>https://retrivium.ai/retrospectives/grok-voice3-upgrade-audio-regression/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-voice3-upgrade-audio-regression/</guid><description>Why a Grok Voice 3.0 migration needs a repeatable conversational fixture preserving audio, task state and tool outcomes, not only a text prompt comparison.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Private endpoint visibility is a different boundary from retention</title><link>https://retrivium.ai/retrospectives/retro-openrouter-private-visibility-retention/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-private-visibility-retention/</guid><description>Private Endpoints changes deployment visibility and routing exposure. It does not automatically change upstream retention; even setup tests remain real processing requests.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Reserved inference capacity and optional public overflow</title><link>https://retrivium.ai/retrospectives/retro-openrouter-reserved-fallback/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-reserved-fallback/</guid><description>Private Endpoints can prioritize reserved capacity with optional constrained public overflow. The caller still chooses whether a different execution path and deployment behavior are acceptable.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why Private Endpoints did not become arbitrary self-hosted model ingestion</title><link>https://retrivium.ai/retrospectives/retro-openrouter-private-catalog-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-private-catalog-boundary/</guid><description>Private Endpoints reuses a catalog model’s identity through a supported BYOK provider and workspace key. Those dependencies define an Enterprise deployment feature, not arbitrary supplier admission.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How AI writing created the verification bottleneck behind Deep Review</title><link>https://retrivium.ai/retrospectives/deep-review-verification-bottleneck/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/deep-review-verification-bottleneck/</guid><description>How the progression from Paper Assistant Tool pilots to Deep Review reflects a bottleneck in checking technical claims as AI-assisted writing grows.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why the claim became the right unit for document review</title><link>https://retrivium.ai/retrospectives/deep-review-claim-evidence-unit/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/deep-review-claim-evidence-unit/</guid><description>Why technical-document review benefits from treating a claim and its supporting evidence as an inspectable unit, in the history leading to Deep Review.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How author feedback and institutional peer review diverged</title><link>https://retrivium.ai/retrospectives/deep-review-author-feedback-institutions/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/deep-review-author-feedback-institutions/</guid><description>How optional author-feedback pilots before Deep Review clarify the different roles of manuscript assistance, independent review and institutional decisions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why technical review became an asynchronous AI workload</title><link>https://retrivium.ai/retrospectives/deep-review-asynchronous-compute/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/deep-review-asynchronous-compute/</guid><description>Why a system such as Deep Review is best understood as a long-running verification job, with different infrastructure needs from conversational chat.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How Earth AI showed why a language model needs specialized spatial tools</title><link>https://retrivium.ai/retrospectives/earth-ai-specialized-tools/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/earth-ai-specialized-tools/</guid><description>How the Earth AI geospatial-agent announcement follows a path from reusable spatial representations toward specialized tools coordinated by a language model.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why planetary data belongs in a workspace beyond the context window</title><link>https://retrivium.ai/retrospectives/earth-ai-workspace-context-window/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/earth-ai-workspace-context-window/</guid><description>Why Earth AI’s geospatial-agent architecture makes a separate data workspace important when the underlying evidence is larger than a useful prompt.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How upfront planning became a measurable part of geospatial agents</title><link>https://retrivium.ai/retrospectives/earth-ai-planning-before-execution/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/earth-ai-planning-before-execution/</guid><description>How Earth AI’s geospatial-agent evaluation makes upfront planning a testable design choice, while separating planning quality from extra computation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why geospatial agents still need a boundary for expert review</title><link>https://retrivium.ai/retrospectives/earth-ai-expert-review-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/earth-ai-expert-review-boundary/</guid><description>Why experimental geospatial agents such as Earth AI need an inspectable boundary between a useful first draft and an expert-validated spatial conclusion.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Argon GA made the continuation protocol an integration decision</title><link>https://retrivium.ai/retrospectives/argon-ga-unified-budget-continuation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/argon-ga-unified-budget-continuation/</guid><description>How Argon GA turns long decoding into a client continuation contract with unified-budget interpretation and explicit output assembly checks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Broad access still needs a platform-by-plan matrix</title><link>https://retrivium.ai/retrospectives/argon-ga-platform-availability-matrix/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/argon-ga-platform-availability-matrix/</guid><description>How Argon&apos;s broad release still requires a platform-and-plan access matrix that keeps app demonstrations separate from API acceptance.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Argon&apos;s introductory pricing created a temporary planning condition</title><link>https://retrivium.ai/retrospectives/argon-ga-introductory-economics/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/argon-ga-introductory-economics/</guid><description>How Argon&apos;s introductory price creates a temporary planning condition that should be separated from task mix and steady-state usage scenarios.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Public engineering artifacts make launch claims more inspectable</title><link>https://retrivium.ai/retrospectives/argon-ga-public-artifacts-evidence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/argon-ga-public-artifacts-evidence/</guid><description>How public Argon engineering artifacts improve causal inspection while keeping framework benchmarks separate from unmeasured downstream performance.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-24B-A2B: the final LFM2.5 release and its changed reasoning contract</title><link>https://retrivium.ai/retrospectives/lfm25-24b-final-family-release/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/lfm25-24b-final-family-release/</guid><description>The final LFM2.5 release should be read as a change in the reasoning and adaptation contract, rather than as a promise that sparse activation makes the whole checkpoint small.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-24B-A2B: reasoning-only responses and structured clients</title><link>https://retrivium.ai/retrospectives/retro-liquid-24b-reasoning-parser/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-24b-reasoning-parser/</guid><description>LFM2.5-24B-A2B&apos;s reasoning-only contract changes what a structured client must recognize as completion, independently of any model-quality comparison.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-24B-A2B: active experts and weight residency</title><link>https://retrivium.ai/retrospectives/retro-liquid-24b-resident-experts/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-24b-resident-experts/</guid><description>LFM2.5-24B-A2B&apos;s sparse computation does not make its full weight inventory disappear, so active experts and resident artifacts need separate accounting.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-24B-A2B: tokenizer expansion and migration fixtures</title><link>https://retrivium.ai/retrospectives/retro-liquid-24b-tokenizer-contract/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-24b-tokenizer-contract/</guid><description>LFM2.5-24B-A2B&apos;s tokenizer change makes input identity part of migration, because preserving text does not necessarily preserve token sequences or budgets.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Active Focus still needs a stopping rule</title><link>https://retrivium.ai/retrospectives/wonder-active-focus-stopping-rule/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/wonder-active-focus-stopping-rule/</guid><description>Why Muse Wonder&apos;s Active Focus needs progress evidence and stopping rules that distinguish recoverable errors from genuine blockers.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Active Memory raises the question of evidence freshness</title><link>https://retrivium.ai/retrospectives/wonder-active-memory-evidence-freshness/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/wonder-active-memory-evidence-freshness/</guid><description>Why Muse Wonder&apos;s Active Memory needs freshness evaluation as well as relevant recall when agents revisit changing projects and records.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Wonder and Wonder Full launched through different access paths</title><link>https://retrivium.ai/retrospectives/wonder-full-access-matrix/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/wonder-full-access-matrix/</guid><description>How Muse Wonder and Wonder Full&apos;s initial access routes require a variant-by-surface matrix rather than one family-wide availability claim.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Helion and the separation of agent execution from model inference</title><link>https://retrivium.ai/retrospectives/retro-helion-cpu-agents-inference-split/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-helion-cpu-agents-inference-split/</guid><description>Helion’s CPU-only option exposes a separate agent execution tier. The useful sizing unit includes tool work, model calls and the dependencies between them.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why Helion includes an enterprise CPU/GPU configuration</title><link>https://retrivium.ai/retrospectives/retro-helion-enterprise-mi350p-rack/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-helion-enterprise-mi350p-rack/</guid><description>Helion’s EPYC and MI350P option gives enterprises a system boundary to evaluate. Integration value depends on real application handoffs, not accelerator count alone.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Helion: open specification, partner design, and availability are separate milestones</title><link>https://retrivium.ai/retrospectives/retro-helion-open-rack-availability/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-helion-open-rack-availability/</guid><description>Helion’s open blueprint, partner implementation and planned availability are distinct milestones. A specification improves coordination without proving delivery or site acceptance.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A CPU-only agent rack changes what an AI capacity count means</title><link>https://retrivium.ai/retrospectives/retro-helion-cpu-rack-accounting/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-helion-cpu-rack-accounting/</guid><description>A CPU-only Helion rack highlights three different ledgers: installed hardware, ready service capacity and completed application work. Their units cannot simply be added.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Haiku 5.5 subagents need smaller contracts, not vague delegation</title><link>https://retrivium.ai/retrospectives/haiku55-subagent-contract-size/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/haiku55-subagent-contract-size/</guid><description>Why Haiku 5.5 subagents need bounded questions and checkable return artifacts before lower call costs can become useful task-level efficiency.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Cheap summaries still spend an omission budget</title><link>https://retrivium.ai/retrospectives/haiku55-summary-omission-budget/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/haiku55-summary-omission-budget/</guid><description>How to evaluate Haiku 5.5 summaries for task-relevant exceptions and exact identifiers instead of treating short output as sufficient quality.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Haiku 5.5 browser use makes action composition visible</title><link>https://retrivium.ai/retrospectives/haiku55-browser-action-composition/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/haiku55-browser-action-composition/</guid><description>Why Haiku 5.5 browser evaluation must check target identity and changing page state across an action sequence, not just plausible clicks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>High-volume Haiku traffic needs failure slices, not one average</title><link>https://retrivium.ai/retrospectives/haiku55-volume-evaluation-slices/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/haiku55-volume-evaluation-slices/</guid><description>Why high-volume Haiku 5.5 evaluation needs failure slices, consequence-aware routing and explicit uncertainty beyond a pooled average.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A 240-MW India plan is not current GPU availability</title><link>https://retrivium.ai/retrospectives/retro-india-power-plan-not-gpu-availability/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-india-power-plan-not-gpu-availability/</guid><description>CoreWeave’s India campus is a phased future deployment. Its planned power describes infrastructure scale, while an application still needs a matching date and allocated execution path.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Indonesia before India: the sequencing of CoreWeave’s Asia expansion</title><link>https://retrivium.ai/retrospectives/retro-coreweave-asia-region-sequencing/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-coreweave-asia-region-sequencing/</guid><description>CoreWeave announced Indonesia before India, with separate 2028 delivery descriptions. A common cloud roadmap links the projects without making their commissioning paths identical.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why a future India campus was announced around Rubin-class infrastructure</title><link>https://retrivium.ai/retrospectives/retro-india-rubin-facility-planning/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-india-rubin-facility-planning/</guid><description>CoreWeave’s India plan names cooling mechanisms and future-generation intent. Adaptability becomes meaningful through specified building-to-rack interfaces and later qualification.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Three planned buildings do not establish one India delivery date</title><link>https://retrivium.ai/retrospectives/retro-india-power-phase-timeline/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-india-power-phase-timeline/</guid><description>CoreWeave specifies three buildings and phased India delivery. Building count does not establish the number of commissioning phases or one date for the whole campus.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Open d1: why a decision model is a different interface from a chat model</title><link>https://retrivium.ai/retrospectives/open-d1-not-generative-chat/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/open-d1-not-generative-chat/</guid><description>Open d1 changes the shape of the application interface: a decision model can return a bounded answer without composing a conversational response.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Open d1: decision probabilities and application policy</title><link>https://retrivium.ai/retrospectives/retro-liquid-d1-weights-probability-policy/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-d1-weights-probability-policy/</guid><description>Open d1 exposes a decision interface, but the application&apos;s action threshold remains a separate policy choice with consequences that model publication cannot determine.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Open d1: encoder and decoder decision backbones</title><link>https://retrivium.ai/retrospectives/retro-liquid-d1-weights-encoder-decoder/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-d1-weights-encoder-decoder/</guid><description>Open d1&apos;s encoder and decoder variants solve a related decision problem through different input contracts, so parameter count alone cannot select between them.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Open d1: portable weights and browser execution</title><link>https://retrivium.ai/retrospectives/retro-liquid-d1-weights-browser-portability/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-d1-weights-browser-portability/</guid><description>Open d1&apos;s downloadable weights make browser experiments possible to investigate, but weight availability alone does not establish a complete browser execution path.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How better AI-assisted work became a different question from better skills</title><link>https://retrivium.ai/retrospectives/ai-work-quality-vs-skill/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/ai-work-quality-vs-skill/</guid><description>How the AI-assisted work debate reached a separate question about independent skill, in the context of Google’s October study of professional learning.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why seniority changes the learning question around AI assistance</title><link>https://retrivium.ai/retrospectives/ai-work-seniority-learning/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/ai-work-seniority-learning/</guid><description>Why professional experience changes the learning question around AI assistance, in the history leading to Google’s October work-quality study.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How unaided transfer tests became essential for evaluating AI tools</title><link>https://retrivium.ai/retrospectives/ai-work-transfer-testing/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/ai-work-transfer-testing/</guid><description>How independent transfer tasks became necessary for evaluating AI-assisted learning, separating a useful tool from a durable change in human competence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>An uprate adds output without being a new reactor</title><link>https://retrivium.ai/retrospectives/retro-nuclear-uprate-new-reactor/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nuclear-uprate-new-reactor/</guid><description>The Constellation agreement targets uprates at operating nuclear plants. New reactors, dormant-plant restarts and uprates begin from different physical baselines.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>An AI power purchase agreement spans a longer clock than a GPU refresh</title><link>https://retrivium.ai/retrospectives/retro-nuclear-ppa-time-horizon/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nuclear-ppa-time-horizon/</guid><description>Long-term nuclear procurement and GPU deployment run on different schedules. The uprate agreement supports future supply rather than a named accelerator delivery date.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Preserving nuclear output and adding nuclear output are different quantities</title><link>https://retrivium.ai/retrospectives/retro-nuclear-capacity-additionality/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nuclear-capacity-additionality/</guid><description>Nuclear agreements change different baselines: new construction, restored operation, uprates and preserved output. Capacity accounting must name the baseline before summing.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grid-scale nuclear supply does not describe a datacenter’s instantaneous mix</title><link>https://retrivium.ai/retrospectives/retro-nuclear-grid-datacenter-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nuclear-grid-datacenter-boundary/</guid><description>Nuclear procurement supports supply development. It does not establish a datacenter&apos;s instantaneous electricity mix or a service&apos;s measured inference energy footprint.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mistral Large4 preview: what was public on October6</title><link>https://retrivium.ai/retrospectives/mistral-large4-preview-versus-release/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/mistral-large4-preview-versus-release/</guid><description>Mistral&apos;s Large4 preview created an evaluation surface before it created a downloadable deployment artifact.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Mistral Large 4: preview access and defensive evaluation</title><link>https://retrivium.ai/retrospectives/retro-mistral-large4-preview-preview-cyber/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-large4-preview-preview-cyber/</guid><description>Mistral Large4&apos;s preview provides a real evaluation surface, but a successful preview test does not certify a later checkpoint that undergoes additional post-training.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Mistral Large 4: API access before deployment control</title><link>https://retrivium.ai/retrospectives/retro-mistral-large4-preview-preview-portability/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-large4-preview-preview-portability/</guid><description>Mistral Large4&apos;s API preview enabled task evaluation before it enabled control over a self-hosted checkpoint, so those adoption decisions must remain distinct.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Mistral Large 4: benchmark claims before reproducible artifacts</title><link>https://retrivium.ai/retrospectives/retro-mistral-large4-preview-preview-evals/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-large4-preview-preview-evals/</guid><description>A benchmark claim attached to the Mistral Large4 preview and an independently reproduced result are different evidence types, even when they concern the same task name.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How reporting delays made location embeddings useful for health research</title><link>https://retrivium.ai/retrospectives/earth-ai-health-reporting-lag/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/earth-ai-health-reporting-lag/</guid><description>How reporting delays create a role for location embeddings in Earth AI health research, and why prediction-time evidence must be evaluated carefully.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why cross-border health modelling needs geographic transfer tests</title><link>https://retrivium.ai/retrospectives/earth-ai-health-geographic-transfer/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/earth-ai-health-geographic-transfer/</guid><description>Why Earth AI public-health research makes geographic transfer a separate evaluation problem, even when a model uses reusable location representations.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How place embeddings sharpened the distinction between prediction and cause</title><link>https://retrivium.ai/retrospectives/earth-ai-health-proxy-causality/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/earth-ai-health-proxy-causality/</guid><description>How Earth AI place representations make the distinction between useful prediction and a causal explanation especially important in public-health research.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>d1 vision launch: hosted decisions before open weights</title><link>https://retrivium.ai/retrospectives/d1-hosted-vision-before-open-weights/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/d1-hosted-vision-before-open-weights/</guid><description>The hosted d1 vision announcement made policy questions over text and images an application interface before the later open-weight release.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing d1: versioning a hosted decision question</title><link>https://retrivium.ai/retrospectives/retro-liquid-d1-vision-policy-version/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-d1-vision-policy-version/</guid><description>The hosted d1 launch made the decision question part of an application&apos;s behaviour, so editing that question can constitute a release without changing the model name.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing d1: visual conditions versus text-only labels</title><link>https://retrivium.ai/retrospectives/retro-liquid-d1-vision-image-condition/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-d1-vision-image-condition/</guid><description>The d1 vision launch changed the evidence available to a decision, so a text-only fixture cannot establish that an image-dependent condition is being evaluated correctly.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing d1: uncertain decisions before the open-weight drop</title><link>https://retrivium.ai/retrospectives/retro-liquid-d1-vision-abstention-contract/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-d1-vision-abstention-contract/</guid><description>The hosted d1 announcement made bounded decisions accessible before the weight publication, but it did not remove the application&apos;s responsibility for uncertain or unanswerable cases.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How agent privacy moved from secret storage to appropriate information flow</title><link>https://retrivium.ai/retrospectives/agent-privacy-information-flow/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agent-privacy-information-flow/</guid><description>How the contextual-agent privacy report reflects a shift from protecting stored secrets toward controlling which information flows are appropriate for a task.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why delegated agent work needs delegated authority limits</title><link>https://retrivium.ai/retrospectives/agent-privacy-delegation-authority/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agent-privacy-delegation-authority/</guid><description>Why the progression from tool use to delegated agents makes authority boundaries part of the task contract, in the context of the October privacy report.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How confirmation fatigue became a design problem for AI agents</title><link>https://retrivium.ai/retrospectives/agent-privacy-confirmation-fatigue/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agent-privacy-confirmation-fatigue/</guid><description>How agent autonomy made confirmation fatigue a privacy and interaction problem, and why useful approval boundaries need more than frequent prompts.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why agent observability needs its own privacy boundary</title><link>https://retrivium.ai/retrospectives/agent-privacy-security-observability/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agent-privacy-security-observability/</guid><description>Why the contextual-agent privacy discussion creates a second boundary around observability: tracing actions without unnecessarily retaining private payloads.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A smaller Spark configuration changes capacity choice before compute identity</title><link>https://retrivium.ai/retrospectives/retro-spark-64-capacity-choice/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-spark-64-capacity-choice/</guid><description>The 64 GB DGX Spark option changes the memory tier within the GB10 platform. Workload state and partner delivery status remain part of the configuration decision.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Two Spark systems add distributed capacity, not one local memory bus</title><link>https://retrivium.ai/retrospectives/retro-spark-cluster-memory-locality/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-spark-cluster-memory-locality/</guid><description>Sync Cluster Assistant can simplify multi-Spark setup. Connected systems still have distributed placement and communication boundaries rather than one local memory bus.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why the Spark post date and partner shipping date differ</title><link>https://retrivium.ai/retrospectives/retro-spark-announced-shipping-date/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-spark-announced-shipping-date/</guid><description>The Spark configuration post and its planned partner availability date describe different milestones. Announcement, shipment and workload acceptance need separate evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Local inference capacity does not make an entire agent workflow offline</title><link>https://retrivium.ai/retrospectives/retro-spark-local-agent-scope/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-spark-local-agent-scope/</guid><description>Local Spark inference changes where the model executes. Agent tools, artifact downloads, stored history and external services retain their own location boundaries.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How federated learning reached the demand for verifiable trust</title><link>https://retrivium.ai/retrospectives/federated-learning-verifiable-trust/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/federated-learning-verifiable-trust/</guid><description>How the history of secure aggregation and federated learning leads to Google’s October proposal for externally verifiable privacy guarantees.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why moving computation does not settle the privacy question</title><link>https://retrivium.ai/retrospectives/federated-learning-compute-placement/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/federated-learning-compute-placement/</guid><description>Why Google’s October federated-learning proposal makes compute placement and privacy guarantees separate architectural questions, beyond local-versus-cloud labels.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How device participation became part of learning quality</title><link>https://retrivium.ai/retrospectives/federated-learning-device-participation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/federated-learning-device-participation/</guid><description>How federated learning’s device constraints made participation part of model quality, and why the October system announcement renews that evaluation question.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why privacy guarantees must survive the whole training workflow</title><link>https://retrivium.ai/retrospectives/federated-learning-guarantee-composition/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/federated-learning-guarantee-composition/</guid><description>Why the history of private federated learning leads to workflow-level guarantees, including repeated releases, verification state and operational changes.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Argon had an announcement clock and an access clock</title><link>https://retrivium.ai/retrospectives/argon-preview-phased-release-clock/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/argon-preview-phased-release-clock/</guid><description>Why Gemini 4 Argon&apos;s September announcement must retain its restricted initial-access condition instead of backdating broader availability.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Long output capacity does not define a completed project</title><link>https://retrivium.ai/retrospectives/argon-preview-long-output-completion/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/argon-preview-long-output-completion/</guid><description>Why Argon&apos;s expanded output headroom still needs independent completion rules, semantic continuity and acceptance evidence for the delivered project.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Code migration claims need semantic equivalence evidence</title><link>https://retrivium.ai/retrospectives/argon-preview-code-migration-evidence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/argon-preview-code-migration-evidence/</guid><description>Why Argon&apos;s code-migration examples need behavioral contracts and bounded equivalence evidence beyond rewrite size or performance anecdotes.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Internal agent examples do not establish external reproducibility</title><link>https://retrivium.ai/retrospectives/argon-preview-agent-work-internal-external/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/argon-preview-agent-work-internal-external/</guid><description>How Argon&apos;s internal-agent examples can become portability hypotheses without assuming that external teams share the same inputs, tools and review.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Micron: A 512 GB RDIMM sample is a server-qualification milestone</title><link>https://retrivium.ai/retrospectives/retro-micron-rdimm-sampling-capacity/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-micron-rdimm-sampling-capacity/</guid><description>Micron’s September 512 GB RDIMM samples followed earlier memory production and lower-capacity samples. What that sequence means for server qualification.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Micron: Shipping an SSD for KV cache does not make storage behave like HBM</title><link>https://retrivium.ai/retrospectives/retro-micron-ssd-kv-cache-role/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-micron-ssd-kv-cache-role/</guid><description>Micron’s KV-cache SSD shipment update followed Gen6 storage production. Why the useful inference role is managed state reuse rather than replacing HBM by capacity.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Micron: Memory supply needs a ledger of samples, qualification and shipments</title><link>https://retrivium.ai/retrospectives/retro-micron-memory-product-stage-ledger/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-micron-memory-product-stage-ledger/</guid><description>A retrospective through Micron’s March, June and September updates shows why AI memory samples, production and application shipments need separate product-level records.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Micron: A growing AI memory business does not identify an application’s bottleneck</title><link>https://retrivium.ai/retrospectives/retro-micron-portfolio-inference-bottleneck/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-micron-portfolio-inference-bottleneck/</guid><description>Micron’s AI memory growth followed concrete product milestones. Why that market signal explains industry investment but cannot diagnose an inference application’s bottleneck.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CoreWeave Forge: Why a GPU cloud added the improvement loop above raw capacity</title><link>https://retrivium.ai/retrospectives/retro-forge-gpu-cloud-loop/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-forge-gpu-cloud-loop/</guid><description>CoreWeave Forge followed accelerator plans and agent sandboxes. How the path from running workloads to improving them made workflow continuity an infrastructure concern.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CoreWeave Forge: Production observations are not automatically training data</title><link>https://retrivium.ai/retrospectives/retro-forge-observation-training-data/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-forge-observation-training-data/</guid><description>CoreWeave Forge connects observation with model improvement. Why earlier execution tools make curation possible without turning every recorded interaction into training data.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CoreWeave Forge: A connected evaluation loop still needs a release decision</title><link>https://retrivium.ai/retrospectives/retro-forge-evaluation-release-gate/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-forge-evaluation-release-gate/</guid><description>CoreWeave Forge followed sandboxes and compute plans. Why a connected evaluation workflow can shorten handoffs while leaving the release decision product-specific.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CoreWeave Forge: Portable improvement data and portable execution are different promises</title><link>https://retrivium.ai/retrospectives/retro-forge-portability-interfaces/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-forge-portability-interfaces/</guid><description>CoreWeave Forge emphasizes portable data and open interfaces. How earlier execution and compute layers explain the difference between moving an improvement dataset and moving a workload.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How SynthID Bio moved provenance beyond a digital file</title><link>https://retrivium.ai/retrospectives/synthid-bio-provenance-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/synthid-bio-provenance-boundary/</guid><description>How SynthID Bio connects the earlier history of generated-media provenance with a harder boundary: identifying the origin of scientific artifacts.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why generated science made database provenance urgent</title><link>https://retrivium.ai/retrospectives/synthid-bio-scientific-data-integrity/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/synthid-bio-scientific-data-integrity/</guid><description>Why SynthID Bio reflects a wider scientific data problem: distinguishing generated artifacts from observations before their records are reused.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How watermarking became one layer of scientific trust</title><link>https://retrivium.ai/retrospectives/synthid-bio-layered-trust/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/synthid-bio-layered-trust/</guid><description>A retrospective on SynthID Bio and layered scientific trust: why identifying origin, validating a result and authorizing a use remain separate tasks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What a one-week model replacement means for evaluation cadence</title><link>https://retrivium.ai/retrospectives/sol61-weekly-migration-cadence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sol61-weekly-migration-cadence/</guid><description>Sol changed within a week of its launch; preserve model, fixture and tool configuration so rapid release cadence does not create mixed evaluation reports.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why the Sol 6.1 cache discount is not a task-cost estimate</title><link>https://retrivium.ai/retrospectives/sol61-cache-price-vs-total-task-cost/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sol61-cache-price-vs-total-task-cost/</guid><description>The Sol upgrade cut a cache-read rate, but completed-task costs also depend on cache eligibility, output, retries and accepted work.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Sol 6.1 and the new middle tier for repository work</title><link>https://retrivium.ai/retrospectives/sol61-coding-middle-tier/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sol61-coding-middle-tier/</guid><description>Sol moved the middle tier for repository work; judge dependency relationships, optional paths and accepted patches rather than isolated code generation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Sol 6.1 multi-agent beta: delegation is another execution contract</title><link>https://retrivium.ai/retrospectives/sol61-multiagent-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sol61-multiagent-boundary/</guid><description>Sol introduced a multi-agent beta, but useful delegation still depends on dependency ordering, bounded worker results and an explicit merge condition.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>From API tools to a browser: what changed on DevDay</title><link>https://retrivium.ai/retrospectives/agents-computer-use-from-tools-to-browser/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agents-computer-use-from-tools-to-browser/</guid><description>The Agents API browser expansion changed interaction state; compare identity checks and transitions with direct tools while keeping the task requirement fixed.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The application still owns the browser sign-in boundary</title><link>https://retrivium.ai/retrospectives/agents-computer-use-authentication-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agents-computer-use-authentication-boundary/</guid><description>Agents API browser sign-in establishes access, while the application must still bind the user request to the specific actions permitted under that account.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What a browser-agent replay must preserve</title><link>https://retrivium.ai/retrospectives/agents-computer-use-replay-evidence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agents-computer-use-replay-evidence/</guid><description>A browser-agent audit needs linked observations, intended actions and confirmed outcomes; reconstructing history is different from reapplying clicks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>When a hosted browser is justified beside direct tools</title><link>https://retrivium.ai/retrospectives/agents-computer-use-api-vs-ui-selection/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agents-computer-use-api-vs-ui-selection/</guid><description>Use the Agents API browser option to close a specific evidence gap; an alternate path must preserve target identity and the original question.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Dots changed a task into an ongoing responsibility</title><link>https://retrivium.ai/retrospectives/dots-persistent-responsibility/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/dots-persistent-responsibility/</guid><description>How always-on dots change task completion into responsibility management, with explicit triggers, stale assumptions and stopping conditions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A dot can learn a preference without gaining authority</title><link>https://retrivium.ai/retrospectives/dots-memory-vs-authority/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/dots-memory-vs-authority/</guid><description>Why learned preferences in dots must remain separate from access and action authority, illustrated by a draft-first reporting workflow.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A personal cloud computer is an operational boundary</title><link>https://retrivium.ai/retrospectives/dots-cloud-computer-operating-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/dots-cloud-computer-operating-boundary/</guid><description>Why dots&apos; personal cloud computer makes retained files, session lifetimes and recovery evidence part of agent evaluation beyond model quality.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How to review work that happened between conversations</title><link>https://retrivium.ai/retrospectives/dots-reviewing-background-work/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/dots-reviewing-background-work/</guid><description>How to review dots&apos; background work using evidence-bearing handoffs that preserve partial results, missing dependencies and a clear next decision.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Business connectors make record consistency part of agent work</title><link>https://retrivium.ai/retrospectives/muse-smb-connectors-record-consistency/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/muse-smb-connectors-record-consistency/</guid><description>Why Muse business connectors require entity matching and observation consistency rather than assuming connected tools share one transactional state.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A business goal needs smaller observable action units</title><link>https://retrivium.ai/retrospectives/muse-smb-goal-to-action-granularity/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/muse-smb-goal-to-action-granularity/</guid><description>How Muse&apos;s small-business goals can become observable stages without confusing useful drafts, completed actions and unmeasured business value.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Connected context is not automatically the business source of truth</title><link>https://retrivium.ai/retrospectives/muse-smb-source-of-truth/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/muse-smb-source-of-truth/</guid><description>Why Muse business synthesis needs source authority and permission boundaries when newer messages conflict with approved records.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>One graphics image reduces the GPU-generation image matrix</title><link>https://retrivium.ai/retrospectives/retro-workspaces-image-matrix/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-workspaces-image-matrix/</guid><description>Unified WorkSpaces graphics images reduce generation-specific packaging across supported families. Application tests and licensing remain separate dimensions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Cross-family UpdateFleet changes the migration unit</title><link>https://retrivium.ai/retrospectives/retro-workspaces-cross-family-fleet/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-workspaces-cross-family-fleet/</guid><description>Cross-family UpdateFleet separates supported fleet selection from generation-specific image rebuilding. Image eligibility and application acceptance remain distinct steps.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Image portability does not certify every graphics application</title><link>https://retrivium.ai/retrospectives/retro-workspaces-image-compatibility-validation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-workspaces-image-compatibility-validation/</guid><description>Image portability in WorkSpaces Applications concerns packaging support. Application output, plugins and licensing require distinct qualification evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How image generation separated steering from retraining</title><link>https://retrivium.ai/retrospectives/diffusion-controller-control-vs-retraining/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/diffusion-controller-control-vs-retraining/</guid><description>How the Diffusion Controller explanation fits a longer search for steering image generation without treating every new objective as a full model retraining.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why controllable images require more than a single reward score</title><link>https://retrivium.ai/retrospectives/diffusion-controller-reward-tradeoffs/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/diffusion-controller-reward-tradeoffs/</guid><description>Why the Diffusion Controller discussion renews the distinction between optimizing one image reward and preserving a useful balance of generation qualities.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How diffusion control changed what an inference interface should describe</title><link>https://retrivium.ai/retrospectives/diffusion-controller-serving-interfaces/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/diffusion-controller-serving-interfaces/</guid><description>How steering research such as Diffusion Controller changes what an image-inference interface should identify for reproducibility and workload evaluation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Sonnet 5.5 split the middle-tier question between office work and code</title><link>https://retrivium.ai/retrospectives/sonnet55-middle-tier-office-code/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sonnet55-middle-tier-office-code/</guid><description>Why Sonnet 5.5&apos;s everyday-work positioning needs separate acceptance evidence for repository changes, spreadsheets and presentations.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Faster Sonnet feedback changes the iteration budget</title><link>https://retrivium.ai/retrospectives/sonnet55-faster-feedback-budget/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sonnet55-faster-feedback-budget/</guid><description>How faster Sonnet 5.5 output can change feedback loops, and why generation, human review and accepted completion need separate timing.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A new Sonnet default should not silently rewrite the baseline</title><link>https://retrivium.ai/retrospectives/sonnet55-default-model-evaluation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sonnet55-default-model-evaluation/</guid><description>Why Sonnet 5.5 adoption needs pinned evaluation identities and stable task cohorts, separate from whatever a product interface currently defaults to.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Effort allocation matters inside the Sonnet 5.5 tier</title><link>https://retrivium.ai/retrospectives/sonnet55-effort-allocation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sonnet55-effort-allocation/</guid><description>Why Sonnet 5.5 effort should follow task uncertainty and acceptance boundaries rather than treating the middle tier as one fixed cost-quality point.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Team Bots: Shared expertise does not mean shared private conversations</title><link>https://retrivium.ai/retrospectives/team-bots-shared-expertise-private-context/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/team-bots-shared-expertise-private-context/</guid><description>Team Bots combine shared expertise with separate user context. This retrospective examines why those are different state boundaries in a collaborative agent.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Team Bots: A shared bot needs explicit credential ownership</title><link>https://retrivium.ai/retrospectives/team-bots-credential-ownership/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/team-bots-credential-ownership/</guid><description>Why Team Bots make credential ownership a separate question from sharing an agent, with different identities for personal and team-connected tools.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Team Bots: A team bot&apos;s learned role needs a correction path</title><link>https://retrivium.ai/retrospectives/team-bots-role-memory-correction/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/team-bots-role-memory-correction/</guid><description>Why a learning Team Bot needs a correction path that identifies whether a mistaken instruction, shared skill or individual memory actually caused the answer.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>World Labs and AMD: model research as a hardware-design feedback loop</title><link>https://retrivium.ai/retrospectives/retro-amd-worldlabs-hardware-feedback/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-amd-worldlabs-hardware-feedback/</guid><description>The World Labs agreement could shorten feedback between model research and compute design. The hypothesis needs a trace from workload behavior to a validated platform change.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>From AMD investment to a proposed World Labs acquisition</title><link>https://retrivium.ai/retrospectives/retro-worldlabs-investment-to-agreement/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-worldlabs-investment-to-agreement/</guid><description>World Labs’ earlier funding and AMD’s platform roadmap explain strategic continuity before the acquisition agreement, while leaving internal intent and technical outcomes unproven.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What AMD’s World Labs agreement establishes—and what it does not</title><link>https://retrivium.ai/retrospectives/retro-worldlabs-agreement-not-closing/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-worldlabs-agreement-not-closing/</guid><description>The World Labs announcement establishes an acquisition agreement. Closing, integrated software and usable operating capability each need their own later evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Physical-AI research adds a workload lens to a compute acquisition</title><link>https://retrivium.ai/retrospectives/retro-worldlabs-physical-ai-infrastructure/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-worldlabs-physical-ai-infrastructure/</guid><description>The World Labs agreement is an opportunity to examine workload-to-hardware feedback. Physical-AI capacity still needs an explicit data path, execution profile and evaluation boundary.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>An expressive avatar can conceal unfinished backend work</title><link>https://retrivium.ai/retrospectives/avatar38-presence-vs-completion/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/avatar38-presence-vs-completion/</guid><description>Why Gemini Live Avatar&apos;s continuous visual presence needs separate evidence for backend completion and accurate status communication.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Enterprise Avatar availability is not every Live API surface</title><link>https://retrivium.ai/retrospectives/avatar38-enterprise-surface-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/avatar38-enterprise-surface-boundary/</guid><description>Why Gemini Live Avatar enterprise GA must retain platform, modality and custom-creation access boundaries rather than imply every Live API supports them.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Lip sync and semantic agreement are separate checks</title><link>https://retrivium.ai/retrospectives/avatar38-audio-video-sync-evidence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/avatar38-audio-video-sync-evidence/</guid><description>Why Gemini Live Avatar lip sync, spoken meaning and task completion need separate evidence before an end-to-end quality claim.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A visual persona needs a state handoff during tool delays</title><link>https://retrivium.ai/retrospectives/avatar38-character-state-handoff/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/avatar38-character-state-handoff/</guid><description>How Gemini Live Avatar should represent waiting, user corrections and resolution as meaningful state transitions during asynchronous tool work.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vision DSpark: why faster decoding does not remove image-processing cost</title><link>https://retrivium.ai/retrospectives/lfm25-vision-dspark-prefill-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/lfm25-vision-dspark-prefill-boundary/</guid><description>The visual DSpark release is significant because it accelerates one stage of a multimodal request rather than making the whole request equivalent to text generation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM watermarking: a provenance signal is not a truth score</title><link>https://retrivium.ai/retrospectives/vllm-watermark-provenance-not-truth/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/vllm-watermark-provenance-not-truth/</guid><description>vLLM watermarking adds a statistical provenance signal, but the detector does not determine whether a passage is true or identify its human author.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-VL-DSpark: visual preprocessing and decode acceleration</title><link>https://retrivium.ai/retrospectives/retro-liquid-vl-dspark-vision-prefill/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-vl-dspark-vision-prefill/</guid><description>Vision DSpark can change decoding without removing visual preparation, so its benefit depends on where a complete request spends its work.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-VL-DSpark: a visual drafter and its target contract</title><link>https://retrivium.ai/retrospectives/retro-liquid-vl-dspark-draft-target/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-vl-dspark-draft-target/</guid><description>Vision DSpark needs a paired target and visual input path, so the draft artifact cannot be selected independently from the model it is meant to accelerate.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-VL-DSpark: visual context and draft acceptance</title><link>https://retrivium.ai/retrospectives/retro-liquid-vl-dspark-acceptance-context/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-vl-dspark-acceptance-context/</guid><description>Vision DSpark&apos;s draft acceptance is workload-dependent, so a useful result on one visual task does not establish identical benefit on every output distribution.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM watermark detection: keys, tokenizers and the generation contract</title><link>https://retrivium.ai/retrospectives/retro-vllm-watermarking-key-tokenizer/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-vllm-watermarking-key-tokenizer/</guid><description>A retrospective on text watermarking in vLLM and why detector configuration must identify the key, tokenizer and assumptions behind the generation process.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM watermark statistics: why searching many keys changes the conclusion</title><link>https://retrivium.ai/retrospectives/retro-vllm-watermarking-multiple-testing/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-vllm-watermarking-multiple-testing/</guid><description>How the vLLM watermarking release brings multiple-testing questions into serving operations, and why the best-looking detector result needs its search history.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Voice design turned a preset into a control surface</title><link>https://retrivium.ai/retrospectives/tts38-voice-design-control-surface/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/tts38-voice-design-control-surface/</guid><description>How Gemini 3.8 TTS voice design turns descriptions into production specifications with separate identity, delivery and representative-script checks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Line-level direction can change the meaning of dialogue</title><link>https://retrivium.ai/retrospectives/tts38-dialogue-direction-semantics/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/tts38-dialogue-direction-semantics/</guid><description>Why Gemini 3.8 TTS line direction must preserve negation, uncertainty and speaker intent rather than optimize expressiveness alone.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Flash TTS and Flash-Lite need workload-specific acceptance</title><link>https://retrivium.ai/retrospectives/tts38-flash-lite-production-choice/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/tts38-flash-lite-production-choice/</guid><description>How to compare Gemini Flash TTS and Flash-Lite through distinct creative and batch workloads rather than one universal voice-quality ranking.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A reusable voice is an artifact with provenance</title><link>https://retrivium.ai/retrospectives/tts38-voice-artifact-provenance/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/tts38-voice-artifact-provenance/</guid><description>Why reusable Gemini 3.8 TTS voices need lineage records for design inputs, authorized source material and revisions beyond a saved profile name.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why Sol and Luna changed the economics of task allocation</title><link>https://retrivium.ai/retrospectives/sol-luna-two-model-economics/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sol-luna-two-model-economics/</guid><description>The Sol and Luna release widened model choices; compare completed workflows, escalations and acceptance quality before assigning work by token price.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Image input did not turn Sol and Luna into image generators</title><link>https://retrivium.ai/retrospectives/sol-luna-image-input-text-output/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sol-luna-image-input-text-output/</guid><description>Sol and Luna accept images and return text; distinguish screenshot interpretation from artifact creation when routing requests through a shared interface.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What cached context changed in the Sol and Luna decision</title><link>https://retrivium.ai/retrospectives/sol-luna-cache-workload-economics/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sol-luna-cache-workload-economics/</guid><description>The Sol and Luna launch connected model choice with caching; analyze stable request context separately from changing evidence and generated output.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>An escalation policy after the Sol and Luna launch</title><link>https://retrivium.ai/retrospectives/sol-luna-escalation-evidence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/sol-luna-escalation-evidence/</guid><description>Sol and Luna widened escalation choices, but a useful gate depends on missing evidence and acceptance conditions rather than confidence alone.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Opus 5.5 made token efficiency a task-accounting question</title><link>https://retrivium.ai/retrospectives/opus55-token-efficiency-task-accounting/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/opus55-token-efficiency-task-accounting/</guid><description>How to evaluate Opus 5.5 token efficiency using equivalent accepted tasks, including retries, validation and changes in work scope.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Shorter Opus reports need a different review test</title><link>https://retrivium.ai/retrospectives/opus55-shorter-reports-review-quality/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/opus55-shorter-reports-review-quality/</guid><description>Why Opus 5.5&apos;s clearer communication claim needs a reconstruction test that preserves evidence, qualifications and the reader&apos;s decision.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Action screening and model safeguards are different layers</title><link>https://retrivium.ai/retrospectives/opus55-action-screening-vs-model-policy/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/opus55-action-screening-vs-model-policy/</guid><description>How Opus 5.5&apos;s action screening, sandbox and model safeguards form separate layers with different evidence and recovery obligations.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The conditions behind Opus 5.5 cost-per-task comparisons</title><link>https://retrivium.ai/retrospectives/opus55-benchmark-cost-conditions/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/opus55-benchmark-cost-conditions/</guid><description>How to interpret Opus 5.5 cost-per-task comparisons through effort settings, harnesses and acceptance rules before testing another workload.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Batch pricing trades immediacy for scheduling flexibility</title><link>https://retrivium.ai/retrospectives/retro-openrouter-batch-capacity-flexibility/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-batch-capacity-flexibility/</guid><description>Batch inference buys scheduling flexibility by relaxing immediacy. It performs new work within a variable completion window, while response caching avoids repeating an identical answered request.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why a batch has one provider even on a multi-provider gateway</title><link>https://retrivium.ai/retrospectives/retro-openrouter-batch-single-provider/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-batch-single-provider/</guid><description>OpenRouter routes each accepted batch through one eligible provider. Per-request results improve outcome handling but do not make every row an independent provider-routing decision.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Seven-minute beta medians and a 24-hour completion window</title><link>https://retrivium.ai/retrospectives/retro-openrouter-batch-deadline-median/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-batch-deadline-median/</guid><description>The seven-minute beta median is an observed cohort statistic. The 24-hour window and the application’s deadline remain separate conditions for useful batch work.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.8Omni report: from understanding media to executing media tasks</title><link>https://retrivium.ai/retrospectives/qwen38-omni-agent-productivity-report/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/qwen38-omni-agent-productivity-report/</guid><description>The Qwen3.8Omni report shifts attention from describing media to completing media tasks, but perception and successful execution remain separate claims.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vllm-metal: why concurrent serving changed the Mac-inference question</title><link>https://retrivium.ai/retrospectives/vllm-metal-scheduler-not-just-backend/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/vllm-metal-scheduler-not-just-backend/</guid><description>vllm-metal made concurrent serving a central AppleSilicon question, rather than treating successful token generation as a complete description of deployment.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.8-Omni: media understanding and task execution</title><link>https://retrivium.ai/retrospectives/retro-qwen38-omni-report-media-planning/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-qwen38-omni-report-media-planning/</guid><description>Qwen3.8-Omni shifts attention from media perception to agent deliverables. Trace why understanding a recording and completing its requested task differ.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.8-Omni: what a technical report establishes about weight availability</title><link>https://retrivium.ai/retrospectives/retro-qwen38-omni-report-paper-availability/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-qwen38-omni-report-paper-availability/</guid><description>The Qwen3.8-Omni paper documents a research disclosure. Trace why a technical report, product interface, source framework, and checkpoint need separate evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vllm-metal unified memory: why concurrent inference needs headroom</title><link>https://retrivium.ai/retrospectives/retro-vllm-metal-unified-memory/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-vllm-metal-unified-memory/</guid><description>The vllm-metal release in context: shared memory changes placement, while concurrent requests still require an explicit budget for model state and the host.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vllm-metal attention: the boundary between reused layers and request state</title><link>https://retrivium.ai/retrospectives/retro-vllm-metal-attention-replacement/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-vllm-metal-attention-replacement/</guid><description>Why the vllm-metal announcement separates reusable token operations from request-aware attention, and how this follows earlier serving-memory research.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Harness-native training raises a transfer question</title><link>https://retrivium.ai/retrospectives/grok47-harness-native-transfer/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok47-harness-native-transfer/</guid><description>How Grok 4.7&apos;s harness-native training claim creates a transfer question for third-party tool semantics, state encoding and recovery behavior.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Longer Grok work needs verification that survives retries</title><link>https://retrivium.ai/retrospectives/grok47-long-tasks-verification/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok47-long-tasks-verification/</guid><description>Why Grok 4.7 self-verification needs evidence tied to the final artifact after retries, changed inputs and revised methods.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok 4.7: The same token rate can buy a different amount of work</title><link>https://retrivium.ai/retrospectives/grok47-same-rate-different-work/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok47-same-rate-different-work/</guid><description>Grok 4.7 retained the predecessor’s launch token rates, but longer work, tool execution and acceptance criteria can change the cost of a completed task.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok 4.7: A larger base model is not a complete architecture disclosure</title><link>https://retrivium.ai/retrospectives/grok47-bigger-base-not-architecture-proof/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok47-bigger-base-not-architecture-proof/</guid><description>What Grok 4.7’s larger-base statement establishes, and why it does not disclose parameter counts, memory requirements or the cause of every benchmark gain.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen Image2.1: transparent generation meets unified editing</title><link>https://retrivium.ai/retrospectives/qwen-image21-rgba-unification/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/qwen-image21-rgba-unification/</guid><description>Qwen Image2.1 joins creation and editing with transparent-image workflows, but preserving that capability requires more than displaying a convincing preview.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen-Image-2.1: native transparency and ordinary RGB output</title><link>https://retrivium.ai/retrospectives/retro-qwen-image21-transparent-edit/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-qwen-image21-transparent-edit/</guid><description>Qwen-Image-2.1 brings native transparent output into unified image creation. Trace the path from layered images to preserving alpha through an application.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen-Image-2.1: reference-image editing and identity</title><link>https://retrivium.ai/retrospectives/retro-qwen-image21-reference-images/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-qwen-image21-reference-images/</guid><description>Qwen-Image-2.1 expands reference-image editing. Reconstruct why multiple visual inputs require explicit evidence roles rather than a vague similarity check.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Transcribe 2.0: Noisy-audio gains need workload slices rather than one WER</title><link>https://retrivium.ai/retrospectives/grok-transcribe2-noisy-audio-slices/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-transcribe2-noisy-audio-slices/</guid><description>Grok Voice Transcribe 2.0 emphasizes noisy audio. This retrospective separates telephony, accents and spoken identifiers rather than treating one WER as universal.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Transcribe 2.0: A wrong spoken identifier can outweigh fluent transcription</title><link>https://retrivium.ai/retrospectives/grok-transcribe2-identifier-cost/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-transcribe2-identifier-cost/</guid><description>Why Grok Transcribe 2.0’s spoken-identifier focus calls for exact-value acceptance tests alongside ordinary transcript quality and average word error.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Transcribe 2.0: An API listing and a model announcement are different clocks</title><link>https://retrivium.ai/retrospectives/grok-transcribe2-listing-vs-announcement/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-transcribe2-listing-vs-announcement/</guid><description>Why an observed API catalog entry and the official Grok Transcribe 2.0 announcement date support different historical claims about model availability.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why model-server state matters more than connection counts</title><link>https://retrivium.ai/retrospectives/retro-hyperpod-routing-gpu-state/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-hyperpod-routing-gpu-state/</guid><description>HyperPod Inference Gateway brought serving-aware destination selection to a per-cluster add-on. Connection counts alone cannot describe queue and memory pressure.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The HyperPod launch did not make global routing generally available</title><link>https://retrivium.ai/retrospectives/retro-hyperpod-global-tier-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-hyperpod-global-tier-boundary/</guid><description>The HyperPod launch separated an available per-cluster gateway from a forthcoming global tier. Architecture diagrams do not override those release statuses.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Three dates behind the HyperPod Inference Gateway announcement</title><link>https://retrivium.ai/retrospectives/retro-hyperpod-release-announcement-dates/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-hyperpod-release-announcement-dates/</guid><description>September release notes, the HyperPod launch blog and a later news post date different milestones. A precise history keeps those records separate.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Build Memory: Project memory must distinguish conventions from temporary state</title><link>https://retrivium.ai/retrospectives/grok-memory-convention-vs-transient-state/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-memory-convention-vs-transient-state/</guid><description>How Grok Build memory makes the distinction between durable project conventions and temporary task state a practical engineering boundary.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Build Memory: Background memory notes need an inspectable review surface</title><link>https://retrivium.ai/retrospectives/grok-memory-note-review/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-memory-note-review/</guid><description>Why Grok Build’s background-written memory notes need an inspectable review surface, and how visible storage differs from verified memory content.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Build Memory: A correct memory note can become wrong after a repository change</title><link>https://retrivium.ai/retrospectives/grok-memory-repository-revision/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-memory-repository-revision/</guid><description>How a correct Grok Build memory note can become obsolete after a repository revision, and why project memory needs a relationship to current source evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>From a Rubin roadmap to a multi-rack cluster</title><link>https://retrivium.ai/retrospectives/retro-rubin-rack-to-cluster-milestone/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-rubin-rack-to-cluster-milestone/</guid><description>CoreWeave’s Rubin chronology moves from planned adoption to a multi-rack bring-up. The milestone advances system evidence while leaving workload qualification distinct.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why object-storage changes accompanied CoreWeave’s Rubin cluster</title><link>https://retrivium.ai/retrospectives/retro-rubin-storage-locality-announcement/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-rubin-storage-locality-announcement/</guid><description>CoreWeave’s storage and Rubin announcements meet at artifact delivery. Write acceleration, model materialization and archive retention improve different stages of a workload lifecycle.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Cluster bring-up versus readiness for a specific inference workload</title><link>https://retrivium.ai/retrospectives/retro-rubin-bringup-customer-readiness/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-rubin-bringup-customer-readiness/</guid><description>CoreWeave’s multi-rack milestone establishes system progress. Workload readiness still concerns a named artifact, software combination, execution shape and request mix.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why multi-rack Rubin bring-up makes failure boundaries a system question</title><link>https://retrivium.ai/retrospectives/retro-rubin-multirack-failure-domain/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-rubin-multirack-failure-domain/</guid><description>Multi-rack Rubin deployment creates placement choices with different failure dependencies. Recovery scope follows the application’s cooperating set and shared services, not rack count alone.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A Blackwell desktop bundle is not a general GPU instance</title><link>https://retrivium.ai/retrospectives/retro-workspaces-g7-service-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-workspaces-g7-service-boundary/</guid><description>Graphics G7 brought Blackwell to WorkSpaces Personal and Core. Desktop bundles, application fleets and general GPU instances retain different operating boundaries.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What 32 GB per GPU changes for a remote graphics project</title><link>https://retrivium.ai/retrospectives/retro-workspaces-g7-scene-memory/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-workspaces-g7-scene-memory/</guid><description>WorkSpaces G7 specifies 32 GB per GPU. Scene residency, temporary buffers and multi-device behavior determine whether that budget suits a graphics project.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AlwaysOn and AutoStop belong in the workstation migration decision</title><link>https://retrivium.ai/retrospectives/retro-workspaces-g7-desktop-lifecycle/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-workspaces-g7-desktop-lifecycle/</guid><description>The G7 desktop release included AlwaysOn and AutoStop. Workstation migration therefore requires a session-lifecycle decision alongside GPU selection.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Parallel reasoning changes what waiting sounds like</title><link>https://retrivium.ai/retrospectives/live38-parallel-reasoning-dialogue/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/live38-parallel-reasoning-dialogue/</guid><description>How Gemini 3.8 Live parallel reasoning changes progress narration, and why useful dialogue must remain separate from supported completion.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Live and Extended Thinking solve different latency choices</title><link>https://retrivium.ai/retrospectives/live38-variant-task-choice/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/live38-variant-task-choice/</guid><description>How to choose between Gemini 3.8 Live and Extended Thinking using task depth, acknowledgement timing and supported-resolution evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A spoken correction can invalidate pending tool work</title><link>https://retrivium.ai/retrospectives/live38-tool-cancellation-intent/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/live38-tool-cancellation-intent/</guid><description>Why Gemini 3.8 Live corrections need separate handling for obsolete tool results, cancellation attempts and already committed consequences.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Live visual grounding still has a context-age problem</title><link>https://retrivium.ai/retrospectives/live38-audio-visual-context-age/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/live38-audio-visual-context-age/</guid><description>Why Gemini 3.8 Live visual grounding must distinguish image comprehension from the age and applicability of the scene behind a spoken instruction.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why NUMA topology became part of managed Slurm placement</title><link>https://retrivium.ai/retrospectives/retro-aws-pcs-numa-placement/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-aws-pcs-numa-placement/</guid><description>AWS PCS exposed NUMA topology and GPU affinity to managed Slurm placement. The change makes locality visible without promising a universal application speedup.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>MIG partitions became scheduler resources in AWS PCS</title><link>https://retrivium.ai/retrospectives/retro-aws-pcs-mig-allocation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-aws-pcs-mig-allocation/</guid><description>AWS PCS added independent scheduling of compatible MIG instances. Hardware support, partition profiles and application memory remain separate constraints.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Custom GRES as an escape hatch from automatic hardware discovery</title><link>https://retrivium.ai/retrospectives/retro-aws-pcs-custom-gres-escape-hatch/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-aws-pcs-custom-gres-escape-hatch/</guid><description>Custom GRES lets AWS PCS administrators express resources and topology beyond automatic discovery. An explicit declaration still needs to match real hardware.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The Agents API moved the harness into the service boundary</title><link>https://retrivium.ai/retrospectives/agents-api-managed-harness-shift/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agents-api-managed-harness-shift/</guid><description>The Agents API beta moved orchestration into a managed service; applications still own task identity, access, artifact handling and acceptance.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A durable agent session is more than a saved chat</title><link>https://retrivium.ai/retrospectives/agents-api-durable-session-meaning/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agents-api-durable-session-meaning/</guid><description>Durable Agents API sessions preserve a work context, but applications must distinguish task records, turn state, artifacts and acknowledgments during recovery.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Hosted and self-hosted environments after the Agents API beta</title><link>https://retrivium.ai/retrospectives/agents-api-environment-choice/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agents-api-environment-choice/</guid><description>The Agents API added environment choices; compare data access, dependency ownership and artifact behavior before attributing outcomes to model intelligence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why agent API success still needs a task acceptance artifact</title><link>https://retrivium.ai/retrospectives/agents-api-acceptance-artifacts/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agents-api-acceptance-artifacts/</guid><description>The Agents API can report a completed run while a private task remains incomplete; preserve an artifact with coverage, source identity and acceptance criteria.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Full duplex changed the voice-agent state machine</title><link>https://retrivium.ai/retrospectives/live-api-full-duplex-state-machine/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/live-api-full-duplex-state-machine/</guid><description>Why the GPT-Live-1 API release changes voice-agent state ownership, and how concurrent speech exposes cancellation and stale-result boundaries.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Backend delegation separates conversation from slow reasoning</title><link>https://retrivium.ai/retrospectives/live-api-backend-delegation-latency/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/live-api-backend-delegation-latency/</guid><description>How backend reasoning delegation changes a live voice workflow, with separate acknowledgement, resolution and stale-context acceptance criteria.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why voice minutes and backend tokens need separate budgets</title><link>https://retrivium.ai/retrospectives/live-api-audio-clock-billing/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/live-api-audio-clock-billing/</guid><description>Why the GPT-Live-1 launch price describes a voice layer rather than total agent cost, and how to account for delegated reasoning separately.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Interruption quality needs a conversation fixture</title><link>https://retrivium.ai/retrospectives/live-api-interruption-acceptance/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/live-api-interruption-acceptance/</guid><description>Interruption tests for GPT-Live-1 should distinguish thinking pauses, acknowledgements, corrections and task outcomes rather than measuring latency alone.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DeepSeek V4.1 Flash: why the September release changed more than a model name</title><link>https://retrivium.ai/retrospectives/deepseek41-asymmetric-release-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/deepseek41-asymmetric-release-boundary/</guid><description>DeepSeek V4.1 Flash changes more than the name sent to an API: its asymmetric execution and native visual path create a new model contract.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing DeepSeek-V4.1-Flash: input and output execution roles</title><link>https://retrivium.ai/retrospectives/retro-deepseek41-flash-asymmetric-work/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-deepseek41-flash-asymmetric-work/</guid><description>DeepSeekV4.1Flash&apos;s asymmetric encoder-decoder separates input and output roles, so one generic parameter or speed label cannot explain every workload bottleneck.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing DeepSeek-V4.1-Flash: API aliases and source reproducibility</title><link>https://retrivium.ai/retrospectives/retro-deepseek41-flash-alias-lifecycle/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-deepseek41-flash-alias-lifecycle/</guid><description>DeepSeekV4.1Flash&apos;s API transition shows why a stable client-side model name is not sufficient provenance for comparing answers across a release boundary.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing DeepSeek-V4.1-Flash: native vision and historical cache comparisons</title><link>https://retrivium.ai/retrospectives/retro-deepseek41-flash-vision-cache/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-deepseek41-flash-vision-cache/</guid><description>DeepSeekV4.1Flash&apos;s architectural cache claims do not describe the entire memory footprint of a multimodal request, so historical comparisons need a clearly defined allocation boundary.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Residency starts at gateway decryption, not only at the GPU</title><link>https://retrivium.ai/retrospectives/retro-openrouter-residency-gateway-decryption/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-residency-gateway-decryption/</guid><description>OpenRouter’s regional route includes gateway decryption as well as eligible inference location. Customer deployment regions and retention remain separately scoped parts of the path.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why regional inference can fail with an otherwise valid model</title><link>https://retrivium.ai/retrospectives/retro-openrouter-regional-fail-closed/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-regional-fail-closed/</guid><description>A valid global model may have no eligible regional endpoint. OpenRouter’s documented regional 404 preserves the location condition instead of silently sending the request elsewhere.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A model’s country of origin is not its inference location</title><link>https://retrivium.ai/retrospectives/retro-openrouter-model-origin-hosting/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-model-origin-hosting/</guid><description>OpenRouter’s regional announcement separates model provenance from serving location. The creator, operator, gateway and data policy are distinct parts of a processing description.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why the Finland expansion combined nuclear, wind and storage</title><link>https://retrivium.ai/retrospectives/retro-finland-energy-portfolio/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-finland-energy-portfolio/</guid><description>The Finland portfolio combined nuclear life extension, wind, storage and exploratory flexibility. Their different grid functions and rollout states should remain explicit.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Keeping a nuclear plant online is different from adding a new plant</title><link>https://retrivium.ai/retrospectives/retro-finland-life-extension-accounting/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-finland-life-extension-accounting/</guid><description>Loviisa life extension preserves a future supply path rather than creating a new reactor. Its contribution depends on the retirement counterfactual being changed.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A hypothetical siting model is not a realized electricity-price result</title><link>https://retrivium.ai/retrospectives/retro-finland-siting-study-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-finland-siting-study-boundary/</guid><description>The Finland siting argument used commissioned hypothetical modeling. Scenario results can guide planning without being reported as realized national electricity-price savings.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Demand-response exploration does not make every inference job interruptible</title><link>https://retrivium.ai/retrospectives/retro-finland-flexibility-compute/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-finland-flexibility-compute/</guid><description>Finland&apos;s demand-response work was exploratory. Movable inference demand still requires a workload policy for deadlines, state preservation, restart and side effects.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CUDA 13.4: Functional Rubin preview is not a blanket production-support claim</title><link>https://retrivium.ai/retrospectives/retro-cuda134-rubin-preview/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-cuda134-rubin-preview/</guid><description>CUDA 13.4 introduces functional Rubin preview support after the platform roadmap. Why porting access and production qualification belong to different milestones.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CUDA 13.4: MPS management controls and MIG isolation remain different mechanisms</title><link>https://retrivium.ai/retrospectives/retro-cuda134-mps-control-isolation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-cuda134-mps-control-isolation/</guid><description>CUDA 13.4 expands MPS management after earlier GPU partition controls. How to distinguish programmable sharing policy from a MIG hardware-isolation boundary.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CUDA 13.4: Separating driver packaging makes an implicit dependency explicit</title><link>https://retrivium.ai/retrospectives/retro-cuda134-driver-toolkit-packaging/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-cuda134-driver-toolkit-packaging/</guid><description>CUDA 13.4 separates driver and toolkit installers. How successive hardware and software releases made installation ownership a visible compatibility question.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CUDA 13.4: Windows on Arm adds an operating-system axis to CUDA qualification</title><link>https://retrivium.ai/retrospectives/retro-cuda134-arm-os-matrix/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-cuda134-arm-os-matrix/</guid><description>CUDA 13.4 adds Windows on Arm after earlier Linux Arm and GPU-platform work. Why a CPU architecture does not determine an application’s operating-system support.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Images 2.5 and the problem of preserving edits across turns</title><link>https://retrivium.ai/retrospectives/images25-editing-state-continuity/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/images25-editing-state-continuity/</guid><description>Images 2.5 strengthened iterative editing, but continuity still requires a governing reference, protected properties and versioned acceptance after each edit.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Flare and Sunburst need different creative acceptance checks</title><link>https://retrivium.ai/retrospectives/images25-flare-sunburst-acceptance/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/images25-flare-sunburst-acceptance/</guid><description>Flare and Sunburst target different image workflows; compare exploratory variation and precise corrections under separate artifact acceptance criteria.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Image provenance is not a reliable model-selector label</title><link>https://retrivium.ai/retrospectives/images25-provenance-vs-model-selection/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/images25-provenance-vs-model-selection/</guid><description>Images 2.5 offers distinct API variants; preserve request identity, artifact identity and the documented meaning of provenance labels when attributing outputs.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Sketches and comments made image intent more explicit</title><link>https://retrivium.ai/retrospectives/images25-sketch-comments-workflow/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/images25-sketch-comments-workflow/</guid><description>How sketches and image comments changed edit review in Images 2.5, and why spatial scope still needs a reference revision and preservation criteria.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why Muse&apos;s dedicated computer changed the personal-agent boundary</title><link>https://retrivium.ai/retrospectives/muse-dedicated-computer-personal-agent/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/muse-dedicated-computer-personal-agent/</guid><description>Why Muse&apos;s dedicated computer makes browser state and retained artifacts part of the personal-agent contract rather than a chat-only capability.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A personal goal does not define every background permission</title><link>https://retrivium.ai/retrospectives/muse-goals-vs-background-authority/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/muse-goals-vs-background-authority/</guid><description>How Muse&apos;s personal-goal framing separates supported preparation, connected access and exact actions without turning a broad objective into unlimited authority.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The gap between Spark&apos;s model capability and Muse&apos;s useful work</title><link>https://retrivium.ai/retrospectives/muse-model-to-product-gap/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/muse-model-to-product-gap/</guid><description>Why Muse&apos;s launch should be evaluated as an objective-to-outcome product loop rather than inferred from Spark&apos;s planning capability alone.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CUDA Rust offers a language choice and a separate programming-model choice</title><link>https://retrivium.ai/retrospectives/retro-cuda-rust-two-models/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-cuda-rust-two-models/</guid><description>NVIDIA introduced SIMT and tile-oriented CUDA Rust tracks. Language choice, programming-model responsibility and production readiness remain separate decisions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What Rust ownership catches at a GPU launch boundary</title><link>https://retrivium.ai/retrospectives/retro-cuda-rust-borrow-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-cuda-rust-borrow-boundary/</guid><description>Rust ownership can catch a bounded class of GPU programming mistakes. It does not establish numerical correctness, complete synchronization safety or production maturity.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why NVIDIA called its Rust GPU tracks early-stage</title><link>https://retrivium.ai/retrospectives/retro-cuda-rust-alpha-production/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-cuda-rust-alpha-production/</guid><description>NVIDIA explicitly labeled CUDA Rust tracks early-stage. Runnable examples establish an experimental path rather than complete APIs or production readiness.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Tile abstraction trades explicit thread control for compiler responsibility</title><link>https://retrivium.ai/retrospectives/retro-cuda-rust-abstraction-kernel-control/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-cuda-rust-abstraction-kernel-control/</guid><description>Tile-oriented CUDA Rust shifts mapping responsibility toward the compiler. That abstraction choice is separate from language choice and does not imply a universal speed advantage.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How AlphaGenome Atlas moved inference from request time to publication time</title><link>https://retrivium.ai/retrospectives/alphagenome-atlas-precomputed-inference/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/alphagenome-atlas-precomputed-inference/</guid><description>How AlphaGenome Atlas illustrates a shift from interactive inference to precomputed scientific reference data, and what that changes in operations.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why AlphaGenome Atlas needs explanations alongside rankings</title><link>https://retrivium.ai/retrospectives/alphagenome-atlas-ranking-explanation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/alphagenome-atlas-ranking-explanation/</guid><description>A retrospective on AlphaGenome Atlas and why a useful variant ranking needs inspectable reasons, calibration and a question-specific interpretation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How a model became a shared scientific reference with AlphaGenome Atlas</title><link>https://retrivium.ai/retrospectives/alphagenome-atlas-accessible-science/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/alphagenome-atlas-accessible-science/</guid><description>How AlphaGenome Atlas follows the path from specialized predictive models to shared research resources, where accessibility and traceability change reuse.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why a predictive atlas must version its data with its model</title><link>https://retrivium.ai/retrospectives/alphagenome-atlas-model-data-versioning/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/alphagenome-atlas-model-data-versioning/</guid><description>Why a predictive reference such as AlphaGenome Atlas needs linked model and dataset versions, reproducible snapshots and explicit refresh semantics.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why Astra made the API contract part of the model upgrade</title><link>https://retrivium.ai/retrospectives/astra-responses-tool-contract/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/astra-responses-tool-contract/</guid><description>Astra made tool integration part of the model migration: examine request items, execution results and continuation before comparing output quality.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Astra and the shift from answering to completing long work</title><link>https://retrivium.ai/retrospectives/astra-long-running-work-completion/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/astra-long-running-work-completion/</guid><description>Astra arrived after execution and compaction primitives; the useful question is whether long work leaves evidence another reviewer can recover.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The controls Astra removed, and what a migration must preserve</title><link>https://retrivium.ai/retrospectives/astra-reasoning-control-compatibility/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/astra-reasoning-control-compatibility/</guid><description>Astra removed familiar sampling controls; a migration must preserve the task intention rather than silently translate unrelated settings.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What the Astra launch can and cannot prove about a workflow</title><link>https://retrivium.ai/retrospectives/astra-launch-evidence-vs-task-acceptance/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/astra-launch-evidence-vs-task-acceptance/</guid><description>Astra launch evidence can justify a local trial, but workload conditions and acceptance criteria determine what the trial can actually establish.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>An acquisition agreement and an open-platform promise answer different questions</title><link>https://retrivium.ai/retrospectives/retro-nvidia-hf-open-platform/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nvidia-hf-open-platform/</guid><description>The NVIDIA–Hugging Face agreement and its openness promise concern different claims. Closing status and future platform behavior each require their own evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why model distribution became strategically adjacent to compute</title><link>https://retrivium.ai/retrospectives/retro-nvidia-hf-distribution-compute/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nvidia-hf-distribution-compute/</guid><description>Model discovery and execution are complementary functions in the NVIDIA–Hugging Face chronology. Their strategic adjacency does not establish mandatory hardware lock-in.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What NVIDIA explicitly said about other clouds and accelerators</title><link>https://retrivium.ai/retrospectives/retro-nvidia-hf-multicloud-commitment/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nvidia-hf-multicloud-commitment/</guid><description>NVIDIA promised continued cloud and accelerator choice in the Hugging Face announcement. That commitment is separate from model licenses, source access and future governance.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The documented path from a compute partnership to an acquisition agreement</title><link>https://retrivium.ai/retrospectives/retro-nvidia-hf-partnership-acquisition-sequence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nvidia-hf-partnership-acquisition-sequence/</guid><description>The documented NVIDIA–Hugging Face chronology supports strategic continuity, not inevitability. Partnership, provider breadth and acquisition agreement have different evidentiary roles.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How WeatherNext 3 made observation freshness part of model design</title><link>https://retrivium.ai/retrospectives/weathernext-3-observation-to-forecast/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/weathernext-3-observation-to-forecast/</guid><description>How the route from GraphCast and GenCast to WeatherNext 3 made observation freshness an architectural question rather than a final dashboard detail.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why sharper weather forecasts change the serving workload</title><link>https://retrivium.ai/retrospectives/weathernext-3-resolution-serving/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/weathernext-3-resolution-serving/</guid><description>Why the move toward sharper forecasts in WeatherNext 3 changes output volume, data movement and workload design beyond a model-speed comparison.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How weather AI reached the decision problem beyond average accuracy</title><link>https://retrivium.ai/retrospectives/weathernext-3-probability-decisions/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/weathernext-3-probability-decisions/</guid><description>How the path to WeatherNext 3 clarifies the difference between an accurate weather prediction and a useful decision under uncertainty.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why learned weather models still need physical consistency checks</title><link>https://retrivium.ai/retrospectives/weathernext-3-physical-consistency/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/weathernext-3-physical-consistency/</guid><description>Why the progression toward WeatherNext 3 leaves physical consistency, coupled variables and out-of-distribution tests central to learned forecasting.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Spark 1.3 and the challenge of several workflows in one thread</title><link>https://retrivium.ai/retrospectives/spark13-long-thread-workflows/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/spark13-long-thread-workflows/</guid><description>Why Spark 1.3 long-thread evaluation needs workflow identity and dependency checks when a user steers several unfinished deliverables.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Spark 1.3 shows how API and coding-product feedback meet</title><link>https://retrivium.ai/retrospectives/spark13-api-product-feedback-loop/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/spark13-api-product-feedback-loop/</guid><description>How Spark&apos;s model, coding-product and API release sequence helps separate feedback about intelligence from feedback about harnesses and integration.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Max reasoning in Spark 1.3 is a configuration to evaluate</title><link>https://retrivium.ai/retrospectives/spark13-max-reasoning-acceptance/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/spark13-max-reasoning-acceptance/</guid><description>How to evaluate Spark 1.3 max reasoning against resolvable uncertainty, missing evidence and supported task completion rather than answer length.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Flash 3.8 shows why a diligent model may spend more tokens</title><link>https://retrivium.ai/retrospectives/flash38-extra-work-cost/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/flash38-extra-work-cost/</guid><description>Why Gemini 3.8 Flash&apos;s additional diligence should be evaluated as changed work quantity alongside rates, tool waiting and accepted task outcomes.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Flash and Flash Cyber need separate deployment descriptions</title><link>https://retrivium.ai/retrospectives/flash38-cyber-deployment-separation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/flash38-cyber-deployment-separation/</guid><description>Why Gemini 3.8 Flash and Flash Cyber need separate capability, access-route and authorized-task descriptions in deployment comparisons.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Long-horizon software work needs intermediate checkpoints</title><link>https://retrivium.ai/retrospectives/flash38-long-horizon-software-checkpoints/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/flash38-long-horizon-software-checkpoints/</guid><description>Why Gemini 3.8 Flash long-horizon coding needs source-state checkpoints and validation tied to the delivered patch rather than an earlier success.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introductory Flash pricing is a historical condition</title><link>https://retrivium.ai/retrospectives/flash38-introductory-price-history/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/flash38-introductory-price-history/</guid><description>Why Gemini 3.8 Flash introductory pricing belongs in a dated adoption record rather than a timeless claim about task economics.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Fable 5.1 made thinking history a compatibility boundary</title><link>https://retrivium.ai/retrospectives/fable51-reasoning-history-compatibility/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/fable51-reasoning-history-compatibility/</guid><description>Why Fable 5.1 thinking-history constraints turn a model upgrade into state migration, with a replay matrix for edited conversations and fallback.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why the Fable 5.1 forced-tool change matters to orchestration</title><link>https://retrivium.ai/retrospectives/fable51-forced-tools-contract/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/fable51-forced-tools-contract/</guid><description>How Fable 5.1&apos;s forced-tool breaking change exposes routing, clarification and execution decisions that an application still needs to own.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What cheaper Fable cache reads changed in long agent loops</title><link>https://retrivium.ai/retrospectives/fable51-cache-reads-agent-loops/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/fable51-cache-reads-agent-loops/</guid><description>Why cheaper Fable 5.1 cache reads change long-run cost composition without proving cache hits, fewer iterations or lower cost per accepted task.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>One frontier release, two access surfaces</title><link>https://retrivium.ai/retrospectives/fable51-two-access-surfaces/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/fable51-two-access-surfaces/</guid><description>Why the paired Fable 5.1 and Mythos 5.1 release needs separate capability, availability and tested-deployment claims in model-selection records.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Agentic video replaced uniform sampling with evidence seeking</title><link>https://retrivium.ai/retrospectives/agentic-video-search-vs-sampling/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agentic-video-search-vs-sampling/</guid><description>How Gemini agentic video changes evidence acquisition, with explicit checks for inspected intervals and search-hypothesis blind spots.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Video token savings need a retained-evidence denominator</title><link>https://retrivium.ai/retrospectives/agentic-video-token-saving-coverage/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agentic-video-token-saving-coverage/</guid><description>Why agentic-video token savings need accepted answers, required-event coverage and complete attempts as their comparison boundary.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>When the transcript and frame describe different events</title><link>https://retrivium.ai/retrospectives/agentic-video-transcript-visual-disagreement/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agentic-video-transcript-visual-disagreement/</guid><description>Why Gemini agentic video must preserve temporal relationships when combining transcript passages, narration and visual events.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Not finding an event is not proof it never happened</title><link>https://retrivium.ai/retrospectives/agentic-video-negative-evidence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/agentic-video-negative-evidence/</guid><description>Why Gemini agentic video&apos;s not-found results need coverage-aware wording before they become claims that an event never occurred.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>HUMAIN: live compute is a different milestone from a gigawatt plan</title><link>https://retrivium.ai/retrospectives/retro-humain-live-versus-gigawatt-plan/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-humain-live-versus-gigawatt-plan/</guid><description>HUMAIN’s August update combines live Instinct systems with future expansion targets. The operating milestone, scheduled power and workload allocation need separate records.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why HUMAIN’s GPU-as-a-service announcement includes its network fabric</title><link>https://retrivium.ai/retrospectives/retro-humain-gpu-fabric-platform/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-humain-gpu-fabric-platform/</guid><description>HUMAIN’s update includes Cisco fabric as part of the live compute platform. A useful interpretation maps artifact, execution, client and management traffic separately.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Sovereign AI moves from investment language to operating responsibility</title><link>https://retrivium.ai/retrospectives/retro-humain-sovereign-ai-operation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-humain-sovereign-ai-operation/</guid><description>HUMAIN’s live-system milestone shifts attention from investment scope to operating responsibility: access, maintenance, recovery and application acceptance need accountable owners.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Sovereign AI capacity needs an operational boundary beyond location</title><link>https://retrivium.ai/retrospectives/retro-humain-sovereign-operations-stack/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-humain-sovereign-operations-stack/</guid><description>HUMAIN’s local compute milestone invites an application-level boundary map. Requests, artifacts, diagnostics, administration and recovery can follow different paths.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.8Next report: the state that active-parameter counts omit</title><link>https://retrivium.ai/retrospectives/qwen38-next-report-off-accelerator-state/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/qwen38-next-report-off-accelerator-state/</guid><description>The Qwen3.8Next report makes off-accelerator state part of the inference question, so activated parameters alone cannot describe deployment requirements.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>On the Design of Qwen3.8-Next Architecture: off-accelerator n-gram tables</title><link>https://retrivium.ai/retrospectives/retro-qwen38next-paper-ngram-residency/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-qwen38next-paper-ngram-residency/</guid><description>The Qwen3.8-Next report places n-gram tables outside the accelerator. Trace why active parameters no longer describe the complete inference memory path.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>On the Design of Qwen3.8-Next Architecture: architecture ablations and deployment conclusions</title><link>https://retrivium.ai/retrospectives/retro-qwen38next-paper-ablation-reading/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-qwen38next-paper-ablation-reading/</guid><description>Qwen3.8-Next architecture ablations explain research choices. Learn why pretraining evidence cannot directly establish production serving performance.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Scene extension turns continuity into a reviewable constraint</title><link>https://retrivium.ai/retrospectives/omni11-extension-continuity/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/omni11-extension-continuity/</guid><description>Why Omni 1.1 scene extension should be reviewed for physical and narrative continuity at the seam rather than attractive extra footage alone.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>First and last frames do not specify the entire transition</title><link>https://retrivium.ai/retrospectives/omni11-endpoints-transition-path/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/omni11-endpoints-transition-path/</guid><description>Why Omni 1.1 first-and-last-frame interpolation needs path constraints that distinguish camera motion, object motion and continuity between anchors.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A resolution option is not a native-detail guarantee</title><link>https://retrivium.ai/retrospectives/omni11-resolution-upscaling-meaning/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/omni11-resolution-upscaling-meaning/</guid><description>Why Omni 1.1 4K upscaling should be evaluated separately from native detail, content fidelity and temporal consistency in a delivered video.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Cheap video previews need a deliberate final-artifact handoff</title><link>https://retrivium.ai/retrospectives/omni11-prototype-final-artifact/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/omni11-prototype-final-artifact/</guid><description>How Omni 1.1 lightweight previews need a clear creative-selection record and a separate final-artifact acceptance pass.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How hidden tests became an infrastructure problem for AI evaluation</title><link>https://retrivium.ai/retrospectives/double-blind-ai-hidden-test/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/double-blind-ai-hidden-test/</guid><description>How the double-blind AI evaluation pilot follows the history of broader benchmarks and turns hidden test integrity into a systems problem.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why confidential evaluation must protect both models and questions</title><link>https://retrivium.ai/retrospectives/double-blind-ai-model-sovereignty/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/double-blind-ai-model-sovereignty/</guid><description>Why double-blind AI evaluation has two confidentiality objectives: protecting proprietary model artifacts and the evaluator’s undisclosed questions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How attestation changed the evidence behind an AI benchmark</title><link>https://retrivium.ai/retrospectives/double-blind-ai-attestation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/double-blind-ai-attestation/</guid><description>How the double-blind evaluation pilot makes execution attestation relevant to benchmark evidence, while keeping configuration proof distinct from scientific validity.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why double-blind execution cannot repair a weak benchmark</title><link>https://retrivium.ai/retrospectives/double-blind-ai-benchmark-design/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/double-blind-ai-benchmark-design/</guid><description>Why a double-blind evaluation process cannot repair an unrepresentative benchmark, and how to keep execution integrity separate from task validity.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Smart transcription changes the boundary of a quotation</title><link>https://retrivium.ai/retrospectives/transcribe35-smart-cleanup-evidence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/transcribe35-smart-cleanup-evidence/</guid><description>Why Gemini 3.5 Transcribe cleanup should be treated as a representation choice when readable notes and exact quotations have different obligations.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Live and recorded transcription are different contracts</title><link>https://retrivium.ai/retrospectives/transcribe35-live-recorded-contracts/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/transcribe35-live-recorded-contracts/</guid><description>Why Gemini 3.5 Transcribe&apos;s live and recorded paths need different completion, input-identity and downstream-use rules.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Custom vocabulary needs an audio-backed correction test</title><link>https://retrivium.ai/retrospectives/transcribe35-vocabulary-scope/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/transcribe35-vocabulary-scope/</guid><description>How to test Gemini 3.5 Transcribe vocabulary hints using contrasting audio, corrected recognition and false substitutions rather than expected spellings alone.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Speaker labels and word times carry different uncertainty</title><link>https://retrivium.ai/retrospectives/transcribe35-speaker-timestamp-trust/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/transcribe35-speaker-timestamp-trust/</guid><description>Why Gemini 3.5 Transcribe words, speaker labels and timestamps need separate acceptance checks before they are combined into an action record.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Moving the memory controller changes more than a memory specification</title><link>https://retrivium.ai/retrospectives/retro-nvhbm-controller-placement/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nvhbm-controller-placement/</guid><description>NVHBM moves memory-controller functionality into the HBM base die. The change shifts integration responsibilities while partner qualification remains future work.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Custom XPU choice still depends on memory qualification</title><link>https://retrivium.ai/retrospectives/retro-nvhbm-custom-xpu-qualification/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nvhbm-custom-xpu-qualification/</guid><description>NVHBM extends modular infrastructure for custom XPUs. Reusing memory functionality can narrow design work while final combinations still require qualification.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>HBM power is not whole-inference energy</title><link>https://retrivium.ai/retrospectives/retro-nvhbm-component-system-energy/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nvhbm-component-system-energy/</guid><description>NVHBM component power claims do not directly establish whole-inference energy savings. A service result needs system scope, duration and useful-output accounting.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why custom accelerators can share a rack architecture without becoming identical</title><link>https://retrivium.ai/retrospectives/retro-nvhbm-hyperscaler-common-rack/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nvhbm-hyperscaler-common-rack/</guid><description>Fusion and NVHBM can share infrastructure around specialized accelerators. Architectural interoperability does not imply identical instruction sets or portable model binaries.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Two million planned GPUs are a delivery window, not an inventory snapshot</title><link>https://retrivium.ai/retrospectives/retro-aws-two-million-delivery-window/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-aws-two-million-delivery-window/</guid><description>The AWS–NVIDIA plan spans 2027–2028. Its additional GPU count describes a future delivery flow rather than current region-level inventory or customer allocation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why AI capacity announcements cannot be added without checking overlap</title><link>https://retrivium.ai/retrospectives/retro-aws-capacity-roadmap-overlap/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-aws-capacity-roadmap-overlap/</guid><description>Capacity headlines need scope and timing before aggregation. The AWS expansion count cannot be added to every related roadmap without evidence about overlap.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A heterogeneous GPU roadmap needs common infrastructure as well as chips</title><link>https://retrivium.ai/retrospectives/retro-aws-common-infrastructure-heterogeneous/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-aws-common-infrastructure-heterogeneous/</guid><description>The AWS–NVIDIA roadmap spans heterogeneous generations and surrounding infrastructure. Useful service delivery depends on networking, isolation and software as well as GPU supply.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A hyperscaler’s deployment plan does not reserve capacity for an application</title><link>https://retrivium.ai/retrospectives/retro-aws-public-plan-customer-allocation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-aws-public-plan-customer-allocation/</guid><description>The AWS expansion is aggregate future supply. An application still needs a supported shape, location, account conditions and a usable allocation window.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM5.3 Flash: why the name hides a different base architecture</title><link>https://retrivium.ai/retrospectives/glm53-flash-new-base-chronology/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/glm53-flash-new-base-chronology/</guid><description>GLM5.3 Flash should be understood as a new base and serving contract, rather than a smaller numerical representation of the preceding flagship.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM-5.3-Flash: hybrid attention and serving assumptions</title><link>https://retrivium.ai/retrospectives/retro-glm53-flash-hybrid-state/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-glm53-flash-hybrid-state/</guid><description>GLM5.3Flash&apos;s newly trained hybrid base changes serving assumptions, so the Flash label is not a reason to copy the larger model&apos;s state handling unchanged.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM-5.3-Flash: native visual input and model lineage</title><link>https://retrivium.ai/retrospectives/retro-glm53-flash-visual-base/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-glm53-flash-visual-base/</guid><description>GLM5.3Flash&apos;s native visual path belongs to a newly trained multimodal base, so it should not be described as a processor attached to an unchanged earlier text checkpoint.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM-5.3-Flash: anonymous feedback before a named release</title><link>https://retrivium.ai/retrospectives/retro-glm53-flash-preview-feedback/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-glm53-flash-preview-feedback/</guid><description>Anonymous feedback around a model preview can reveal useful task cases, but it cannot become a controlled GLM5.3Flash benchmark merely after the model receives a public name.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Shared Cowork memory changed the handoff between conversation and work</title><link>https://retrivium.ai/retrospectives/cowork-memory-cross-surface-continuity/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/cowork-memory-cross-surface-continuity/</guid><description>How shared Claude and Cowork memory reduces repeated briefing while remaining distinct from current evidence and exact task artifacts.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Editable topics made memory an inspectable product object</title><link>https://retrivium.ai/retrospectives/cowork-memory-editable-topics/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/cowork-memory-editable-topics/</guid><description>How editable Claude memory topics turn repeated answer corrections into inspectable changes to persistent assumptions, with clear limits on retroactivity.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Global memory and project evidence should remain distinguishable</title><link>https://retrivium.ai/retrospectives/cowork-memory-project-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/cowork-memory-project-boundary/</guid><description>Why shared Cowork memory should distinguish portable writing preferences from project-specific definitions and source-bound factual claims.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Memory defaults change what a continuation can assume</title><link>https://retrivium.ai/retrospectives/cowork-memory-sensitive-topic-defaults/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/cowork-memory-sensitive-topic-defaults/</guid><description>How sensitive-topic memory settings change continuation inputs, and why missing context should be handled explicitly rather than invented.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Granite4.2: why family naming is insufficient to infer architecture</title><link>https://retrivium.ai/retrospectives/granite42-dense-reasoning-family-change/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/granite42-dense-reasoning-family-change/</guid><description>Granite4.2 illustrates why a model-family name is not a complete architecture specification.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Granite4.2 brings native reasoning to enterprise agents: dense models after hybrid predecessors</title><link>https://retrivium.ai/retrospectives/retro-ibm-granite42-dense-family/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-ibm-granite42-dense-family/</guid><description>Granite4.2&apos;s dense architecture means that a family name cannot determine serving requirements, especially when an operator&apos;s earlier Granite configuration used different internal assumptions.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Granite4.2 brings native reasoning to enterprise agents: native reasoning and enterprise parsers</title><link>https://retrivium.ai/retrospectives/retro-ibm-granite42-native-thinking/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-ibm-granite42-native-thinking/</guid><description>Granite4.2&apos;s native reasoning makes answer interpretation an enterprise integration question, because a capable response still needs an explicit boundary before it becomes an accepted structured result.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Granite4.2 brings native reasoning to enterprise agents: multi-stage post-training and causal attribution</title><link>https://retrivium.ai/retrospectives/retro-ibm-granite42-multistage-rl/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-ibm-granite42-multistage-rl/</guid><description>Granite4.2 changed post-training alongside enterprise reasoning. Reconstruct why the release invites a causal question that a headline benchmark cannot resolve.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Groq 3 LPX separates token-generation specialization from general compute</title><link>https://retrivium.ai/retrospectives/retro-groq-lpx-decode-specialization/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-groq-lpx-decode-specialization/</guid><description>Groq 3 LPX was announced as a specialized generation extension to Rubin. Its role is best evaluated through phase placement and the surrounding system path.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Full production hardware is not the same milestone as a public API</title><link>https://retrivium.ai/retrospectives/retro-groq-lpx-production-api/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-groq-lpx-production-api/</guid><description>Groq 3 LPX production and Nebius integration are different milestones. A hardware release does not by itself establish a generally available customer API route.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Fast token generation does not determine the whole agent loop</title><link>https://retrivium.ai/retrospectives/retro-groq-lpx-agent-speed-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-groq-lpx-agent-speed-boundary/</guid><description>LPX accelerates a generation stage, while agents also process inputs, call tools and wait on dependencies. Task completion requires a wider timing boundary.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why the LPX benchmark needs its model and context denominator</title><link>https://retrivium.ai/retrospectives/retro-groq-lpx-benchmark-denominator/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-groq-lpx-benchmark-denominator/</guid><description>The LPX benchmark belongs to its stated model, context and system path. A useful comparison retains timing, concurrency and acceptable-output boundaries.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Pipette: the August shift from model scores to deployed-system measurements</title><link>https://retrivium.ai/retrospectives/pipette-system-benchmark-2026/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/pipette-system-benchmark-2026/</guid><description>Pipette&apos;s release matters because it makes the measured unit an entire deployed configuration rather than an isolated model name.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Pipette: context-dependent edge rankings</title><link>https://retrivium.ai/retrospectives/retro-liquid-pipette-context-rankings/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-pipette-context-rankings/</guid><description>Pipette&apos;s system-oriented benchmark framing makes context part of a ranking, so a leading result under one request shape cannot establish a universal edge winner.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Pipette: runtime revisions as benchmark variables</title><link>https://retrivium.ai/retrospectives/retro-liquid-pipette-runtime-control/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-pipette-runtime-control/</guid><description>Pipette&apos;s deployed-system perspective makes a runtime revision a benchmark variable, rather than an invisible detail behind an unchanged model name.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Pipette: thermal state and reproducible edge tests</title><link>https://retrivium.ai/retrospectives/retro-liquid-pipette-thermal-state/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-pipette-thermal-state/</guid><description>Pipette&apos;s on-device measurement framing makes device state part of reproducibility, so repeated runs need a declared lifecycle rather than an unexplained average.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5 DSpark release: why the drafter is a separate deployment artifact</title><link>https://retrivium.ai/retrospectives/lfm25-dspark-separate-artifacts/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/lfm25-dspark-separate-artifacts/</guid><description>The text DSpark release adds a paired deployment artifact rather than a new replacement for the target model.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Agentic Search: what changed from retrieval to inspect-and-verify loops</title><link>https://retrivium.ai/retrospectives/mistral-agentic-search-evidence-loop/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/mistral-agentic-search-evidence-loop/</guid><description>Agentic Search changes the retrieval question from finding a plausible passage to deciding which evidence needs further inspection.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-DSpark: draft storage versus verification savings</title><link>https://retrivium.ai/retrospectives/retro-liquid-text-dspark-draft-memory/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-text-dspark-draft-memory/</guid><description>Text DSpark adds a separate draft artifact, so saved serial target work must be considered alongside the state and execution work introduced by the drafter.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-DSpark: distribution preservation and integration correctness</title><link>https://retrivium.ai/retrospectives/retro-liquid-text-dspark-sampling-proof/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-text-dspark-sampling-proof/</guid><description>DSpark&apos;s speculative execution must preserve the intended target contract, so an algorithmic property cannot be assumed to validate every runtime and sampler combination.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-DSpark: target revisions and draft compatibility</title><link>https://retrivium.ai/retrospectives/retro-liquid-text-dspark-target-identity/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-text-dspark-target-identity/</guid><description>A target update changes the DSpark pair&apos;s identity, so an accepted draft configuration should not silently certify every later checkpoint from the same family.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Agentic Search: search navigation versus answer generation</title><link>https://retrivium.ai/retrospectives/retro-mistral-agentic-search-verification-loop/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-agentic-search-verification-loop/</guid><description>Mistral&apos;s Agentic Search changes how evidence is found and inspected, but a successful navigation loop does not automatically make the final answer supported.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Agentic Search: document revisions in agentic navigation</title><link>https://retrivium.ai/retrospectives/retro-mistral-agentic-search-document-identity/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-agentic-search-document-identity/</guid><description>Agentic Search can inspect a document repeatedly, so preserving source revision becomes essential when an answer combines evidence collected at different moments.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Agentic Search: retrieval turns as a stopping problem</title><link>https://retrivium.ai/retrospectives/retro-mistral-agentic-search-loop-budget/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-agentic-search-loop-budget/</guid><description>Agentic Search makes another retrieval step possible, but deciding when to stop remains an application question about unresolved evidence rather than a universal turn budget.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Build: A generated app becomes a different object when published</title><link>https://retrivium.ai/retrospectives/grok-build-everyone-preview-to-published/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-build-everyone-preview-to-published/</guid><description>How Grok Build’s move from an in-chat preview to published apps changes artifact identity, audience and the evidence needed to review a generated application.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The Grok Build name does not identify one runtime</title><link>https://retrivium.ai/retrospectives/grok-build-surface-runtime-differences/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-build-surface-runtime-differences/</guid><description>Why Grok Build’s open terminal harness and later web/mobile Build Mode need separate runtime descriptions despite sharing a product-family name.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Build: Mobile creation needs a deliberate review handoff</title><link>https://retrivium.ai/retrospectives/grok-build-mobile-review-handoff/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-build-mobile-review-handoff/</guid><description>How Grok Build’s mobile availability changes review ergonomics while leaving a generated app’s functional, audience and publication checks necessary.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How billing infrastructure met inference routing</title><link>https://retrivium.ai/retrospectives/retro-stripe-openrouter-billing-routing/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-stripe-openrouter-billing-routing/</guid><description>Stripe and OpenRouter connect customer billing with upstream inference decisions. Their agreement explains strategic overlap, while delivered integration and financial outcomes require later evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What neutrality meant in OpenRouter’s acquisition announcement</title><link>https://retrivium.ai/retrospectives/retro-openrouter-neutrality-after-agreement/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-neutrality-after-agreement/</guid><description>OpenRouter’s continuity statement is a company commitment. Neutrality remains an operating question about exposed choices, caller constraints, selection rules and actual execution.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>From Stripe Projects integration to an acquisition agreement</title><link>https://retrivium.ai/retrospectives/retro-openrouter-acquisition-chronology/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-openrouter-acquisition-chronology/</guid><description>The earlier Stripe Projects flow connected account, key and billing setup. The later acquisition agreement is a distinct corporate milestone, not a retroactive change to that integration.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5 QAD: a quantized release produced by training, not just conversion</title><link>https://retrivium.ai/retrospectives/lfm25-qad-training-versus-conversion/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/lfm25-qad-training-versus-conversion/</guid><description>The QAD release makes training provenance part of quantized-checkpoint identity rather than treating the quantization label as a complete description.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5 Q4_0: trained quantization and artifact provenance</title><link>https://retrivium.ai/retrospectives/retro-liquid-qad-trained-artifact/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-qad-trained-artifact/</guid><description>LFM2.5 QAD shows why a Q4_0 label identifies a representation rather than the complete training provenance of the checkpoint inside it.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5 Q4_0: teacher comparisons and local acceptance</title><link>https://retrivium.ai/retrospectives/retro-liquid-qad-teacher-reference/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-qad-teacher-reference/</guid><description>A teacher-recovery result for LFM2.5 QAD answers a model-comparison question, but it cannot certify a downstream extraction workflow whose errors have different consequences.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5 Q4_0: quantized migration and exact identifiers</title><link>https://retrivium.ai/retrospectives/retro-liquid-qad-precision-migration/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-qad-precision-migration/</guid><description>Replacing a converted checkpoint with trained LFM2.5 QAD should preserve exact-identifier tests, because fluent output can conceal the errors most consequential to structured clients.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM5.3: a new post-training milestone on an existing base</title><link>https://retrivium.ai/retrospectives/glm53-same-base-new-posttraining/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/glm53-same-base-new-posttraining/</guid><description>GLM5.3&apos;s announcement is a post-training milestone rather than evidence that every capability gain requires a larger base model.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.8-27B: reconstructing a release distinct from Max-class weights</title><link>https://retrivium.ai/retrospectives/qwen38-27b-separate-weight-timeline/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/qwen38-27b-separate-weight-timeline/</guid><description>Qwen3.8-27B has its own release chronology, so family naming cannot substitute for identifying the checkpoint that was actually available and tested.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM-5.3: same base and changed post-training</title><link>https://retrivium.ai/retrospectives/retro-glm53-announcement-base-reuse/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-glm53-announcement-base-reuse/</guid><description>GLM5.3&apos;s same-base update makes post-training the relevant comparison axis, so an unchanged parameter count cannot establish unchanged task behaviour.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM-5.3: announcement and later weight publication</title><link>https://retrivium.ai/retrospectives/retro-glm53-announcement-release-stages/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-glm53-announcement-release-stages/</guid><description>GLM5.3&apos;s announcement, hosted rollout and downloadable artifacts need separate dates, because one model name can span several availability milestones.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GLM-5.3: defensive capability and evaluation scope</title><link>https://retrivium.ai/retrospectives/retro-glm53-announcement-cyber-evidence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-glm53-announcement-cyber-evidence/</guid><description>Controlled defensive evaluations around GLM5.3 should be read as task-distribution evidence, rather than proof that a deployed system is universally secure.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.8-27B reasoning budgets: when more output stops helping the task</title><link>https://retrivium.ai/retrospectives/retro-qwen38-27b-weights-thinking-budget/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-qwen38-27b-weights-thinking-budget/</guid><description>A retrospective on Qwen reasoning controls and the Qwen3.8-27B weight release, separating model capability from the output budget a task actually needs.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.8-27B checkpoints: keep official weights and conversions distinct</title><link>https://retrivium.ai/retrospectives/retro-qwen38-27b-weights-precision-evidence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-qwen38-27b-weights-precision-evidence/</guid><description>The Qwen3.8-27B release as an artifact history: preserve checkpoint revision, conversion lineage and template identity when interpreting local model results.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Flash 3.7 turned developer feedback into a short release cycle</title><link>https://retrivium.ai/retrospectives/flash37-release-cadence-feedback/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/flash37-release-cadence-feedback/</guid><description>How Gemini 3.7 Flash&apos;s rapid release cadence can turn developer feedback into regression assets while keeping compatibility and quality distinct.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A workhorse label needs completed-task token accounting</title><link>https://retrivium.ai/retrospectives/flash37-workhorse-token-efficiency/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/flash37-workhorse-token-efficiency/</guid><description>How Gemini 3.7 Flash&apos;s introductory rates and diligent tool work should be evaluated through the complete cost of an equivalent accepted task.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>UI generation gains still need reference fidelity checks</title><link>https://retrivium.ai/retrospectives/flash37-web-ui-reference-fidelity/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/flash37-web-ui-reference-fidelity/</guid><description>Why Gemini 3.7 Flash UI claims need separate checks for screenshot resemblance, design-system rules and functional interaction states.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Better knowledge work requires more than a polished artifact</title><link>https://retrivium.ai/retrospectives/flash37-knowledge-work-evidence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/flash37-knowledge-work-evidence/</guid><description>Why Gemini 3.7 Flash knowledge-work evaluation must preserve evidence identity through extraction, cross-document joins and final presentation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>MiniMax Music3: why the August event was a weight release,not its first API</title><link>https://retrivium.ai/retrospectives/minimax-music3-hosted-versus-weights/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/minimax-music3-hosted-versus-weights/</guid><description>MiniMax Music3&apos;s August event published music-generation weights and inference artifacts, which is different from the first availability of its hosted product.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>MiniMax Music3: why a text prompt still needs an audio inference contract</title><link>https://retrivium.ai/retrospectives/retro-minimax-music3-weights-audio-output/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-minimax-music3-weights-audio-output/</guid><description>The Music3 weight release in context: text-conditioned music research led to a serving problem defined by audio artifacts, duration and generation stages.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>MiniMax Music3 weights: separating artifact access from model terms</title><link>https://retrivium.ai/retrospectives/retro-minimax-music3-weights-weight-license/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-minimax-music3-weights-weight-license/</guid><description>A retrospective on Music3 open weights: distinguish hosted access, the downloadable package and the terms attached to the exact artifact being evaluated.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok 4.6 and the difference between sustained work and long chat</title><link>https://retrivium.ai/retrospectives/grok46-sustained-work-vs-long-chat/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok46-sustained-work-vs-long-chat/</guid><description>Why Grok 4.6 sustained-work claims should be tested through external artifacts, stable objectives and supported progress rather than conversation length.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Interactive artifacts need behavior checks beyond screenshots</title><link>https://retrivium.ai/retrospectives/grok46-interactive-artifact-acceptance/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok46-interactive-artifact-acceptance/</guid><description>Why Grok 4.6 interactive artifacts need parameter, repeated-use and reset checks beyond the appearance of their initial screenshot.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The Grok 4.6 model and its coding harness are separate evidence</title><link>https://retrivium.ai/retrospectives/grok46-coding-harness-boundary/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok46-coding-harness-boundary/</guid><description>Why Grok 4.6 coding evidence belongs to the model-and-harness combination, with tool contracts and available context retained in comparisons.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>First-week model access is a dated operating condition</title><link>https://retrivium.ai/retrospectives/grok46-provisional-access-assumptions/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok46-provisional-access-assumptions/</guid><description>Why Grok 4.6 first-week included usage should remain a dated product condition, separate from permanent capability and task efficiency.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-VL-3B: what changed for edge visual document tasks in August</title><link>https://retrivium.ai/retrospectives/lfm25-vl3b-visual-edge-release/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/lfm25-vl3b-visual-edge-release/</guid><description>The LFM2.5 visual release matters because a compact text lineage acquires a separate path for image evidence.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-VL-3B: visual processors as release artifacts</title><link>https://retrivium.ai/retrospectives/retro-liquid-vl3b-vision-processor/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-vl3b-vision-processor/</guid><description>LFM2.5-VL-3B&apos;s visual processor is part of the effective release artifact, because the same source image can become different evidence before model execution.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-VL-3B: OCR questions and visual evidence</title><link>https://retrivium.ai/retrospectives/retro-liquid-vl3b-ocr-grounding/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-vl3b-ocr-grounding/</guid><description>An OCR-style question for LFM2.5-VL-3B needs source-grounded acceptance, because a persuasive visual explanation can differ from an accurate reading of the image.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-VL-3B: text lineage and visual capability</title><link>https://retrivium.ai/retrospectives/retro-liquid-vl3b-text-visual-lineage/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-vl3b-text-visual-lineage/</guid><description>LFM2.5-VL-3B&apos;s text lineage helps explain its architecture, but visual capability still depends on a separately identified path from image evidence to model representation.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Bot moved from a workflow run to a persistent teammate</title><link>https://retrivium.ai/retrospectives/grok-bot-from-workflow-to-teammate/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-bot-from-workflow-to-teammate/</guid><description>How Grok Bot&apos;s persistent-worker beta changes instruction lifetimes, routine corrections and the assumptions behind repeated work.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A cloud computer changes what survives a user handoff</title><link>https://retrivium.ai/retrospectives/grok-bot-cloud-session-handoff/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-bot-cloud-session-handoff/</guid><description>Why Grok Bot cloud handoffs must reconcile current intent, retained browser state and saved or committed effects separately from conversation memory.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Approval interrupts are part of the task protocol</title><link>https://retrivium.ai/retrospectives/grok-bot-approval-interrupts/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-bot-approval-interrupts/</guid><description>How Grok Bot approval handoffs should connect finished preparation, the exact remaining decision and the operation applied under existing authorization.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Bot&apos;s beta usage boundary needs a date</title><link>https://retrivium.ai/retrospectives/grok-bot-usage-boundary-history/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/grok-bot-usage-boundary-history/</guid><description>Why Grok Bot beta&apos;s separate usage boundary should remain dated and distinct from task resource consumption, accepted outcomes and later plan terms.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Lightning and Switchyard: why the August launch contains two different building blocks</title><link>https://retrivium.ai/retrospectives/lightning-switchyard-model-router-split/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/lightning-switchyard-model-router-split/</guid><description>Lightning and Switchyard represent two different building blocks: a specialized executor and a routing library.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Nemotron3.5 Lightning and NeMo Switchyard: routing library and specialist model</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-lightning-router-library/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-lightning-router-library/</guid><description>NeMo Switchyard and NemotronLightning solve different layers of a specialist system, so a routing library cannot choose the correct model from one attractive benchmark score.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Nemotron3.5 Lightning and NeMo Switchyard: distillation lineage and task specialization</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-lightning-distillation/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-lightning-distillation/</guid><description>NemotronLightning&apos;s distillation lineage describes a training relationship, not universal equivalence to a larger teacher across every planning and execution task.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Nemotron3.5 Lightning and NeMo Switchyard: specialists inside long-running workflows</title><link>https://retrivium.ai/retrospectives/retro-nemotron35-lightning-execution-loop/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-nemotron35-lightning-execution-loop/</guid><description>NemotronLightning can occupy repeated execution steps in a longer workflow, but a compact specialist does not remove the need to validate external actions and accumulated state.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Image 2.0: checking typography beyond visual quality</title><link>https://retrivium.ai/retrospectives/imagine2-typography-acceptance/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/imagine2-typography-acceptance/</guid><description>Imagine Image 2.0 emphasizes typography and layout. This retrospective separates exact wording, visual hierarchy and placement in useful generated graphics.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Image 2.0: which reference details an edit must preserve</title><link>https://retrivium.ai/retrospectives/imagine2-edit-reference-identity/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/imagine2-edit-reference-identity/</guid><description>Why reference-preserving edits in Grok Image 2.0 need explicit invariants, so attractive changes do not erase the subject details the request required.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grok Image 2.0: what the Quality Mode label establishes</title><link>https://retrivium.ai/retrospectives/imagine2-quality-mode-task-meaning/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/imagine2-quality-mode-task-meaning/</guid><description>What Grok Image 2.0’s Quality Mode label establishes, and why task-specific acceptance still needs evidence about text, references and usable output.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SK hynix FMS: Why FMS framed AI memory as placement across tiers</title><link>https://retrivium.ai/retrospectives/retro-fms-memory-tier-placement/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-fms-memory-tier-placement/</guid><description>SK hynix’s FMS presentation followed a rack-scale roadmap and HBM shipment update. Why the next memory question concerns state placement across a hierarchy.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SK hynix FMS: An HBF roadmap is not evidence of deployable HBF servers</title><link>https://retrivium.ai/retrospectives/retro-fms-hbf-roadmap-shipment/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-fms-hbf-roadmap-shipment/</guid><description>The HBF discussion at FMS followed established HBM shipment milestones. How to read an emerging memory roadmap without treating it as deployable server supply.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SK hynix FMS: CXL expansion adds a placement option, not equivalent local memory</title><link>https://retrivium.ai/retrospectives/retro-fms-cxl-capacity-latency/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-fms-cxl-capacity-latency/</guid><description>How the path from HBM supply to FMS hierarchy demonstrations changed the CXL discussion from extra capacity to a workload placement decision.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SK hynix FMS: A broad memory portfolio still needs software to manage state</title><link>https://retrivium.ai/retrospectives/retro-fms-memory-vendor-system-role/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-fms-memory-vendor-system-role/</guid><description>SK hynix’s broad FMS portfolio followed platform and shipment milestones. Why a complete component menu still leaves cache movement and lifecycle policy to software.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Taalas and AMD’s shift toward workload-specialized inference hardware</title><link>https://retrivium.ai/retrospectives/retro-amd-taalas-specialized-inference/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-amd-taalas-specialized-inference/</guid><description>The Taalas agreement follows phase-level inference specialization and a broader AMD platform roadmap. Its useful question is where a tailored execution path fits a changing workload.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why the Taalas headline must be read with the closing conditions</title><link>https://retrivium.ai/retrospectives/retro-taalas-agreement-headline-body/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-taalas-agreement-headline-body/</guid><description>The Taalas headline and release body carry different levels of precision. An event card should preserve the title while classifying the announced transaction from its operative text.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Two different routes to specialized inference in AMD’s 2026 portfolio</title><link>https://retrivium.ai/retrospectives/retro-taalas-cerebras-inference-portfolio/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-taalas-cerebras-inference-portfolio/</guid><description>The Cerebras and Taalas announcements suggest complementary inference paths. A useful portfolio analysis first distinguishes alternatives, phase components and platform layers.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>An inference-chip agreement still leaves an integration roadmap</title><link>https://retrivium.ai/retrospectives/retro-taalas-integration-roadmap-risk/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-taalas-integration-roadmap-risk/</guid><description>The Taalas agreement begins an integration roadmap. A maintained inference path needs explicit model artifacts, runtime dispatch, version qualification and support ownership.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CoreWeave Indonesia: Contracted Indonesian power and live GPU supply are different ledgers</title><link>https://retrivium.ai/retrospectives/retro-coreweave-indonesia-contract-live/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-coreweave-indonesia-contract-live/</guid><description>CoreWeave’s Indonesia expansion followed a hardware roadmap and execution-platform releases. Why contracted power for 2028 is a different record from live GPU supply.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CoreWeave Indonesia: A new AI region needs an operations team as well as equipment</title><link>https://retrivium.ai/retrospectives/retro-coreweave-indonesia-local-operations/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-coreweave-indonesia-local-operations/</guid><description>CoreWeave’s Indonesia plan includes local operations training. How earlier compute and sandbox releases make staffing part of AI regional capacity rather than an afterthought.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CoreWeave Indonesia: Locality benefits require a local service path, not just a facility address</title><link>https://retrivium.ai/retrospectives/retro-coreweave-indonesia-location-service/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-coreweave-indonesia-location-service/</guid><description>CoreWeave’s future Indonesian sites make locality a useful question. Why a regional facility address alone cannot establish the complete path of an AI request.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CoreWeave Indonesia: A 2028 facility plan must remain flexible across accelerator generations</title><link>https://retrivium.ai/retrospectives/retro-coreweave-indonesia-generation-window/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-coreweave-indonesia-generation-window/</guid><description>CoreWeave’s 2028 Indonesian facility plan followed a 2026 accelerator roadmap. A retrospective on why datacenter design and GPU generations run on different clocks.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-2.6B: reconstructing the local-agent release from primary dates</title><link>https://retrivium.ai/retrospectives/lfm25-26b-announcement-timeline/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/lfm25-26b-announcement-timeline/</guid><description>The LFM2.5-2.6B announcement should be understood as a local-agent milestone with several later artifact branches, not a single date attached to every file in its ecosystem.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Shieldstral: the August move from fixed labels to policy questions</title><link>https://retrivium.ai/retrospectives/shieldstral-policy-question-release/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/shieldstral-policy-question-release/</guid><description>Shieldstral made policy questions part of a multimodal classifier&apos;s input, which changes how moderation behaviour must be recorded and compared.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SpecForge: the August separation of target and trainer lifecycles</title><link>https://retrivium.ai/retrospectives/specforge-target-trainer-lifecycle-split/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/specforge-target-trainer-lifecycle-split/</guid><description>SpecForge separated target feature production from draft optimization, making their independent lifecycles an architectural concern rather than a minor release detail.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-2.6B: reasoning traces in persistent local agents</title><link>https://retrivium.ai/retrospectives/retro-liquid-26b-thinking-session/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-26b-thinking-session/</guid><description>LFM2.5-2.6B&apos;s compact weights do not imply a compact lifetime session, because persistent agents also accumulate conversations, tool results and unfinished work.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-2.6B: tool completion versus fluent planning</title><link>https://retrivium.ai/retrospectives/retro-liquid-26b-tool-evidence/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-26b-tool-evidence/</guid><description>LFM2.5-2.6B&apos;s agent-oriented release makes tool use relevant, but a fluent plan is not evidence that an external action completed successfully.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LFM2.5-2.6B: announcement dates and model-card refreshes</title><link>https://retrivium.ai/retrospectives/retro-liquid-26b-date-provenance/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-liquid-26b-date-provenance/</guid><description>LFM2.5-2.6B&apos;s release history should follow the dated primary announcement, rather than treating later model-card changes or secondary coverage as a new launch.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Shieldstral: policy questions as versioned inputs</title><link>https://retrivium.ai/retrospectives/retro-mistral-shieldstral-policy-question/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-shieldstral-policy-question/</guid><description>Shieldstral puts policy questions in the inference input. Trace the move from fixed guardrail labels to versioned wording that applications must evaluate.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing Shieldstral: content policy versus provenance detection</title><link>https://retrivium.ai/retrospectives/retro-mistral-shieldstral-classifier-provenance/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-mistral-shieldstral-classifier-provenance/</guid><description>Shieldstral moderation and watermark detection answer different questions. Trace why content-policy classification cannot establish a text’s origin.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SpecForge disaggregation: captured features need an ownership lifecycle</title><link>https://retrivium.ai/retrospectives/retro-specforge-disaggregation-feature-ownership/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-specforge-disaggregation-feature-ownership/</guid><description>How SpecForge reached separate target-inference and draft-training pools, and why the resulting feature pipeline needs explicit ownership and recovery rules.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SpecForge consistency gates: a small correctness check before a large run</title><link>https://retrivium.ai/retrospectives/retro-specforge-disaggregation-consistency-gate/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-specforge-disaggregation-consistency-gate/</guid><description>A retrospective on the SpecForge training-serving consistency gate: why a controlled example can reject an incompatible pipeline without proving final model quality.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.8 Max: separate the August3 announcement from subsequent weights</title><link>https://retrivium.ai/retrospectives/qwen38-max-announcement-and-weights/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/qwen38-max-announcement-and-weights/</guid><description>Qwen3.8 Max&apos;s announcement created a cloud-model milestone and a future weight commitment, not one universally available artifact.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.8-Max: hosted vision and downloadable text weights</title><link>https://retrivium.ai/retrospectives/retro-qwen38max-announcement-weight-modality/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-qwen38max-announcement-weight-modality/</guid><description>Qwen3.8Max&apos;s hosted capabilities and downloadable checkpoint contract must be checked separately, because one family announcement does not make every route expose identical modalities.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.8-Max: active parameters and full checkpoint movement</title><link>https://retrivium.ai/retrospectives/retro-qwen38max-announcement-max-scale/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-qwen38max-announcement-max-scale/</guid><description>Qwen3.8Max&apos;s selected computation should not be confused with full checkpoint movement, because loading and distributing an artifact involve state beyond the experts active for one request.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3.8-Max: one announcement and several availability clocks</title><link>https://retrivium.ai/retrospectives/retro-qwen38max-announcement-release-clock/</link><guid isPermaLink="true">https://retrivium.ai/retrospectives/retro-qwen38max-announcement-release-clock/</guid><description>Qwen3.8Max&apos;s cloud announcement, checkpoint publication and runtime support form separate availability clocks, so one launch date cannot stand in for the complete adoption history.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 5090 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-5090-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-5090-inference-rendering/</guid><description>RTX 5090 32 GB for LLMs and Cycles, covering reference 575 W power, Blackwell software checks and verified switching between server workloads.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 5080 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-5080-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-5080-inference-rendering/</guid><description>RTX 5080 16 GB for inference and server rendering, with memory limits, backend validation and queue decisions around the reference 360 W specification.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 5070 Ti for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-5070-ti-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-5070-ti-inference-rendering/</guid><description>RTX 5070 Ti 16 GB: validate LLM context, rendering scenes and server admission against Blackwell support, reference 300 W and RTX 5070 differences.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 5070 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-5070-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-5070-inference-rendering/</guid><description>RTX 5070 12 GB for LLMs and Cycles: context boundaries, GDDR7 configuration, a server worker and a scene reload verification experiment.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 5060 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-5060-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-5060-inference-rendering/</guid><description>RTX 5060 8 GB for a bounded LLM service and GPU rendering, with host memory checks and a request cancellation resource-release experiment.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 5050 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-5050-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-5050-inference-rendering/</guid><description>Desktop RTX 5050 8 GB GDDR6 for small LLM workloads and Cycles, including neighboring-model differences and a display-attached worker check.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 5060 Ti for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-5060-ti-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-5060-ti-inference-rendering/</guid><description>RTX 5060 Ti 8 and 16 GB: variant specifications, LLM and Cycles memory checks, server setup and a reproducible comparison of two actual boards.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 5090 D for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-5090-d-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-5090-d-inference-rendering/</guid><description>The original RTX 5090 D 32 GB: distinguish D v2, verified NVIDIA specifications, LLM and Cycles paths and an exact regional server inventory.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 5090 D v2 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-5090-d-v2-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-5090-d-v2-inference-rendering/</guid><description>RTX 5090 D v2 24 GB: a distinct GDDR7 profile, original D differences, reference 575 W and verification of inference and a server render scene.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 4090 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-4090-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-4090-inference-rendering/</guid><description>RTX 4090 24 GB for LLMs and server Cycles: official desktop specifications, reference 450 W, explicit GPU workers and a two-queue acceptance test.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 4080 SUPER for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-4080-super-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-4080-super-inference-rendering/</guid><description>RTX 4080 SUPER 16 GB for LLM inference and Cycles, with reference 320 W and a worker upgrade check that keeps the original RTX 4080 distinct.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 4080 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-4080-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-4080-inference-rendering/</guid><description>The original RTX 4080 16 GB for inference and Cycles, distinct from SUPER, with cold-start tests separating file loading from GPU memory behavior.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 4070 Ti SUPER for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-4070-ti-super-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-4070-ti-super-inference-rendering/</guid><description>RTX 4070 Ti SUPER 16 GB: LLM and Cycles memory, differences from the 12 GB Ti and a server admission test for long request histories.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 4070 Ti for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-4070-ti-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-4070-ti-inference-rendering/</guid><description>RTX 4070 Ti 12 GB for inference and Cycles: the original non-SUPER profile, context memory, reference 285 W and complete job energy boundaries.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 4070 SUPER for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-4070-super-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-4070-super-inference-rendering/</guid><description>RTX 4070 SUPER 12 GB for inference and Cycles, distinct from the ordinary 4070, with a complete streaming response check on a server worker.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 4060 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-4060-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-4060-inference-rendering/</guid><description>RTX 4060 8 GB GDDR6 for LLMs and Cycles, with reference 115 W, container device checks and reproducible job transfer between workers.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 4070 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-4070-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-4070-inference-rendering/</guid><description>RTX 4070 12 GB GDDR6 and GDDR6X variants for LLMs and Cycles, including memory inventory and separate server workload phase checks.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 4060 Ti for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-4060-ti-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-4060-ti-inference-rendering/</guid><description>RTX 4060 Ti 8 and 16 GB: variant table, unknown board-specific power, LLM and Cycles paths and job routing by verified memory capacity.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 4090 D for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-4090-d-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-4090-d-inference-rendering/</guid><description>RTX 4090 D 24 GB: official regional Ada specifications, 425 W board power, inference and Cycles paths and a server inventory classification check.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 3090 Ti for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-3090-ti-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-3090-ti-inference-rendering/</guid><description>RTX 3090 Ti 24 GB for inference and Cycles, covering Ampere, reference 450 W, RTX 3090 differences and repeated jobs under normal cooling.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 3090 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-3090-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-3090-inference-rendering/</guid><description>RTX 3090 24 GB for inference and server Cycles, with reference 350 W and a reproducible workload acceptance test for an existing GPU.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 3080 Ti for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-3080-ti-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-3080-ti-inference-rendering/</guid><description>RTX 3080 Ti 12 GB for inference and GPU rendering, with reference 350 W and resident data checks when changing a model or scene on a server worker.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 3070 Ti for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-3070-ti-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-3070-ti-inference-rendering/</guid><description>RTX 3070 Ti 8 GB GDDR6X for LLMs and Cycles, with reference 290 W and a bounded memory-rejection test for a server queue.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 3070 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-3070-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-3070-inference-rendering/</guid><description>RTX 3070 8 GB GDDR6 for LLMs and Cycles, with partial GPU offload verification, reference 220 W and reproducible server workload placement.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 3080 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-3080-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-3080-inference-rendering/</guid><description>RTX 3080 10 and 12 GB GDDR6X variants, reference 320/350 W, LLM and Cycles paths and admission rules for different server worker classes.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 3060 Ti for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-3060-ti-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-3060-ti-inference-rendering/</guid><description>RTX 3060 Ti 8 GB GDDR6 and GDDR6X for LLMs and Cycles, with board-revision power uncertainty and a reproducible server workload inventory.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 3060 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-3060-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-3060-inference-rendering/</guid><description>RTX 3060 8 and 12 GB GDDR6 variants, reference 170 W, LLM and Cycles paths and a capacity-based acceptance test beyond the shared model name.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 3050 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-3050-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-3050-inference-rendering/</guid><description>RTX 3050 6 and 8 GB including OEM, with LLM and Cycles paths, reference 70/130 W and checks that preserve board-specific unknowns.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 2080 Ti for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-2080-ti-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-2080-ti-inference-rendering/</guid><description>RTX 2080 Ti 11 GB for LLMs and Cycles, with NVIDIA comparison-design power and worker checks that avoid rounding capacity up to 12 GB.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 2080 SUPER for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-2080-super-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-2080-super-inference-rendering/</guid><description>RTX 2080 SUPER 8 GB for inference and Cycles, with comparison-design 250 W and a controlled CUDA/OptiX backend change on a server scene.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 2080 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-2080-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-2080-inference-rendering/</guid><description>The original RTX 2080 8 GB for LLMs and Cycles, with NVIDIA design power and software compatibility checks separate from VRAM exhaustion.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 2070 SUPER for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-2070-super-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-2070-super-inference-rendering/</guid><description>RTX 2070 SUPER 8 GB for inference and Cycles, with the 215 W design specification and queue-delay checks separate from GPU execution time.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 2070 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-2070-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-2070-inference-rendering/</guid><description>RTX 2070 8 GB for LLMs and Cycles: the original Turing model, NVIDIA design power and checks for a workstation worker under background graphics load.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 2060 SUPER for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-2060-super-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-2060-super-inference-rendering/</guid><description>RTX 2060 SUPER 8 GB, distinct from RTX 2060 6/12 GB, with LLM and Cycles checks, the 175 W design and full-name server job routing.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce RTX 2060 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-rtx-2060-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-rtx-2060-inference-rendering/</guid><description>RTX 2060 6 and 12 GB Turing variants for LLMs and Cycles, reference 160/185 W and capacity checks without assuming a newer architecture.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA TITAN RTX for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-titan-rtx-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-titan-rtx-inference-rendering/</guid><description>TITAN RTX 24 GB for LLMs and Cycles, with 280 W, Turing software checks and NVLink validation without automatic memory-pooling claims.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA TITAN V for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-titan-v-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-titan-v-inference-rendering/</guid><description>TITAN V 12 GB HBM2 for conditional legacy inference, the vLLM CC 7.5 boundary, compatible CUDA tooling and a Cycles server worker check.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA TITAN Xp for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-titan-xp-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-titan-xp-inference-rendering/</guid><description>TITAN Xp 12 GB GDDR5X for conditional Pascal inference and Cycles, with 250 W and a legacy binary check using the correct build architecture.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA TITAN X Pascal for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-titan-x-pascal-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-titan-x-pascal-inference-rendering/</guid><description>TITAN X Pascal 12 GB GDDR5X, distinct from Maxwell and Xp, with legacy inference and Cycles checks that preserve unknown board power.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce GTX 1660 Ti for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-gtx-1660-ti-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-gtx-1660-ti-inference-rendering/</guid><description>GTX 1660 Ti 6 GB GDDR6: Turing without Tensor or RT cores, LLM offload, Cycles and a bounded worker test with the 120 W design specification.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce GTX 1660 SUPER for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-gtx-1660-super-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-gtx-1660-super-inference-rendering/</guid><description>GTX 1660 SUPER 6 GB GDDR6 for LLMs and Cycles without Tensor/RT cores, with 125 W and separate memory, loading and execution checks.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce GTX 1660 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-gtx-1660-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-gtx-1660-inference-rendering/</guid><description>GTX 1660 6 GB GDDR5: original Turing without Tensor/RT cores, bounded LLM and Cycles paths and GGUF provenance checks for a server worker.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce GTX 16 4 GB family for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-gtx-16-4-gb-family-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-gtx-16-4-gb-family-inference-rendering/</guid><description>GTX 1650, 1650 SUPER and 1630 4 GB variants, with GDDR5/GDDR6 specifications, tiny LLM and Cycles experiments and a limited worker envelope.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce GTX 1080 Ti for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-gtx-1080-ti-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-gtx-1080-ti-inference-rendering/</guid><description>GTX 1080 Ti 11 GB GDDR5X for legacy LLMs and Cycles, with a 250 W board example and build compatibility checks separate from capacity.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce GTX 1080 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-gtx-1080-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-gtx-1080-inference-rendering/</guid><description>GTX 1080 8 GB GDDR5X, original and 11 Gbps refresh variants, with legacy LLM and Cycles checks separating data rate from capacity.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce GTX 1070 Ti for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-gtx-1070-ti-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-gtx-1070-ti-inference-rendering/</guid><description>GTX 1070 Ti 8 GB GDDR5 using the MSI GAMING 180 W example, with legacy LLM and Cycles paths tied to an actual board specification.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce GTX 1070 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-gtx-1070-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-gtx-1070-inference-rendering/</guid><description>GTX 1070 8 GB GDDR5 using a Founders Edition 150 W example, with conditional legacy inference, Cycles and saved worker environment migration checks.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce GTX 1060 for LLM inference and GPU rendering</title><link>https://retrivium.ai/journal/gpu-nvidia-gtx-1060-inference-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvidia-gtx-1060-inference-rendering/</guid><description>GTX 1060 3, 5 and 6 GB GDDR5/GDDR5X variants, with a unified inventory, legacy LLM and Cycles checks tied to the actual AIB board.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX PRO 6000 Blackwell Workstation Edition: 96GB in a single tower</title><link>https://retrivium.ai/journal/rtx-pro-6000-blackwell-workstation-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-pro-6000-blackwell-workstation-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX PRO 6000 Blackwell Workstation Edition, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition: 96GB at a 300W board limit</title><link>https://retrivium.ai/journal/rtx-pro-6000-blackwell-max-q-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-pro-6000-blackwell-max-q-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX PRO 6000 Blackwell Server Edition: air and liquid server integration</title><link>https://retrivium.ai/journal/rtx-pro-6000-blackwell-server-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-pro-6000-blackwell-server-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX PRO 6000 Blackwell Server Edition, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX PRO 5500 Blackwell Workstation Edition: 84GB and preliminary specifications</title><link>https://retrivium.ai/journal/rtx-pro-5500-blackwell-workstation-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-pro-5500-blackwell-workstation-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX PRO 5500 Blackwell Workstation Edition, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX PRO 5000 Blackwell: 48GB and72GB are separate variants</title><link>https://retrivium.ai/journal/rtx-pro-5000-blackwell-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-pro-5000-blackwell-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX PRO 5000 Blackwell, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX PRO 4500 Blackwell Workstation Edition: the 200W active workstation board</title><link>https://retrivium.ai/journal/rtx-pro-4500-blackwell-workstation-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-pro-4500-blackwell-workstation-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX PRO 4500 Blackwell Workstation Edition, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX PRO 4500 Blackwell Server Edition: 32GB in a passive single-slot server card</title><link>https://retrivium.ai/journal/rtx-pro-4500-blackwell-server-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-pro-4500-blackwell-server-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX PRO 4500 Blackwell Server Edition, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX PRO 4000 Blackwell: 24GB in a full-height single slot</title><link>https://retrivium.ai/journal/rtx-pro-4000-blackwell-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-pro-4000-blackwell-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX PRO 4000 Blackwell, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX PRO 4000 Blackwell SFF Edition: 24GB for low-profile systems</title><link>https://retrivium.ai/journal/rtx-pro-4000-blackwell-sff-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-pro-4000-blackwell-sff-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX PRO 4000 Blackwell SFF Edition, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX PRO 2000 Blackwell: 16GB inference and compact rendering</title><link>https://retrivium.ai/journal/rtx-pro-2000-blackwell-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-pro-2000-blackwell-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX PRO 2000 Blackwell, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX 6000 Ada Generation: 48GB without assuming Ampere A6000 equivalence</title><link>https://retrivium.ai/journal/rtx-6000-ada-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-6000-ada-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX 6000 Ada Generation, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX 5880 Ada Generation: identify the 48GB Ada SKU</title><link>https://retrivium.ai/journal/rtx-5880-ada-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-5880-ada-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX 5880 Ada Generation, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX 5000 Ada Generation: 32GB and engine compatibility</title><link>https://retrivium.ai/journal/rtx-5000-ada-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-5000-ada-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX 5000 Ada Generation, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX 4500 Ada Generation: 24GB for a mixed workstation</title><link>https://retrivium.ai/journal/rtx-4500-ada-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-4500-ada-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX 4500 Ada Generation, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX 4000 Ada Generation: 20GB in a full-height single slot</title><link>https://retrivium.ai/journal/rtx-4000-ada-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-4000-ada-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX 4000 Ada Generation, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX 4000 SFF Ada Generation: 20GB under a 70W board limit</title><link>https://retrivium.ai/journal/rtx-4000-sff-ada-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-4000-sff-ada-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX 4000 SFF Ada Generation, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX 2000 Ada Generation: 16GB in a compact render worker</title><link>https://retrivium.ai/journal/rtx-2000-ada-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-2000-ada-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX 2000 Ada Generation, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA A800 40GB Active: inference compute and rendering caveats</title><link>https://retrivium.ai/journal/a800-40gb-active-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/a800-40gb-active-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA A800 40GB Active, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX A6000: 48GB and explicit multi-GPU memory</title><link>https://retrivium.ai/journal/rtx-a6000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-a6000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX A6000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX A5500: 24GB without an Ada name collision</title><link>https://retrivium.ai/journal/rtx-a5500-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-a5500-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX A5500, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX A5000: a 24GB Ampere baseline</title><link>https://retrivium.ai/journal/rtx-a5000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-a5000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX A5000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX A4500: 20GB and bounded context</title><link>https://retrivium.ai/journal/rtx-a4500-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-a4500-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX A4500, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX A4000: 16GB in one full-height slot</title><link>https://retrivium.ai/journal/rtx-a4000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-a4000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX A4000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX A2000: 6GB versus12GB in one model family</title><link>https://retrivium.ai/journal/rtx-a2000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-a2000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX A2000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX A1000: 8GB in a 50W compact board</title><link>https://retrivium.ai/journal/rtx-a1000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-a1000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX A1000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA RTX A400: 4GB sets the workload boundary</title><link>https://retrivium.ai/journal/rtx-a400-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-a400-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA RTX A400, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA T400, T600 and T1000: small-model inference and rendering limits</title><link>https://retrivium.ai/journal/compact-nvidia-t400-t600-t1000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/compact-nvidia-t400-t600-t1000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA T400, T600 and T1000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro RTX 8000: 48GB and the active board identity</title><link>https://retrivium.ai/journal/quadro-rtx-8000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-rtx-8000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro RTX 8000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro RTX 6000: 24GB before the Ada and Blackwell names</title><link>https://retrivium.ai/journal/quadro-rtx-6000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-rtx-6000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro RTX 6000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro RTX 5000: 16GB on the original Turing5000</title><link>https://retrivium.ai/journal/quadro-rtx-5000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-rtx-5000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro RTX 5000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro RTX 4000: 8GB in the original single-slot RTX</title><link>https://retrivium.ai/journal/quadro-rtx-4000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-rtx-4000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro RTX 4000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro RTX 8000 Passive PCIe Server Card: the passive250W server edition</title><link>https://retrivium.ai/journal/quadro-rtx-8000-passive-server-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-rtx-8000-passive-server-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro RTX 8000 Passive PCIe Server Card, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro RTX 6000 Passive PCIe Server Card: the passive250W server edition</title><link>https://retrivium.ai/journal/quadro-rtx-6000-passive-server-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-rtx-6000-passive-server-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro RTX 6000 Passive PCIe Server Card, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro GV100: 32GB Volta needs a pinned stack</title><link>https://retrivium.ai/journal/quadro-gv100-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-gv100-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro GV100, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro GP100: 16GB HBM2 without modern vLLM support</title><link>https://retrivium.ai/journal/quadro-gp100-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-gp100-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro GP100, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro P6000: 24GB capacity with legacy compilation</title><link>https://retrivium.ai/journal/quadro-p6000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-p6000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro P6000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro P5000: 16GB Pascal for bounded reuse</title><link>https://retrivium.ai/journal/quadro-p5000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-p5000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro P5000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro P4000: 8GB and the 105W single-slot board</title><link>https://retrivium.ai/journal/quadro-p4000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-p4000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro P4000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro P400, P600, P620, P1000, P2000 and P2200: 2GB to5GB legacy workload boundaries</title><link>https://retrivium.ai/journal/compact-quadro-pascal-2gb-5gb-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/compact-quadro-pascal-2gb-5gb-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro P400, P600, P620, P1000, P2000 and P2200, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro M6000: 12GB and24GB on a retained legacy stack</title><link>https://retrivium.ai/journal/quadro-m6000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-m6000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro M6000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro M5000: 8GB with a Maxwell compatibility ceiling</title><link>https://retrivium.ai/journal/quadro-m5000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-m5000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro M5000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Quadro M4000: 8GB in a legacy single slot</title><link>https://retrivium.ai/journal/quadro-m4000-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/quadro-m4000-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Quadro M4000, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 9070 XT: 16 GB RDNA 4 deployment boundaries</title><link>https://retrivium.ai/journal/amd-radeon-rx-9070-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-9070-xt-llm-rendering/</guid><description>Radeon RX 9070 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 9070: 16 GB capacity and a 220 W board</title><link>https://retrivium.ai/journal/amd-radeon-rx-9070-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-9070-llm-rendering/</guid><description>Radeon RX 9070: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 9070 GRE: verify 12 GB before model sizing</title><link>https://retrivium.ai/journal/amd-radeon-rx-9070-gre-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-9070-gre-llm-rendering/</guid><description>Radeon RX 9070 GRE: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 9060 XT: 8 GB versus 16 GB for inference</title><link>https://retrivium.ai/journal/amd-radeon-rx-9060-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-9060-xt-llm-rendering/</guid><description>Radeon RX 9060 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 9060 XT LP: the 140 W product and chassis checks</title><link>https://retrivium.ai/journal/amd-radeon-rx-9060-xt-lp-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-9060-xt-lp-llm-rendering/</guid><description>Radeon RX 9060 XT LP: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 9060: the non-XT 8 GB deployment case</title><link>https://retrivium.ai/journal/amd-radeon-rx-9060-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-9060-llm-rendering/</guid><description>Radeon RX 9060: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 9050: 4 GB and 8 GB small-model limits</title><link>https://retrivium.ai/journal/amd-radeon-rx-9050-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-9050-llm-rendering/</guid><description>Radeon RX 9050: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 7900 XTX: 24 GB on one GPU</title><link>https://retrivium.ai/journal/amd-radeon-rx-7900-xtx-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-7900-xtx-llm-rendering/</guid><description>Radeon RX 7900 XTX: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 7900 XT: planning around 20 GB</title><link>https://retrivium.ai/journal/amd-radeon-rx-7900-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-7900-xt-llm-rendering/</guid><description>Radeon RX 7900 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 7900 GRE: a separate 16 GB GRE target</title><link>https://retrivium.ai/journal/amd-radeon-rx-7900-gre-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-7900-gre-llm-rendering/</guid><description>Radeon RX 7900 GRE: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 7800 XT: a repeatable 16 GB workstation</title><link>https://retrivium.ai/journal/amd-radeon-rx-7800-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-7800-xt-llm-rendering/</guid><description>Radeon RX 7800 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 7700 XT: 12 GB and the non-XT naming trap</title><link>https://retrivium.ai/journal/amd-radeon-rx-7700-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-7700-xt-llm-rendering/</guid><description>Radeon RX 7700 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 7700: identify the official 16 GB non-XT SKU</title><link>https://retrivium.ai/journal/amd-radeon-rx-7700-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-7700-llm-rendering/</guid><description>Radeon RX 7700: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 7650 GRE: regional SKU and software support checks</title><link>https://retrivium.ai/journal/amd-radeon-rx-7650-gre-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-7650-gre-llm-rendering/</guid><description>Radeon RX 7650 GRE: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 7600 XT: 16 GB does not establish ROCm support</title><link>https://retrivium.ai/journal/amd-radeon-rx-7600-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-7600-xt-llm-rendering/</guid><description>Radeon RX 7600 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 7600: an exact 8 GB ROCm SKU</title><link>https://retrivium.ai/journal/amd-radeon-rx-7600-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-7600-llm-rendering/</guid><description>Radeon RX 7600: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 7400: an 8 GB low-board-power candidate</title><link>https://retrivium.ai/journal/amd-radeon-rx-7400-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-7400-llm-rendering/</guid><description>Radeon RX 7400: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 6950 XT: 16 GB with a 335 W reference envelope</title><link>https://retrivium.ai/journal/amd-radeon-rx-6950-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-6950-xt-llm-rendering/</guid><description>Radeon RX 6950 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 6900 XT: reuse an existing 16 GB flagship carefully</title><link>https://retrivium.ai/journal/amd-radeon-rx-6900-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-6900-xt-llm-rendering/</guid><description>Radeon RX 6900 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 6800 XT: consumer RX versus PRO software boundaries</title><link>https://retrivium.ai/journal/amd-radeon-rx-6800-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-6800-xt-llm-rendering/</guid><description>Radeon RX 6800 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 6800: 16 GB without the XT or PRO assumptions</title><link>https://retrivium.ai/journal/amd-radeon-rx-6800-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-6800-llm-rendering/</guid><description>Radeon RX 6800: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 6750 XT: 12 GB for a measured offload layout</title><link>https://retrivium.ai/journal/amd-radeon-rx-6750-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-6750-xt-llm-rendering/</guid><description>Radeon RX 6750 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 6700 XT: validate a 12 GB RDNA 2 node</title><link>https://retrivium.ai/journal/amd-radeon-rx-6700-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-6700-xt-llm-rendering/</guid><description>Radeon RX 6700 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 6700: the non-XT 10 GB capacity boundary</title><link>https://retrivium.ai/journal/amd-radeon-rx-6700-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-6700-llm-rendering/</guid><description>Radeon RX 6700: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 6650 XT: an 8 GB refresh needs its own test</title><link>https://retrivium.ai/journal/amd-radeon-rx-6650-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-6650-xt-llm-rendering/</guid><description>Radeon RX 6650 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 6600 XT: an 8 GB backend qualification checklist</title><link>https://retrivium.ai/journal/amd-radeon-rx-6600-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-6600-xt-llm-rendering/</guid><description>Radeon RX 6600 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 6600: selective offload on an 8 GB card</title><link>https://retrivium.ai/journal/amd-radeon-rx-6600-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-6600-llm-rendering/</guid><description>Radeon RX 6600: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 6400: 4 GB and host-transfer constraints</title><link>https://retrivium.ai/journal/amd-radeon-rx-6400-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-6400-llm-rendering/</guid><description>Radeon RX 6400: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 6750 GRE: 10 GB versus 12 GB official variants</title><link>https://retrivium.ai/journal/amd-radeon-rx-6750-gre-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-6750-gre-llm-rendering/</guid><description>Radeon RX 6750 GRE: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 6500 XT: 4 GB and 8 GB under tight memory budgets</title><link>https://retrivium.ai/journal/amd-radeon-rx-6500-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-6500-xt-llm-rendering/</guid><description>Radeon RX 6500 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 5700: an existing 8 GB RDNA 1 workstation</title><link>https://retrivium.ai/journal/amd-radeon-rx-5700-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-5700-llm-rendering/</guid><description>Radeon RX 5700: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 5600 XT: a practical 6 GB allocation test</title><link>https://retrivium.ai/journal/amd-radeon-rx-5600-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-5600-xt-llm-rendering/</guid><description>Radeon RX 5600 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 5600: identify the 6 GB non-XT OEM card</title><link>https://retrivium.ai/journal/amd-radeon-rx-5600-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-5600-llm-rendering/</guid><description>Radeon RX 5600: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 5500: the 4 GB OEM model is a separate SKU</title><link>https://retrivium.ai/journal/amd-radeon-rx-5500-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-5500-llm-rendering/</guid><description>Radeon RX 5500: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 5300: what the 3 GB OEM boundary means</title><link>https://retrivium.ai/journal/amd-radeon-rx-5300-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-5300-llm-rendering/</guid><description>Radeon RX 5300: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 5700 XT: standard and Anniversary board limits</title><link>https://retrivium.ai/journal/amd-radeon-rx-5700-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-5700-xt-llm-rendering/</guid><description>Radeon RX 5700 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX 5500 XT: official 4 GB and 8 GB configurations</title><link>https://retrivium.ai/journal/amd-radeon-rx-5500-xt-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-5500-xt-llm-rendering/</guid><description>Radeon RX 5500 XT: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon VII: 16 GB HBM2 with legacy software boundaries</title><link>https://retrivium.ai/journal/amd-radeon-vii-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-vii-llm-rendering/</guid><description>Radeon VII: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX Vega 64: an 8 GB legacy assessment</title><link>https://retrivium.ai/journal/amd-radeon-rx-vega-64-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-vega-64-llm-rendering/</guid><description>Radeon RX Vega 64: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon RX Vega 56: an 8 GB legacy assessment</title><link>https://retrivium.ai/journal/amd-radeon-rx-vega-56-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-rx-vega-56-llm-rendering/</guid><description>Radeon RX Vega 56: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon Vega Frontier Edition: air versus liquid and real physical VRAM</title><link>https://retrivium.ai/journal/amd-radeon-vega-frontier-edition-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-vega-frontier-edition-llm-rendering/</guid><description>Radeon Vega Frontier Edition: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon AI PRO R9700: 32 GB in an active-cooled workstation</title><link>https://retrivium.ai/journal/amd-radeon-ai-pro-r9700-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-ai-pro-r9700-llm-rendering/</guid><description>Radeon AI PRO R9700: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon AI PRO R9700S: 32 GB passive cooling needs a qualified host</title><link>https://retrivium.ai/journal/amd-radeon-ai-pro-r9700s-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-ai-pro-r9700s-llm-rendering/</guid><description>Radeon AI PRO R9700S: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon AI PRO R9600: 32 GB on the 150 W single-slot product</title><link>https://retrivium.ai/journal/amd-radeon-ai-pro-r9600-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-ai-pro-r9600-llm-rendering/</guid><description>Radeon AI PRO R9600: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon AI PRO R9600D: a passive 150 W host qualification</title><link>https://retrivium.ai/journal/amd-radeon-ai-pro-r9600d-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-ai-pro-r9600d-llm-rendering/</guid><description>Radeon AI PRO R9600D: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO W7900: 48 GB standard versus Dual Slot</title><link>https://retrivium.ai/journal/amd-radeon-pro-w7900-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-w7900-llm-rendering/</guid><description>Radeon PRO W7900: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO W7800: 32 GB versus 48 GB model and scene budgets</title><link>https://retrivium.ai/journal/amd-radeon-pro-w7800-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-w7800-llm-rendering/</guid><description>Radeon PRO W7800: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO W7700: 16 GB with an exact workstation support entry</title><link>https://retrivium.ai/journal/amd-radeon-pro-w7700-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-w7700-llm-rendering/</guid><description>Radeon PRO W7700: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO W7600: professional drivers do not establish LLM support</title><link>https://retrivium.ai/journal/amd-radeon-pro-w7600-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-w7600-llm-rendering/</guid><description>Radeon PRO W7600: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO W7500: 8 GB on a 70 W workstation board</title><link>https://retrivium.ai/journal/amd-radeon-pro-w7500-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-w7500-llm-rendering/</guid><description>Radeon PRO W7500: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO W7400: verify the 8 GB 55 W product</title><link>https://retrivium.ai/journal/amd-radeon-pro-w7400-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-w7400-llm-rendering/</guid><description>Radeon PRO W7400: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO W6800: the specifically listed 32 GB RDNA 2 workstation</title><link>https://retrivium.ai/journal/amd-radeon-pro-w6800-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-w6800-llm-rendering/</guid><description>Radeon PRO W6800: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO W6600: an 8 GB workstation and its 130 W specification</title><link>https://retrivium.ai/journal/amd-radeon-pro-w6600-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-w6600-llm-rendering/</guid><description>Radeon PRO W6600: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO W6400: the 4 GB workstation boundary</title><link>https://retrivium.ai/journal/amd-radeon-pro-w6400-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-w6400-llm-rendering/</guid><description>Radeon PRO W6400: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO W5700: 8 GB on an existing RDNA workstation</title><link>https://retrivium.ai/journal/amd-radeon-pro-w5700-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-w5700-llm-rendering/</guid><description>Radeon PRO W5700: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO W5500: an 8 GB 125 W workstation test</title><link>https://retrivium.ai/journal/amd-radeon-pro-w5500-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-w5500-llm-rendering/</guid><description>Radeon PRO W5500: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO VII: PRO VII is distinct from consumer Radeon VII</title><link>https://retrivium.ai/journal/amd-radeon-pro-vii-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-vii-llm-rendering/</guid><description>Radeon PRO VII: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO WX 9100: 16 GB with a versioned legacy specification</title><link>https://retrivium.ai/journal/amd-radeon-pro-wx-9100-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-wx-9100-llm-rendering/</guid><description>Radeon PRO WX 9100: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO WX 8200: 8 GB HBM2 and current backend limits</title><link>https://retrivium.ai/journal/amd-radeon-pro-wx-8200-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-wx-8200-llm-rendering/</guid><description>Radeon PRO WX 8200: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO V710: 28 GB and server or guest visibility</title><link>https://retrivium.ai/journal/amd-radeon-pro-v710-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-v710-llm-rendering/</guid><description>Radeon PRO V710: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO V620: 32 GB board memory versus guest allocation</title><link>https://retrivium.ai/journal/amd-radeon-pro-v620-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-v620-llm-rendering/</guid><description>Radeon PRO V620: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO V520: 8 GB HBM2 on a virtualization-oriented board</title><link>https://retrivium.ai/journal/amd-radeon-pro-v520-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-v520-llm-rendering/</guid><description>Radeon PRO V520: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Radeon PRO V340: dual-GPU board total is not unified VRAM</title><link>https://retrivium.ai/journal/amd-radeon-pro-v340-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-radeon-pro-v340-llm-rendering/</guid><description>Radeon PRO V340: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA L40S: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-l40s-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-l40s-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA L40S, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA L40: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-l40-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-l40-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA L40, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA L4: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-l4-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-l4-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA L4, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA L20: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-l20-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-l20-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA L20, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA A40: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-a40-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-a40-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA A40, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA A10: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-a10-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-a10-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA A10, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA A16: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-a16-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-a16-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA A16, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA A2: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-a2-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-a2-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA A2, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA A30: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-a30-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-a30-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA A30, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA A100: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-a100-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-a100-llm-rendering/</guid><description>NVIDIA A100: A100 is a family of PCIe and SXM accelerators with different memory budgets. Model residency, MIG allocation and renderer eligibility need separate checks.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA A800: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-a800-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-a800-llm-rendering/</guid><description>NVIDIA A800: A800 80 GB server configurations need their own inventory and support record. They must not be confused with the A800 40 GB Active workstation board.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA H100: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-h100-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-h100-llm-rendering/</guid><description>NVIDIA H100: H100 PCIe, SXM and NVL are different deployment choices. The NVL pair has 188 GB across two 94 GB GPUs, not a single 188 GB allocation.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA H200: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-h200-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-h200-llm-rendering/</guid><description>NVIDIA H200: H200 provides 141 GB HBM3e per GPU in published SXM and NVL configurations. That capacity is a runtime budget, not a model-size or concurrency guarantee.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA H800: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-h800-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-h800-llm-rendering/</guid><description>NVIDIA H800: H800 assessment needs the exact OEM configuration: PCIe and SXM 80 GB, or NVL 94 GB per GPU. Similar names do not establish identical host or interconnect requirements.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA H20: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-h20-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-h20-llm-rendering/</guid><description>NVIDIA H20: Official platform documentation distinguishes 96 GB and 141 GB H20 configurations. Capacity must follow the exact platform identity, not a generic H20 label.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA B200: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-b200-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-b200-llm-rendering/</guid><description>NVIDIA B200: The checked HGX reference architecture specifies 180 GB usable HBM3e per B200. Nominal capacity, MIG profiles and node totals must remain distinct.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA B300: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-b300-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-b300-llm-rendering/</guid><description>NVIDIA B300: HGX B300 publishes 288 GB HBM3e per GPU. Physical capacity, partition profiles and a multi-GPU node total describe different resource budgets.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Rubin GPU: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-rubin-gpu-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-rubin-gpu-llm-rendering/</guid><description>NVIDIA Rubin GPU: Rubin documentation publishes a 288 GB HBM4 platform GPU. Treat the specification as a platform-planning reference, with availability and software qualification checked separately.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Tesla V100: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-tesla-v100-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-tesla-v100-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Tesla V100, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Tesla V100S: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-tesla-v100s-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-tesla-v100s-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Tesla V100S, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Tesla P100: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-tesla-p100-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-tesla-p100-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Tesla P100, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Tesla P40: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-tesla-p40-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-tesla-p40-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Tesla P40, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Tesla P4: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-tesla-p4-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-tesla-p4-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Tesla P4, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Tesla T4: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-tesla-t4-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-tesla-t4-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Tesla T4, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Tesla M40: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-tesla-m40-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-tesla-m40-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Tesla M40, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Tesla M60: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-tesla-m60-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-tesla-m60-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Tesla M60, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Tesla M10: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-tesla-m10-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-tesla-m10-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Tesla M10, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA Tesla M6 and P6: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-tesla-m6-and-p6-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-tesla-m6-and-p6-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA Tesla M6 and P6, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce GTX 980 Ti: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-geforce-gtx-980-ti-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-geforce-gtx-980-ti-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA GeForce GTX 980 Ti, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA GeForce GTX TITAN X Maxwell: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/nvidia-geforce-gtx-titan-x-maxwell-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-geforce-gtx-titan-x-maxwell-llm-rendering/</guid><description>Specifications and qualification steps for NVIDIA GeForce GTX TITAN X Maxwell, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AMD Instinct MI100: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/amd-instinct-mi100-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-instinct-mi100-llm-rendering/</guid><description>Specifications and qualification steps for AMD Instinct MI100, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AMD Instinct MI210: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/amd-instinct-mi210-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-instinct-mi210-llm-rendering/</guid><description>Specifications and qualification steps for AMD Instinct MI210, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AMD Instinct MI250 and MI250X: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/amd-instinct-mi250-and-mi250x-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-instinct-mi250-and-mi250x-llm-rendering/</guid><description>Specifications and qualification steps for AMD Instinct MI250 and MI250X, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AMD Instinct MI300X: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/amd-instinct-mi300x-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-instinct-mi300x-llm-rendering/</guid><description>Specifications and qualification steps for AMD Instinct MI300X, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AMD Instinct MI300A: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/amd-instinct-mi300a-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-instinct-mi300a-llm-rendering/</guid><description>AMD Instinct MI300A: MI300A combines CPU and GPU in an APU platform with 128 GB shared HBM3. The shared budget is not dedicated GPU VRAM plus a separate 128 GB CPU pool.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AMD Instinct MI325X: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/amd-instinct-mi325x-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-instinct-mi325x-llm-rendering/</guid><description>Specifications and qualification steps for AMD Instinct MI325X, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AMD Instinct MI350P: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/amd-instinct-mi350p-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-instinct-mi350p-llm-rendering/</guid><description>Specifications and qualification steps for AMD Instinct MI350P, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AMD Instinct MI350X and MI355X: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/amd-instinct-mi350x-and-mi355x-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-instinct-mi350x-and-mi355x-llm-rendering/</guid><description>Specifications and qualification steps for AMD Instinct MI350X and MI355X, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AMD Instinct MI455X: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/amd-instinct-mi455x-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-instinct-mi455x-llm-rendering/</guid><description>AMD Instinct MI455X: AMD publishes 432 GB HBM4 for the MI455X EAM platform accelerator. Direct liquid cooling and system qualification are part of the deployment boundary.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AMD Instinct MI430X: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/amd-instinct-mi430x-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-instinct-mi430x-llm-rendering/</guid><description>AMD Instinct MI430X: AMD describes MI430X as planned for 2027 and publishes 432 GB HBM4. This is a roadmap profile, not a currently validated removable GPU recommendation.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AMD Instinct MI50 and MI60: LLM inference and server rendering boundaries</title><link>https://retrivium.ai/journal/amd-instinct-mi50-and-mi60-llm-rendering/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-instinct-mi50-and-mi60-llm-rendering/</guid><description>Specifications and qualification steps for AMD Instinct MI50 and MI60, covering memory variants, LLM backends, Cycles and system integration.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU compatibility for LLM inference and Cycles rendering</title><link>https://retrivium.ai/journal/gpu-llm-renderer-compatibility-matrix/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-llm-renderer-compatibility-matrix/</guid><description>CUDA, ROCm and a renderer backend answer different compatibility questions. Check the exact GPU, software version and workload before assigning a node.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU VRAM, board totals and shared memory: how to read specifications</title><link>https://retrivium.ai/journal/gpu-vram-board-module-shared-memory/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-vram-board-module-shared-memory/</guid><description>Per-GPU VRAM, a multi-GPU board total, module memory and unified CPU/GPU memory are different budgets. Adding the numbers can create a false model-fit claim.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Desktop GPU, workstation or server accelerator: qualify the host</title><link>https://retrivium.ai/journal/gpu-server-chassis-cooling-qualification/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-server-chassis-cooling-qualification/</guid><description>A compatible software backend does not prove that a GPU is suitable for a server chassis. Cooling, power, mechanics and manufacturer validation need their own assessment.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Legacy GPUs for LLMs and rendering: experimental versus supported</title><link>https://retrivium.ai/journal/legacy-gpu-inference-rendering-boundaries/</link><guid isPermaLink="true">https://retrivium.ai/journal/legacy-gpu-inference-rendering-boundaries/</guid><description>Older NVIDIA and Radeon GPUs can require legacy software or conditional backend experiments. Missing current certification is different from universal inability to compute.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Sharing GPUs between LLM inference and server rendering</title><link>https://retrivium.ai/journal/gpu-llm-rendering-workload-scheduling/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-llm-rendering-workload-scheduling/</guid><description>A GPU that passes separate LLM and render tests may still fail a mixed workload. Schedule by memory, latency and supported isolation rather than peak utilisation alone.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA and AMD GPU catalogue for LLM inference and server rendering</title><link>https://retrivium.ai/journal/nvidia-amd-gpu-catalog/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-amd-gpu-catalog/</guid><description>194 model profiles and grouped variants, plus six guides: NVIDIA, Radeon and Instinct memory, software boundaries, cooling and workload qualification in English and Russian.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Runpod for LLMs: when to choose Pods or Serverless</title><link>https://retrivium.ai/journal/runpod-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/runpod-guide/</guid><description>Compare Runpod Pods and Serverless for model serving: environment control, storage, startup, worker billing and a reproducible first pilot.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AWS for LLM inference: evaluating GPUs in Amazon EC2</title><link>https://retrivium.ai/journal/aws-gpu-hosting-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/aws-gpu-hosting-guide/</guid><description>Evaluate GPU EC2 instances by accelerator family, region, purchase option, related resources and the distinction between cloud rental and an owned GPU pool.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Hetzner for LLMs: evaluating a dedicated GPU server</title><link>https://retrivium.ai/journal/hetzner-hosting-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/hetzner-hosting-guide/</guid><description>Evaluate Hetzner GEX GPU servers by node configuration, location, setup and recurring charges, self-managed operations and a model acceptance test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vast.ai GPUs: evaluating marketplace offers</title><link>https://retrivium.ai/journal/vast-ai-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/vast-ai-guide/</guid><description>Read Vast.ai inference offers by host configuration, rental type, storage and reproducibility, while keeping GPU renter and equipment-provider roles distinct.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Lambda Cloud: planning a GPU virtual-machine pilot</title><link>https://retrivium.ai/journal/lambda-cloud-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/lambda-cloud-guide/</guid><description>Evaluate Lambda Cloud On-Demand through VM configuration, region, resource lifecycle, storage and the complete budget for a repeatable language-model test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CoreWeave inference: choose the management layer first</title><link>https://retrivium.ai/journal/coreweave-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/coreweave-guide/</guid><description>Evaluate CoreWeave infrastructure and dedicated inference through team responsibilities, purchasing units, complete costs and the selected service-level test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DigitalOcean and Paperspace: distinguish the GPU products</title><link>https://retrivium.ai/journal/digitalocean-paperspace-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/digitalocean-paperspace-guide/</guid><description>Distinguish DigitalOcean GPU Droplets from Paperspace Machines, Notebooks and Deployments, including their billing catalogues and a first LLM pilot.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Google Cloud GPU: regions and quotas before model launch</title><link>https://retrivium.ai/journal/google-cloud-gpu-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/google-cloud-gpu-guide/</guid><description>Prepare a Compute Engine GPU pilot through compatible configuration, regional availability, quotas, software and the complete resource lifecycle.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Azure GPUs for LLMs: selecting a compute VM series</title><link>https://retrivium.ai/journal/azure-gpu-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/azure-gpu-guide/</guid><description>Evaluate Azure GPU virtual machines by compute versus graphics series, region, software environment and the connected operating expenses of a language model.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OVHcloud GPUs: distinguishing cloud instances from other services</title><link>https://retrivium.ai/journal/ovhcloud-gpu-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/ovhcloud-gpu-guide/</guid><description>Evaluate OVHcloud Public Cloud GPU through product, configuration, region, charging model and the boundary between infrastructure and managed AI services.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Scaleway GPUs: from a prepared image to a repeatable pilot</title><link>https://retrivium.ai/journal/scaleway-gpu-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/scaleway-gpu-guide/</guid><description>Evaluate Scaleway GPU Instances by configuration, image, region, resource charges and a repeatable launch of your language model.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Nebius AI Cloud: planning growth from a VM to a GPU pool</title><link>https://retrivium.ai/journal/nebius-gpu-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/nebius-gpu-guide/</guid><description>Evaluate Nebius AI Cloud through VMs, cluster interconnects, capacity purchasing, storage and the separate validation needed to expand beyond a small test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Fluidstack: evaluating large-scale AI infrastructure</title><link>https://retrivium.ai/journal/fluidstack-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/fluidstack-guide/</guid><description>Assess Fluidstack through its current infrastructure focus, project scale, customer responsibilities and commercial inquiry route rather than assuming single-VM rental.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vultr Cloud GPU: checking plan, region and image</title><link>https://retrivium.ai/journal/vultr-gpu-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/vultr-gpu-guide/</guid><description>Evaluate Vultr Cloud GPU by plan, location, system image, network route, complete expenses and repeatable model deployment before scaling a workload.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Oracle Cloud GPUs: VMs and bare metal for an owned model</title><link>https://retrivium.ai/journal/oracle-cloud-gpu-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/oracle-cloud-gpu-guide/</guid><description>Evaluate OCI GPUs through VM and bare-metal configurations, accelerator software, region, host resources and validation before expanding capacity.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Crusoe Cloud: infrastructure or managed inference?</title><link>https://retrivium.ai/journal/crusoe-cloud-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/crusoe-cloud-guide/</guid><description>Distinguish Crusoe Infrastructure Cloud and Managed AI: self-managed VMs and clusters, managed deployments, payment units and model responsibilities.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Latitude.sh for LLMs: evaluating Metal GPU</title><link>https://retrivium.ai/journal/latitude-sh-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/latitude-sh-guide/</guid><description>Evaluate Latitude.sh Metal GPU through dedicated configuration, location, management, storage and the full deployment-to-completion workflow.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Hyperstack: GPU VM costs begin with the resource lifecycle</title><link>https://retrivium.ai/journal/hyperstack-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/hyperstack-guide/</guid><description>Evaluate Hyperstack GPU VMs by flavour, region, disks, instance states and billing, then measure the complete cost of a language-model test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>TensorDock: evaluating GPU VMs across a host network</title><link>https://retrivium.ai/journal/tensor-dock-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/tensor-dock-guide/</guid><description>Evaluate TensorDock by specific host, configurable VM resources, complete charges and the separate responsibilities of customers and equipment owners.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CUDO Compute in 2026: current services and older instructions</title><link>https://retrivium.ai/journal/cudo-compute-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/cudo-compute-guide/</guid><description>Understand CUDO Compute’s public on-demand closure, current enterprise infrastructure focus and the questions needed before planning an AI project.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Five GPU clouds for a first pilot: building a shortlist</title><link>https://retrivium.ai/journal/top-gpu-clouds-first-pilot/</link><guid isPermaLink="true">https://retrivium.ai/journal/top-gpu-clouds-first-pilot/</guid><description>An editorial shortlist for a bounded LLM pilot: Runpod, Lambda, DigitalOcean, Hyperstack and AWS, with selection criteria and a matched-test plan.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Four providers for European GPU deployment</title><link>https://retrivium.ai/journal/top-european-infrastructure-providers/</link><guid isPermaLink="true">https://retrivium.ai/journal/top-european-infrastructure-providers/</guid><description>Investigate Hetzner, OVHcloud, Scaleway and Hyperstack for European GPU placement, checking official locations, resource formats, data routes and operations.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Dedicated GPUs for LLMs: four different purchasing formats</title><link>https://retrivium.ai/journal/top-dedicated-servers-llm/</link><guid isPermaLink="true">https://retrivium.ai/journal/top-dedicated-servers-llm/</guid><description>Compare Hetzner, Latitude.sh, Oracle Cloud and CoreWeave dedicated resources: physical servers, bare-metal configurations and dedicated model endpoints.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Four serverless approaches to GPU inference</title><link>https://retrivium.ai/journal/top-serverless-gpu-providers/</link><guid isPermaLink="true">https://retrivium.ai/journal/top-serverless-gpu-providers/</guid><description>Investigate Runpod, Vast.ai, Modal and Crusoe serverless workflows: owned code, workers, managed model APIs, cold starts and different charging units.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Runpod or Vast.ai: compare the task, not one price</title><link>https://retrivium.ai/journal/runpod-vs-vast-ai/</link><guid isPermaLink="true">https://retrivium.ai/journal/runpod-vs-vast-ai/</guid><description>Compare Runpod and Vast.ai through instance format, serverless, specific configurations, portability and the separate GPU-equipment-owner scenario.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AWS, Google Cloud or Azure: comparing GPUs for LLMs</title><link>https://retrivium.ai/journal/aws-vs-google-cloud-vs-azure-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/aws-vs-google-cloud-vs-azure-gpu/</guid><description>Compare AWS, Google Cloud and Azure for an owned model using GPU families, regions, access, connected services and a matched end-to-end application test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Hetzner, OVHcloud and Scaleway: comparing GPU infrastructure</title><link>https://retrivium.ai/journal/hetzner-vs-ovhcloud-vs-scaleway/</link><guid isPermaLink="true">https://retrivium.ai/journal/hetzner-vs-ovhcloud-vs-scaleway/</guid><description>Compare Hetzner GEX, OVHcloud Public Cloud GPU and Scaleway GPU Instances by resource format, operations, period, region and one model’s requirements.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Specialist GPU cloud or hyperscaler: choosing the right product</title><link>https://retrivium.ai/journal/specialist-vs-hyperscaler-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/specialist-vs-hyperscaler-gpu/</guid><description>Compare Runpod and Nebius with AWS, Google Cloud and Azure through product focus, existing dependencies, control and an end-to-end application test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Five providers for small GPU teams: choose by the work involved</title><link>https://retrivium.ai/journal/top-providers-small-gpu-teams/</link><guid isPermaLink="true">https://retrivium.ai/journal/top-providers-small-gpu-teams/</guid><description>Investigate Runpod, Lambda, DigitalOcean, Hyperstack and Modal for small teams by maintenance duties, cost control and repeatable model launches.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A GPU-provider shortlist: a method for verifiable selection</title><link>https://retrivium.ai/journal/gpu-cloud-shortlist-method/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-cloud-shortlist-method/</guid><description>Build a current GPU shortlist by verifying product, resource format, starting route, restrictions, complete estimates and matched pilot results.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CPU or GPU hosting: which resource does your AI task need?</title><link>https://retrivium.ai/journal/cpu-vs-gpu-hosting/</link><guid isPermaLink="true">https://retrivium.ai/journal/cpu-vs-gpu-hosting/</guid><description>Separate CPU and GPU tasks in AI hosting: data processing, retrieval, generation and measured constraints before renting or proposing equipment.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Memory-optimized hosting: when more system RAM is useful</title><link>https://retrivium.ai/journal/memory-optimized-hosting/</link><guid isPermaLink="true">https://retrivium.ai/journal/memory-optimized-hosting/</guid><description>Choose high-RAM hosting for databases, caches and data preparation while separating memory capacity from CPU performance and GPU device memory.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RAM and VRAM: which memory matters for an AI server?</title><link>https://retrivium.ai/journal/ram-vs-vram/</link><guid isPermaLink="true">https://retrivium.ai/journal/ram-vs-vram/</guid><description>Distinguish host system RAM from GPU device memory and document an AI server without incorrectly combining them into one memory-capacity figure.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Compute-optimized hosting: when the processor is the constraint</title><link>https://retrivium.ai/journal/compute-optimized-hosting/</link><guid isPermaLink="true">https://retrivium.ai/journal/compute-optimized-hosting/</guid><description>Evaluate intensive CPU hosting through working sets, threads, sustained load and comparisons with higher-RAM configurations before selecting equipment.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Storage-optimized hosting: when disks constrain an AI system</title><link>https://retrivium.ai/journal/storage-optimized-hosting/</link><guid isPermaLink="true">https://retrivium.ai/journal/storage-optimized-hosting/</guid><description>Select servers for intensive data access by checking local and remote storage, model loading, indexes and recovery rather than disk capacity alone.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Arm and x86 inference: comparing CPU architectures</title><link>https://retrivium.ai/journal/arm-vs-x86-inference/</link><guid isPermaLink="true">https://retrivium.ai/journal/arm-vs-x86-inference/</guid><description>Test Arm and x86 on AI workloads through software compatibility, vCPU allocation, memory and application measurements rather than processor names.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU hosting, GPU servers and model APIs: what are you renting?</title><link>https://retrivium.ai/journal/gpu-hosting-vs-gpu-server/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-hosting-vs-gpu-server/</guid><description>Distinguish GPU-machine rental, managed environments and model API access so responsibilities, costs and equipment offers describe the complete service.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>When to test CPU LLM inference before buying a GPU</title><link>https://retrivium.ai/journal/cpu-llm-inference-use-cases/</link><guid isPermaLink="true">https://retrivium.ai/journal/cpu-llm-inference-use-cases/</guid><description>Explore bounded CPU-inference scenarios: low traffic, compatibility checks, background work and matched end-to-end comparison before accelerator procurement.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LLM memory bandwidth: why gigabytes are not enough</title><link>https://retrivium.ai/journal/memory-bandwidth-llm/</link><guid isPermaLink="true">https://retrivium.ai/journal/memory-bandwidth-llm/</guid><description>Evaluate CPU and GPU memory through capacity, access speed and actual workloads rather than replacing model tests with advertised hardware specifications.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVMe for model serving: where a faster disk changes results</title><link>https://retrivium.ai/journal/nvme-for-model-serving/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvme-for-model-serving/</guid><description>Evaluate local NVMe through weight loading, artifact caches, updates and recovery, distinguishing storage speed from warm-model generation performance.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NUMA in GPU servers: why resource placement matters</title><link>https://retrivium.ai/journal/numa-and-gpu-servers/</link><guid isPermaLink="true">https://retrivium.ai/journal/numa-and-gpu-servers/</guid><description>Describe CPU, RAM and GPU relationships in a multi-socket inference server, then test process placement reproducibly before replacing hardware.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>PCIe and GPU hosting: when the connection limits a model</title><link>https://retrivium.ai/journal/gpu-pcie-bandwidth/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-pcie-bandwidth/</guid><description>Assess GPU connections to the host and other devices, separating loading, data transfers, distributed execution and the actual server topology.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Spot or on-demand GPUs: accounting for interruptions</title><link>https://retrivium.ai/journal/spot-vs-on-demand-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/spot-vs-on-demand-gpu/</guid><description>Compare interruptible and ordinary GPU rental through recovery, repeated work, replacement availability and the cost of useful completed jobs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Reserved GPUs and flexible capacity: what are you committing to?</title><link>https://retrivium.ai/journal/reserved-vs-flexible-capacity/</link><guid isPermaLink="true">https://retrivium.ai/journal/reserved-vs-flexible-capacity/</guid><description>Separate GPU availability from financial commitments, then compare duration, change rules, idle costs and a flexible pilot before reserving capacity.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Serverless GPUs or an always-ready replica: choosing an inference mode</title><link>https://retrivium.ai/journal/serverless-vs-always-on-inference/</link><guid isPermaLink="true">https://retrivium.ai/journal/serverless-vs-always-on-inference/</guid><description>Compare on-demand startup with an always-ready model across cold starts, idle intervals, baseline capacity and the complete user experience.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A hybrid CPU/GPU architecture: splitting an AI service by task</title><link>https://retrivium.ai/journal/cpu-gpu-hybrid-architecture/</link><guid isPermaLink="true">https://retrivium.ai/journal/cpu-gpu-hybrid-architecture/</guid><description>Map application stages to CPU and GPU resources, then compare a single-machine service with a split deployment and its full operating cost.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A high-RAM RAG server: deciding what to keep in memory</title><link>https://retrivium.ai/journal/high-ram-rag-servers/</link><guid isPermaLink="true">https://retrivium.ai/journal/high-ram-rag-servers/</guid><description>Separate RAG retrieval and generation, size indexes and update peaks, then evaluate memory configurations against relevance and complete-response latency.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vector-database memory: choosing RAM and storage for retrieval</title><link>https://retrivium.ai/journal/vector-database-memory-hosting/</link><guid isPermaLink="true">https://retrivium.ai/journal/vector-database-memory-hosting/</guid><description>Size vector-database memory by vectors, indexes, payload, filters and operating state, then compare RAM, storage and indexing alternatives.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RAM for AI data preparation: avoiding paid-for idle memory</title><link>https://retrivium.ai/journal/ram-for-data-preprocessing/</link><guid isPermaLink="true">https://retrivium.ai/journal/ram-for-data-preprocessing/</guid><description>Measure data transformations, batch size, workers, streaming and temporary storage before choosing a larger-memory preprocessing server.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPUs in Kubernetes: scheduling CPU, RAM and accelerators together</title><link>https://retrivium.ai/journal/kubernetes-gpu-scheduling/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-gpu-scheduling/</guid><description>Assess Kubernetes GPU jobs using the complete node configuration, placement constraints, model readiness and heterogeneous hardware rather than card count.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU containers or virtual machines: what to check before deployment</title><link>https://retrivium.ai/journal/gpu-containers-vs-vms/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-containers-vs-vms/</guid><description>Compare GPU containers and VMs through compatibility, device access, responsibilities, repeatable tests, updates and recovery before choosing a deployment.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>MIG and time-slicing: sharing a GPU without confusing guarantees</title><link>https://retrivium.ai/journal/gpu-mig-vs-time-slicing/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-mig-vs-time-slicing/</guid><description>Distinguish MIG from time-slicing, then test workload profiles, neighboring effects, host resources and accounting for a shared GPU.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Serving LoRA adapters: estimating GPU-server capacity</title><link>https://retrivium.ai/journal/lora-serving-capacity/</link><guid isPermaLink="true">https://retrivium.ai/journal/lora-serving-capacity/</guid><description>Estimate LoRA serving through the base model, adapter compatibility, switching, mixed traffic, memory and task-specific quality checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU hosting for multimodal models: count more than text</title><link>https://retrivium.ai/journal/multimodal-gpu-hosting/</link><guid isPermaLink="true">https://retrivium.ai/journal/multimodal-gpu-hosting/</guid><description>Evaluate a specific multimodal workload through supported inputs, preparation, file transfer, memory, service limits and useful output.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Hosting batch inference: using GPUs on a schedule</title><link>https://retrivium.ai/journal/batch-inference-hosting/</link><guid isPermaLink="true">https://retrivium.ai/journal/batch-inference-hosting/</guid><description>Plan scheduled GPU batches through work-unit checks, availability windows, batch growth, restart behavior and cost per completed dataset.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU autoscaling: a free card is not a ready replica</title><link>https://retrivium.ai/journal/autoscaling-gpu-cold-start/</link><guid isPermaLink="true">https://retrivium.ai/journal/autoscaling-gpu-cold-start/</guid><description>Measure GPU autoscaling from allocation through weights, preparation and useful output, including queue behavior and a failed-start retry.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AI service network traffic: accounting for egress before GPU placement</title><link>https://retrivium.ai/journal/cloud-egress-model-serving/</link><guid isPermaLink="true">https://retrivium.ai/journal/cloud-egress-model-serving/</guid><description>Map weights, user inputs, storage, responses, backups and updates before comparing GPU placement and complete operating costs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CPU hosting for RAG: four options for a technical comparison</title><link>https://retrivium.ai/journal/top-cpu-hosting-rag/</link><guid isPermaLink="true">https://retrivium.ai/journal/top-cpu-hosting-rag/</guid><description>An editorial comparison of AWS C8i, Google C4, Azure Falsv7 and Hetzner CCX, with CPU semantics and a reproducible RAG pilot.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Memory-optimized hosting: four high-RAM options to compare</title><link>https://retrivium.ai/journal/top-memory-optimized-clouds/</link><guid isPermaLink="true">https://retrivium.ai/journal/top-memory-optimized-clouds/</guid><description>Compare AWS R8i, Google M4, Azure Esv7 and Azure Epsv6 through working-set requirements, CPU compatibility and complete operating costs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LLM hosting architectures: five arrangements for different tasks</title><link>https://retrivium.ai/journal/top-hosting-architectures-llm/</link><guid isPermaLink="true">https://retrivium.ai/journal/top-hosting-architectures-llm/</guid><description>Compare five AI hosting arrangements by readiness, resource roles, data boundaries, failure handling and the unit of useful output.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter: model access and its role for a GPU pool</title><link>https://retrivium.ai/journal/openrouter-platform-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-platform-guide/</guid><description>Understand OpenRouter from the developer and inference-operator sides, separating API access, routing, accounting and provider onboarding.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter provider routing: defining permitted routes</title><link>https://retrivium.ai/journal/openrouter-provider-routing/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-provider-routing/</guid><description>Define mandatory OpenRouter route conditions before preferences, then test provider selection, model fallbacks and complete-request outcomes.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Requesty: a managed LLM gateway for routing and team access</title><link>https://retrivium.ai/journal/requesty-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/requesty-guide/</guid><description>Evaluate Requesty with one model scenario, explicit fallback policies, BYOK ownership, usage reconciliation and a clear data-flow review.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Portkey and Prisma AIRS AI Gateway: functions and product boundaries</title><link>https://retrivium.ai/journal/portkey-ai-gateway-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/portkey-ai-gateway-guide/</guid><description>Evaluate Portkey and Prisma AIRS AI Gateway through product naming, deployment edition, routing policies, telemetry and operating responsibilities.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LiteLLM Proxy: when to operate your own model gateway</title><link>https://retrivium.ai/journal/litellm-proxy-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/litellm-proxy-guide/</guid><description>Assess LiteLLM Proxy through request boundaries, virtual-key policies, routing, usage reconciliation and the operating cost of a self-hosted gateway.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vercel AI Gateway: common model access for an application</title><link>https://retrivium.ai/journal/vercel-ai-gateway-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/vercel-ai-gateway-guide/</guid><description>Evaluate Vercel AI Gateway through API compatibility, provider policy, BYOK, complete usage costs and the distinction between consuming and selling inference.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Cloudflare AI Gateway: routes, observability and unified billing</title><link>https://retrivium.ai/journal/cloudflare-ai-gateway-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/cloudflare-ai-gateway-guide/</guid><description>Separate Cloudflare AI Gateway, Workers AI, external providers, BYOK and unified billing, then test current interfaces and complete costs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Kong AI Gateway: LLM traffic within API infrastructure</title><link>https://retrivium.ai/journal/kong-ai-gateway-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/kong-ai-gateway-guide/</guid><description>Assess Kong AI Gateway through control and data planes, team policies, identity, edition-specific functions and operational recovery.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Helicone AI Gateway: routing with observability</title><link>https://retrivium.ai/journal/helicone-ai-gateway-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/helicone-ai-gateway-guide/</guid><description>Evaluate Helicone as a gateway and observation layer, preserving actual routes, attempt timelines, metric sources and data-retention settings.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Amazon Bedrock: model access within AWS infrastructure</title><link>https://retrivium.ai/journal/bedrock-model-access-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/bedrock-model-access-guide/</guid><description>Evaluate a specific Bedrock model, endpoint, region and application role, then compare complete task costs and operating requirements.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vertex AI Model Garden: reading the current Google Cloud catalog</title><link>https://retrivium.ai/journal/vertex-ai-model-garden-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/vertex-ai-model-garden-guide/</guid><description>Read the current Model Garden documentation through exact model cards, managed and self-deployed paths, project restrictions and complete pilot costs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Azure AI Foundry and Microsoft Foundry Models: choosing execution</title><link>https://retrivium.ai/journal/azure-ai-foundry-models-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/azure-ai-foundry-models-guide/</guid><description>Distinguish Foundry model categories, deployment modes, project access and complete costs while preserving the familiar Azure AI Foundry search name.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Together AI: serverless and dedicated inference for open models</title><link>https://retrivium.ai/journal/together-ai-platform-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/together-ai-platform-guide/</guid><description>Compare Together AI execution modes through workload goals, serverless traffic, model capabilities, useful output and complete operating scenarios.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Fireworks AI: comparing serverless and deployments</title><link>https://retrivium.ai/journal/fireworks-ai-platform-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/fireworks-ai-platform-guide/</guid><description>Evaluate Fireworks execution modes with representative traffic, usage reconciliation, model quality and the lifecycle of a managed inference service.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Hugging Face Inference Providers: models, routes and billing</title><link>https://retrivium.ai/journal/hugging-face-inference-providers-guide/</link><guid isPermaLink="true">https://retrivium.ai/journal/hugging-face-inference-providers-guide/</guid><description>Separate Hub weights, Inference Providers and dedicated endpoints, then verify model tasks, actual executors, billing routes and full deployment costs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Five managed LLM routing platforms: choosing by task</title><link>https://retrivium.ai/journal/top-managed-llm-routing-platforms/</link><guid isPermaLink="true">https://retrivium.ai/journal/top-managed-llm-routing-platforms/</guid><description>Compare five managed LLM-access options by client requirements, payment paths, routing, observability and the same bounded workload.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Four self-hosted AI gateways: LiteLLM, Portkey, Kong and Agent Router</title><link>https://retrivium.ai/journal/top-self-hosted-ai-gateways/</link><guid isPermaLink="true">https://retrivium.ai/journal/top-self-hosted-ai-gateways/</guid><description>Compare four self-hosted gateway options through exact editions, data paths, policies, operating actions and complete maintenance responsibilities.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter or Requesty: comparing managed LLM access</title><link>https://retrivium.ai/journal/openrouter-vs-requesty/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-vs-requesty/</guid><description>Compare OpenRouter and Requesty on the same task, explicit policies, BYOK, incident evidence and the separate process of selling owned inference.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter and Portkey: catalog access or AI-traffic governance</title><link>https://retrivium.ai/journal/openrouter-vs-portkey/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-vs-portkey/</guid><description>Compare OpenRouter and Portkey by intended role, deployment, private endpoints, policies, operating responsibility and inference-sales boundaries.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter or LiteLLM: managed access and an owned gateway</title><link>https://retrivium.ai/journal/openrouter-vs-litellm/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-vs-litellm/</guid><description>Compare OpenRouter and LiteLLM Proxy through control boundaries, complete costs, layered routing, incident work and recovery.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vercel and Cloudflare AI Gateway: comparing managed gateways</title><link>https://retrivium.ai/journal/vercel-vs-cloudflare-ai-gateway/</link><guid isPermaLink="true">https://retrivium.ai/journal/vercel-vs-cloudflare-ai-gateway/</guid><description>Compare Vercel and Cloudflare with the same application contract, allowed routes, payment path, incident work and complete costs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Bedrock, Vertex Model Garden and Foundry: cloud approaches compared</title><link>https://retrivium.ai/journal/bedrock-vs-vertex-vs-foundry/</link><guid isPermaLink="true">https://retrivium.ai/journal/bedrock-vs-vertex-vs-foundry/</guid><description>Compare cloud model platforms through an equivalent task, exact execution mode, project access, full operating period and unresolved conditions.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Together, Fireworks and OpenRouter: comparing inference roles</title><link>https://retrivium.ai/journal/together-vs-fireworks-vs-openrouter/</link><guid isPermaLink="true">https://retrivium.ai/journal/together-vs-fireworks-vs-openrouter/</guid><description>Separate inference execution from routing when comparing Together, Fireworks and OpenRouter on model capabilities, fallbacks and complete task costs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>BYOK or managed billing: who pays for the model request?</title><link>https://retrivium.ai/journal/byok-vs-managed-billing/</link><guid isPermaLink="true">https://retrivium.ai/journal/byok-vs-managed-billing/</guid><description>Trace customer and managed credentials across billing sources, account limits, fallback, reconciliation and credential ownership.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Model routing and provider routing: two different decisions</title><link>https://retrivium.ai/journal/model-routing-vs-provider-routing/</link><guid isPermaLink="true">https://retrivium.ai/journal/model-routing-vs-provider-routing/</guid><description>Separate changing the model from changing its executor, then test quality, route constraints, fallback histories and cost independently.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The full cost of an LLM router: beyond token prices</title><link>https://retrivium.ai/journal/token-router-total-cost/</link><guid isPermaLink="true">https://retrivium.ai/journal/token-router-total-cost/</guid><description>Calculate routing cost per useful result across inference, gateway features, storage, retries and the actual work needed to operate the integration.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Reconciling tokens and billing in an LLM router</title><link>https://retrivium.ai/journal/router-billing-token-accounting/</link><guid isPermaLink="true">https://retrivium.ai/journal/router-billing-token-accounting/</guid><description>Trace application tasks, attempts, usage fields and final charges, including streaming, credentials, cached input and late accounting adjustments.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Comparing LLM-router data policies</title><link>https://retrivium.ai/journal/router-data-policy-comparison/</link><guid isPermaLink="true">https://retrivium.ai/journal/router-data-policy-comparison/</guid><description>Map content, telemetry, providers, retention, fallback and geography separately when checking a router data policy and its actual configuration.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LLM-router fallback and limits: testing resilience</title><link>https://retrivium.ai/journal/router-failover-and-rate-limits/</link><guid isPermaLink="true">https://retrivium.ai/journal/router-failover-and-rate-limits/</guid><description>Test router resilience through total deadlines, compatible backup targets, error categories, traffic bursts, interrupted streams and recovery to normal behavior.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Choosing a token-sales channel for an owned GPU pool</title><link>https://retrivium.ai/journal/choosing-token-sales-channel/</link><guid isPermaLink="true">https://retrivium.ai/journal/choosing-token-sales-channel/</guid><description>Evaluate seller onboarding separately from API consumption, then verify requirements, accounting, commercial readiness and actual demand before expanding GPUs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Mapping a company’s idle GPUs for a new service</title><link>https://retrivium.ai/journal/idle-gpu-resource-map/</link><guid isPermaLink="true">https://retrivium.ai/journal/idle-gpu-resource-map/</guid><description>Create a practical GPU availability map linking each machine to ownership, operating windows, constraints, costs and a dated next check.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU-node acceptance: evidence beyond an attractive benchmark</title><link>https://retrivium.ai/journal/gpu-acceptance-evidence/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-acceptance-evidence/</guid><description>Document GPU acceptance through received configuration, diagnostics, service tests, workload conditions, recovery and clearly scoped decisions.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A GPU maintenance budget: planning beyond startup</title><link>https://retrivium.ai/journal/gpu-maintenance-budget/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-maintenance-budget/</guid><description>Build a maintenance budget from regular work, incident scenarios, monitoring, repair responsibilities, spending authority and spare-part ownership.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Providing a GPU or handing over operations: what the owner retains</title><link>https://retrivium.ai/journal/gpu-owner-managed-operation/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-owner-managed-operation/</guid><description>Separate equipment authority, site services and software operation, then agree access, changes, incident duties and return of the machine.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A short GPU-partner brief: equipment, task and budget</title><link>https://retrivium.ai/journal/gpu-partner-brief-template/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-partner-brief-template/</guid><description>Prepare a concise GPU partnership brief covering the resource, desired decision, constraints, unknowns and evidence needed for the next stage.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Research data and an external GPU pilot: defining the boundary</title><link>https://retrivium.ai/journal/research-data-boundaries-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/research-data-boundaries-gpu/</guid><description>Separate laboratory data from a GPU pilot through explicit directories, permissions, test datasets, logs, incident procedures and access termination.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A reference GPU-node configuration for a small pool</title><link>https://retrivium.ai/journal/gpu-reference-configuration/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-reference-configuration/</guid><description>Document one reproducible GPU node through hardware, software, workload, metrics and meaningful deviations before evaluating additional servers.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Energy per LLM request: measuring without false precision</title><link>https://retrivium.ai/journal/measuring-energy-per-inference/</link><guid isPermaLink="true">https://retrivium.ai/journal/measuring-energy-per-inference/</guid><description>Measure energy per useful inference task with explicit device or server boundaries, time windows, power integration and repeatable workload conditions.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A GPU-pilot spending limit: knowing when to decide again</title><link>https://retrivium.ai/journal/gpu-pilot-spending-limit/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-pilot-spending-limit/</guid><description>Set a GPU-pilot budget with detailed cost categories, observable thresholds, delayed-accounting awareness and a tested completion procedure.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Funding an existing GPU or buying a new one: where to start</title><link>https://retrivium.ai/journal/existing-gpu-vs-new-purchase/</link><guid isPermaLink="true">https://retrivium.ai/journal/existing-gpu-vs-new-purchase/</guid><description>Compare an existing GPU node and new purchase against the same task, preparation needs, operating expenses, acceptance and the next measurable decision.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vast.ai Hosting Setup: Prepare a Verifiable Server Record</title><link>https://retrivium.ai/journal/vast-host-preflight-files/</link><guid isPermaLink="true">https://retrivium.ai/journal/vast-host-preflight-files/</guid><description>Prepare a Vast.ai host record covering hardware, existing workloads, site limits and change permissions before installing hosting software.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vast.ai Host Verification: What Each Stage Actually Shows</title><link>https://retrivium.ai/journal/vast-host-verification-stages/</link><guid isPermaLink="true">https://retrivium.ai/journal/vast-host-verification-stages/</guid><description>Understand Vast.ai host verification by separating hardware records, self-test results and platform status without assuming approval or demand.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vast.ai Offer End Date: Plan When Your Server Must Return</title><link>https://retrivium.ai/journal/vast-host-offer-end-date/</link><guid isPermaLink="true">https://retrivium.ai/journal/vast-host-offer-end-date/</guid><description>Plan a Vast.ai offer end date around the time your server must return to its owner, including workload completion and environment checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Scheduling Maintenance for a Vast.ai Host</title><link>https://retrivium.ai/journal/vast-host-maintenance-window/</link><guid isPermaLink="true">https://retrivium.ai/journal/vast-host-maintenance-window/</guid><description>Plan a Vast.ai host maintenance window with workload checks, UTC timestamps, a bounded change and evidence of restored readiness.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Test Your Own Vast.ai Host Through a Rental</title><link>https://retrivium.ai/journal/vast-host-self-rental-test/</link><guid isPermaLink="true">https://retrivium.ai/journal/vast-host-self-rental-test/</guid><description>Test your own Vast.ai host with a bounded client workflow, distinguishing self-testing, default jobs and self-rental, then verify resource release.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU Server Electricity Costs: Reconcile an Actual Bill</title><link>https://retrivium.ai/journal/own-server-electricity-invoice/</link><guid isPermaLink="true">https://retrivium.ai/journal/own-server-electricity-invoice/</guid><description>Calculate GPU server electricity from measured operating modes, then reconcile energy, tariffs and included hosting charges without double counting.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Calculate the Cost of Making Your GPU Available</title><link>https://retrivium.ai/journal/gpu-availability-cost-per-hour/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-availability-cost-per-hour/</guid><description>Calculate GPU availability cost per hour using a defined period, verified available hours and consistently allocated operating expenses.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU Colocation Power Budget: Check the Site Limit</title><link>https://retrivium.ai/journal/gpu-site-power-budget/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-site-power-budget/</guid><description>Assess a GPU colocation power budget using the site limit, complete system requirements and measurements from several operating modes.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Offer Your GPU Server Without Relocating It</title><link>https://retrivium.ai/journal/gpu-owner-no-relocation-brief/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-owner-no-relocation-brief/</guid><description>Describe a GPU server offered from its existing location: remote access, physical maintenance, schedule, network and responsibilities.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A GPU Availability Calendar Across Time Zones</title><link>https://retrivium.ai/journal/gpu-weekly-availability-calendar/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-weekly-availability-calendar/</guid><description>Build a GPU availability calendar with named time zones, UTC timestamps, preparation windows, reservations and versioned exceptions.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Build a GPU Inventory CSV with nvidia-smi</title><link>https://retrivium.ai/journal/gpu-inventory-csv-from-nvidia-smi/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-inventory-csv-from-nvidia-smi/</guid><description>Export a small GPU inventory CSV with nvidia-smi while preserving units, timestamp and the distinction between configuration and health evidence.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU Operator Handover: Issue and Revoke Access Keys</title><link>https://retrivium.ai/journal/gpu-operator-key-handover/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-operator-key-handover/</guid><description>Plan a GPU operator handover with named accounts, key fingerprints, approved permissions, expiry and verification of revoked access.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU Idle Reports: Separate Waiting, Outages and Reservations</title><link>https://retrivium.ai/journal/gpu-idle-report-state-taxonomy/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-idle-report-state-taxonomy/</guid><description>Classify GPU time as external work, ready waiting, owner reservation, maintenance or unavailability before explaining idle time.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Return a GPU to Its Research Window</title><link>https://retrivium.ai/journal/gpu-research-window-handover/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-research-window-handover/</guid><description>Return a shared GPU before a research window by stopping intake, completing work, checking resources and obtaining acceptance from the researcher.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU Cloud Credits Expiring Soon: Plan a Useful Pilot</title><link>https://retrivium.ai/journal/gpu-cloud-credit-expiry-plan/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-cloud-credit-expiry-plan/</guid><description>Use expiring GPU cloud credits for a bounded, eligible experiment while checking account rules, service coverage and costs outside the credit.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Grant Funded GPUs: Document Remote Access for Review</title><link>https://retrivium.ai/journal/gpu-grant-remote-access-appendix/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-grant-remote-access-appendix/</guid><description>Document remote access to grant funded GPUs with a specific purpose, action matrix, data boundary, expiry and reviewable approval record.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Allocate Electricity Costs for a Shared Research GPU</title><link>https://retrivium.ai/journal/gpu-grant-electricity-cost-center/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-grant-electricity-cost-center/</guid><description>Allocate electricity for a shared research GPU using one measurement boundary, non-overlapping project intervals and the applicable grant rules.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Build a Payment Calendar for a GPU Pilot</title><link>https://retrivium.ai/journal/gpu-funding-payment-calendar/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-funding-payment-calendar/</guid><description>Build a GPU pilot payment schedule that separates invoices, approved commitments, payment dates and available funds from work completion.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Reconcile a Hosting Invoice with GPU Telemetry</title><link>https://retrivium.ai/journal/gpu-invoice-vs-telemetry-reconciliation/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-invoice-vs-telemetry-reconciliation/</guid><description>Reconcile a GPU hosting invoice with telemetry by matching the measured object, units and time period before explaining consumption differences.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Record an Equipment Contribution to a GPU Pilot</title><link>https://retrivium.ai/journal/gpu-in-kind-contribution-register/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-in-kind-contribution-register/</guid><description>Record an equipment contribution to a GPU pilot using configuration, availability, responsibilities and acceptance evidence without inventing a valuation.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU Server Spare Parts: Build a Justified Reserve</title><link>https://retrivium.ai/journal/gpu-spare-part-reserve-table/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-spare-part-reserve-table/</guid><description>Build a GPU server spare parts reserve from compatible components, recovery procedures and lead times rather than a universal budget percentage.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Fixed and Variable GPU Costs: A Working Worksheet</title><link>https://retrivium.ai/journal/gpu-fixed-variable-cost-worksheet/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-fixed-variable-cost-worksheet/</guid><description>Separate fixed and variable GPU costs according to the period and shutdown scenario, with a worksheet that avoids counting included charges twice.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Report Unspent GPU Pilot Funding and Commitments</title><link>https://retrivium.ai/journal/gpu-funding-unused-budget-report/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-funding-unused-budget-report/</guid><description>Report GPU pilot funding by separating received funds, paid expenses, approved commitments and estimates before describing an unspent balance.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Compare Remote Hands Costs for Your GPU Server</title><link>https://retrivium.ai/journal/gpu-remote-hands-callout-cost/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-remote-hands-callout-cost/</guid><description>Compare GPU remote hands quotes by task, minimum billing unit, urgency, materials, site access and evidence of restored service.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Close a GPU Pilot with a Data Cleanup Record</title><link>https://retrivium.ai/journal/gpu-disk-cleanup-evidence/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-disk-cleanup-evidence/</guid><description>Close a GPU pilot with an agreed data inventory, cleanup evidence, separate access withdrawal and clear limits on what was verified.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Keep a Network Outage Log for a GPU Node</title><link>https://retrivium.ai/journal/gpu-owner-network-outage-log/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-owner-network-outage-log/</guid><description>Keep a GPU network outage timeline with observation points, UTC timestamps, connection recovery and separate application readiness evidence.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A Change Register for GPU Drivers and Server Settings</title><link>https://retrivium.ai/journal/gpu-maintenance-change-register/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-maintenance-change-register/</guid><description>Track GPU server changes with a baseline, reason, approval, exact versions, verification result and a documented recovery path.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Allocate Shared Host Costs Between Two GPUs</title><link>https://retrivium.ai/journal/gpu-two-card-cost-allocation/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-two-card-cost-allocation/</guid><description>Allocate shared host costs between two GPUs using direct attribution first and one consistent rule for the remaining common expenses.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Check Which GPU Expenses Cloud Credits Cover</title><link>https://retrivium.ai/journal/gpu-credit-service-eligibility-map/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-credit-service-eligibility-map/</guid><description>Map GPU cloud credit coverage by eligible product, account, status and expiry, keeping uncovered costs and transfer restrictions visible.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Track Vendor Quote Validity in a GPU Purchase Budget</title><link>https://retrivium.ai/journal/gpu-funding-quote-validity-register/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-funding-quote-validity-register/</guid><description>Track GPU vendor quotes by version, expiry, configuration, currency and delivery scope so a purchase budget retains a verifiable basis.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RTX 3090 vs RTX 4090 for LLMs: Compare the Same Workload</title><link>https://retrivium.ai/journal/rtx-3090-vs-4090-llm/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-3090-vs-4090-llm/</guid><description>Compare RTX 3090 and RTX 4090 LLM workloads with the same 24GB memory boundary, model artifact, context, quality checks and host conditions.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RTX 4090 vs RTX 5090 for LLMs: Compare 24GB and 32GB</title><link>https://retrivium.ai/journal/rtx-4090-vs-5090-llm/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-4090-vs-5090-llm/</guid><description>Compare RTX 4090 24GB and RTX 5090 32GB for one LLM task, checking architecture support, full memory use and the measured reason to upgrade.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RTX 4090 48GB: Distinguish Official Hardware from Modifications</title><link>https://retrivium.ai/journal/rtx-4090-48gb-modification/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-4090-48gb-modification/</guid><description>Check an RTX 4090 48GB listing against official hardware, device count, reported memory, modification history and a separate workload acceptance test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RTX 4090 Laptop vs Desktop for Local LLMs</title><link>https://retrivium.ai/journal/rtx-4090-laptop-vs-desktop/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-4090-laptop-vs-desktop/</guid><description>Distinguish RTX 4090 Laptop 16GB from desktop RTX 4090 24GB for LLMs, including memory, sustained operation and an owner-first schedule.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Choose a Local LLM for an RTX 3090 24GB</title><link>https://retrivium.ai/journal/rtx-3090-24gb-model-selection/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-3090-24gb-model-selection/</guid><description>Select a local LLM for RTX 3090 24GB by fixing the artifact, measuring memory and checking quality before expanding context or concurrency.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RTX 5090 LLM Tokens per Second: Define the Benchmark</title><link>https://retrivium.ai/journal/rtx-5090-tokens-per-second/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-5090-tokens-per-second/</guid><description>Interpret RTX 5090 LLM token rates by model, numerical format, request lengths, concurrency, first-token delay and successful output.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Coding LLMs on 8GB VRAM: Start with a Bounded Task</title><link>https://retrivium.ai/journal/coding-llm-8gb-vram/</link><guid isPermaLink="true">https://retrivium.ai/journal/coding-llm-8gb-vram/</guid><description>Test coding LLMs on 8GB VRAM with a small artifact, bounded context and executable checks instead of assuming a complete repository assistant.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Coding LLMs on 12GB VRAM: Budget Context and Headroom</title><link>https://retrivium.ai/journal/coding-llm-12gb-vram/</link><guid isPermaLink="true">https://retrivium.ai/journal/coding-llm-12gb-vram/</guid><description>Plan coding LLMs on 12GB VRAM using exact artifacts, compatible quantisation, code tests and separate input, output and concurrency limits.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Local LLMs on 16GB VRAM: Narrow the Model Choice</title><link>https://retrivium.ai/journal/local-llm-16gb-vram/</link><guid isPermaLink="true">https://retrivium.ai/journal/local-llm-16gb-vram/</guid><description>Narrow a local LLM shortlist for 16GB VRAM by exact model, numerical format, useful context, quality and the level of validation completed.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Local LLMs on 24GB VRAM: Test More Than the Weights</title><link>https://retrivium.ai/journal/local-llm-24gb-vram/</link><guid isPermaLink="true">https://retrivium.ai/journal/local-llm-24gb-vram/</guid><description>Assess local LLMs on 24GB VRAM using exact 14B or 32B artifacts, weight estimates, context tests, concurrency and reproducible free-memory conditions.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>48GB VRAM for LLMs: One GPU and Multiple GPUs Differ</title><link>https://retrivium.ai/journal/llm-models-48gb-vram/</link><guid isPermaLink="true">https://retrivium.ai/journal/llm-models-48gb-vram/</guid><description>Interpret 48GB VRAM for LLMs by separating one large GPU, two 24GB devices, replicas and supported distributed model execution.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How Much VRAM Does a 70B Model Need?</title><link>https://retrivium.ai/journal/llm-70b-vram-calculation/</link><guid isPermaLink="true">https://retrivium.ai/journal/llm-70b-vram-calculation/</guid><description>Estimate 70B LLM weight memory at 16, 8 and 4 bits, then add quantisation overhead, KV cache and the requirements of multi-GPU placement.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Calculate Weight Memory for an 8B Model</title><link>https://retrivium.ai/journal/llm-8b-weight-memory/</link><guid isPermaLink="true">https://retrivium.ai/journal/llm-8b-weight-memory/</guid><description>Calculate an 8B model weight estimate in decimal GB, distinguish actual tensor formats and reserve memory for the complete inference workload.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A 14B Model on 16GB VRAM: Understand the Bit Estimate</title><link>https://retrivium.ai/journal/llm-14b-16gb-memory/</link><guid isPermaLink="true">https://retrivium.ai/journal/llm-14b-16gb-memory/</guid><description>Assess a 14B model on 16GB VRAM with explicit weight arithmetic, supported quantisation, request headroom and a smaller-model quality comparison.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A 32B Model on 24GB VRAM: Why the Formula Is Not Enough</title><link>https://retrivium.ai/journal/llm-32b-24gb-memory/</link><guid isPermaLink="true">https://retrivium.ai/journal/llm-32b-24gb-memory/</guid><description>Evaluate a 32B model on 24GB VRAM by separating ideal weight size, quantised artifact support and the memory needed for requests.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3-8B VRAM: Thinking Mode and a First Local Test</title><link>https://retrivium.ai/journal/qwen3-8b-vram-requirements/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen3-8b-vram-requirements/</guid><description>Test Qwen3-8B VRAM with an exact artifact, supported runtime, explicit thinking mode and separate context, output and concurrency experiments.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3-Coder VRAM: Check the Exact Model Variant</title><link>https://retrivium.ai/journal/qwen3-coder-vram-requirements/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen3-coder-vram-requirements/</guid><description>Read Qwen3-Coder VRAM requirements from the exact model variant, total MoE weights, supported runtime and a narrow code-quality test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen3-VL VRAM: Test Images of Different Complexity</title><link>https://retrivium.ai/journal/qwen3-vl-vram-requirements/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen3-vl-vram-requirements/</guid><description>Assess Qwen3-VL VRAM using exact image inputs, preprocessing settings, model and runtime versions, accuracy checks and full-pipeline measurements.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>gpt-oss-20b VRAM: Read the Conditions Behind the Claim</title><link>https://retrivium.ai/journal/gpt-oss-20b-vram-setup/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpt-oss-20b-vram-setup/</guid><description>Read gpt-oss-20b VRAM claims in context: total versus active parameters, MXFP4 support, actual loading format, reasoning and request memory.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>gpt-oss-120b VRAM: Total MoE Weights and Active Parameters</title><link>https://retrivium.ai/journal/gpt-oss-120b-vram-setup/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpt-oss-120b-vram-setup/</guid><description>Plan gpt-oss-120b memory from the complete MoE artifact, MXFP4 conditions, per-device placement and a bounded reasoning workload.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DeepSeek-R1 vs Distill: Different Models, Different GPU Needs</title><link>https://retrivium.ai/journal/deepseek-r1-distill-vram/</link><guid isPermaLink="true">https://retrivium.ai/journal/deepseek-r1-distill-vram/</guid><description>Distinguish full DeepSeek-R1 from a specific Distill model before estimating VRAM, selecting weights or reporting a GPU test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DeepSeek-OCR GPU Requirements: Test Accuracy and Memory</title><link>https://retrivium.ai/journal/deepseek-ocr-gpu-requirements/</link><guid isPermaLink="true">https://retrivium.ai/journal/deepseek-ocr-gpu-requirements/</guid><description>Check DeepSeek-OCR GPU requirements with the exact model, page-processing mode, expected text, separate RAM/VRAM measurements and accuracy evidence.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Two 24GB GPUs vs One 48GB GPU for an LLM</title><link>https://retrivium.ai/journal/two-24gb-vs-one-48gb-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/two-24gb-vs-one-48gb-gpu/</guid><description>Compare two 24GB GPUs with one 48GB GPU by task, supported model partitioning, interconnects, replica capacity and complete operating behaviour.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RTX 5060 Ti 16GB vs RTX 5070 12GB for Local LLMs</title><link>https://retrivium.ai/journal/rtx-5060ti-16gb-vs-5070-12gb/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-5060ti-16gb-vs-5070-12gb/</guid><description>Compare RTX 5060 Ti 16GB and RTX 5070 12GB for a local LLM using exact variants, artifact memory, quality and measured request limits.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A100 40GB vs 80GB for LLMs: Check Memory and Form Factor</title><link>https://retrivium.ai/journal/a100-40gb-vs-80gb-llm/</link><guid isPermaLink="true">https://retrivium.ai/journal/a100-40gb-vs-80gb-llm/</guid><description>Compare A100 40GB and 80GB LLM configurations by exact form factor, server compatibility, partition profile and complete workload measurements.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>H100 PCIe vs SXM for LLMs: Compare the Whole System</title><link>https://retrivium.ai/journal/h100-pcie-vs-sxm-llm/</link><guid isPermaLink="true">https://retrivium.ai/journal/h100-pcie-vs-sxm-llm/</guid><description>Compare H100 PCIe and SXM using exact SKUs, supported server platforms, real interconnects and a common LLM workload without conflating H100 NVL.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CUDA Out of Memory While Loading a Model: A Check Order</title><link>https://retrivium.ai/journal/cuda-oom-model-loading/</link><guid isPermaLink="true">https://retrivium.ai/journal/cuda-oom-model-loading/</guid><description>Diagnose CUDA OOM during model loading by the last successful stage, weight format, other processes, temporary peaks and runtime-specific allocation.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CUDA Out of Memory on Long Prompts: Check the Context</title><link>https://retrivium.ai/journal/cuda-oom-long-context/</link><guid isPermaLink="true">https://retrivium.ai/journal/cuda-oom-long-context/</guid><description>Investigate CUDA OOM on long prompts using tokenised input, output allowance, KV cache, prefill buffers and a controlled context-growth test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CUDA Out of Memory with Concurrent Requests</title><link>https://retrivium.ai/journal/cuda-oom-concurrent-requests/</link><guid isPermaLink="true">https://retrivium.ai/journal/cuda-oom-concurrent-requests/</guid><description>Diagnose CUDA OOM under concurrent LLM requests by separating clients, queued work and active sequences, then measuring a controlled load progression.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CUDA OOM Allocated vs Reserved: Read the Evidence</title><link>https://retrivium.ai/journal/cuda-oom-reserved-vs-allocated/</link><guid isPermaLink="true">https://retrivium.ai/journal/cuda-oom-reserved-vs-allocated/</guid><description>Interpret allocated and reserved CUDA memory without adding overlapping figures, and distinguish live tensors, allocator cache and evidence of fragmentation.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>First Verifiable vLLM Launch in Docker on NVIDIA GPUs</title><link>https://retrivium.ai/journal/vllm-docker-first-launch/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-docker-first-launch/</guid><description>Make a first local vLLM Docker launch verifiable by checking GPU access, model readiness, API identity and persistent weight storage.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Install vLLM: Check GPU, Driver and Package Compatibility</title><link>https://retrivium.ai/journal/vllm-install-compatibility/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-install-compatibility/</guid><description>Install vLLM through a documented route after checking GPU, OS, driver, Python, package backend and model compatibility as separate layers.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM on Windows: WSL and the Linux Environment</title><link>https://retrivium.ai/journal/vllm-windows-wsl/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-windows-wsl/</guid><description>Run vLLM from Windows through a supported Linux environment such as compatible WSL, checking GPU access, files and local API boundaries in order.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM served-model-name: Fix a Missing API Model</title><link>https://retrivium.ai/journal/vllm-served-model-name/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-served-model-name/</guid><description>Resolve a vLLM model-not-found response by matching served-model-name, the /v1/models result and the client request independently of checkpoint loading.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM max-model-len: Set a Meaningful Context Limit</title><link>https://retrivium.ai/journal/vllm-max-model-len/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-max-model-len/</guid><description>Choose vLLM max-model-len from tokenised input, output allowance, model support and available memory rather than the largest advertised context window.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What vLLM gpu-memory-utilization Actually Limits</title><link>https://retrivium.ai/journal/vllm-gpu-memory-utilization/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-gpu-memory-utilization/</guid><description>Understand vLLM gpu-memory-utilization as an engine memory budget, with explicit headroom and tests for competing processes, cache and workload changes.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM tensor-parallel-size: When One Model Needs Multiple GPUs</title><link>https://retrivium.ai/journal/vllm-tensor-parallel-size/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-tensor-parallel-size/</guid><description>Use vLLM tensor-parallel-size for a supported single-model distribution, distinguishing topology and communication from independent replicas.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM Quantization: Match the Weights, Format and GPU</title><link>https://retrivium.ai/journal/vllm-quantization-launch/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-quantization-launch/</guid><description>Launch quantised weights in vLLM by matching checkpoint, method, GPU support and runtime, then measuring full memory use and task quality.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM and GGUF: Check Compatibility Before Moving a Model</title><link>https://retrivium.ai/journal/vllm-gguf-compatibility/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-gguf-compatibility/</guid><description>Move a GGUF model from llama.cpp to vLLM only after checking experimental plugin support, exact quantisation, tokenizer and equivalent control requests.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM bench serve: Read a Serving Benchmark Result</title><link>https://retrivium.ai/journal/vllm-bench-serve-command/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-bench-serve-command/</guid><description>Run and interpret vLLM bench serve with a verified endpoint, explicit input/output lengths, request rate, warm-up state and useful latency measures.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM is running but not ready: health checks and the first request</title><link>https://retrivium.ai/journal/vllm-health-ready/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-health-ready/</guid><description>Check vLLM readiness in stages: process status, HTTP health, advertised model names and a small generation request after a clean restart.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM KV cache preemption: why requests are recomputed</title><link>https://retrivium.ai/journal/vllm-kv-cache-preemption/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-kv-cache-preemption/</guid><description>Understand vLLM KV cache preemption, distinguish it from OOM and compare concurrency settings using completed requests and end-to-end latency.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Testing streaming responses from the vLLM API</title><link>https://retrivium.ai/journal/vllm-openai-streaming-test/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-openai-streaming-test/</guid><description>Verify vLLM streaming with an unbuffered client, distinguish events from visible tokens and identify proxy buffering before changing GPU settings.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM is unreachable: localhost, containers and published ports</title><link>https://retrivium.ai/journal/vllm-localhost-container-port/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-localhost-container-port/</guid><description>Diagnose unreachable vLLM endpoints by separating process readiness, container networking, bind addresses and the two sides of a published port.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM or Ollama: choose a serving workflow</title><link>https://retrivium.ai/journal/vllm-vs-ollama-serving/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-vs-ollama-serving/</guid><description>Compare vLLM and Ollama by operating workflow, model artifacts, memory, concurrency and cold versus repeated requests without unsupported speed rankings.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM or llama.cpp: serving workloads and GGUF workflows</title><link>https://retrivium.ai/journal/vllm-vs-llama-cpp/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-vs-llama-cpp/</guid><description>Compare vLLM and llama.cpp by model format, partial GPU offloading, serving controls and matched outputs instead of unsupported speed claims.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Ollama is not using the GPU: five separate checks</title><link>https://retrivium.ai/journal/ollama-does-not-use-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/ollama-does-not-use-gpu/</guid><description>Diagnose Ollama CPU-only execution by checking exact GPU support, drivers, process visibility, device selection and memory placement with logs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Ollama on Windows: verify GPU support and workload placement</title><link>https://retrivium.ai/journal/ollama-windows-gpu-check/</link><guid isPermaLink="true">https://retrivium.ai/journal/ollama-windows-gpu-check/</guid><description>Verify native Ollama on Windows using the exact GPU, background process, logs, ollama ps and a repeatable test after restarting the application.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Ollama on AMD: check your exact GPU and backend</title><link>https://retrivium.ai/journal/ollama-amd-gpu-check/</link><guid isPermaLink="true">https://retrivium.ai/journal/ollama-amd-gpu-check/</guid><description>Check Ollama support for an exact AMD GPU, operating system and backend, then verify placement and memory without universal Radeon support claims.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Ollama context length: set and verify the actual window</title><link>https://retrivium.ai/journal/ollama-context-length-setting/</link><guid isPermaLink="true">https://retrivium.ai/journal/ollama-context-length-setting/</guid><description>Set Ollama context length explicitly, inspect effective placement and compare memory and latency at three useful context levels before increasing concurrency.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Running two Ollama models at once: memory and concurrency</title><link>https://retrivium.ai/journal/ollama-two-models-parallel/</link><guid isPermaLink="true">https://retrivium.ai/journal/ollama-two-models-parallel/</guid><description>Test two Ollama models together by separating loaded-model limits from request concurrency, then checking memory, retention and the actual queue.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Ollama CPU and GPU split: interpreting mixed placement</title><link>https://retrivium.ai/journal/ollama-cpu-gpu-split/</link><guid isPermaLink="true">https://retrivium.ai/journal/ollama-cpu-gpu-split/</guid><description>Interpret Ollama CPU/GPU placement, distinguish usable capacity from speed and test whether a mixed configuration meets the task’s latency needs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Ollama keep_alive: retain or unload a model deliberately</title><link>https://retrivium.ai/journal/ollama-keep-alive-unload/</link><guid isPermaLink="true">https://retrivium.ai/journal/ollama-keep-alive-unload/</guid><description>Use Ollama keep_alive deliberately: compare cold and warm requests, inspect model retention, test unloading and document idle intervals.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Choosing a GGUF file for llama.cpp</title><link>https://retrivium.ai/journal/llama-cpp-gguf-selection/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-cpp-gguf-selection/</guid><description>Choose an exact GGUF artifact for llama.cpp using provenance, quantization, runtime memory, tokenizer and chat-template checks on a small task set.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>llama.cpp server: a local API from a GGUF model</title><link>https://retrivium.ai/journal/llama-cpp-server-launch/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-cpp-server-launch/</guid><description>Start llama-server with a compatible GGUF, verify the local API and model identifier, then confirm backend placement and a repeatable clean launch.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>llama.cpp GPU layers: verify partial model offloading</title><link>https://retrivium.ai/journal/llama-cpp-gpu-layers/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-cpp-gpu-layers/</guid><description>Adjust llama.cpp GPU layers in a supported build, inspect real offloading and compare memory and latency without assuming layers occupy equal shares.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Building llama.cpp on Windows with the right backend</title><link>https://retrivium.ai/journal/llama-cpp-windows-build/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-cpp-windows-build/</guid><description>Build or select llama.cpp on Windows with the intended backend, verify the actual executable and separate GPU discovery from model offloading.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SGLang in Docker: launch and verify your first model</title><link>https://retrivium.ai/journal/sglang-docker-launch/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-docker-launch/</guid><description>Launch SGLang in Docker on a compatible NVIDIA environment, retain model files and verify readiness, model identity and a repeated clean start.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SGLang or vLLM: compare engines on the same workload</title><link>https://retrivium.ai/journal/sglang-vs-vllm-serving/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-vs-vllm-serving/</guid><description>Compare SGLang and vLLM on matched checkpoints, quality examples, cache conditions and request rates, including startup and recovery behaviour.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SGLang memory fraction: diagnose GPU memory pressure</title><link>https://retrivium.ai/journal/sglang-memory-fraction/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-memory-fraction/</guid><description>Diagnose SGLang memory pressure using mem-fraction-static, prefill and decode stages, cache capacity and small controlled configuration changes.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Runpod persistent storage: keep files after deleting a Pod</title><link>https://retrivium.ai/journal/runpod-network-volume-persistence/</link><guid isPermaLink="true">https://retrivium.ai/journal/runpod-network-volume-persistence/</guid><description>Keep Runpod files after Pod deletion by choosing an independent network volume, checking /workspace and testing recovery from a new environment.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Runpod storage types: container disk, volume disk and network volume</title><link>https://retrivium.ai/journal/runpod-container-volume-network-disk/</link><guid isPermaLink="true">https://retrivium.ai/journal/runpod-container-volume-network-disk/</guid><description>Compare Runpod container disks, volume disks and network volumes by Stop, Terminate, mount location and the data that each resource should hold.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Runpod storage pricing: what remains billable after Stop</title><link>https://retrivium.ai/journal/runpod-storage-billing-after-stop/</link><guid isPermaLink="true">https://retrivium.ai/journal/runpod-storage-billing-after-stop/</guid><description>Understand Runpod charges after Stop by separating GPU compute from retained disks, independent volumes and the full period between working sessions.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Runpod SSH keys: prepare credentials and choose a connection</title><link>https://retrivium.ai/journal/runpod-ssh-public-key-setup/</link><guid isPermaLink="true">https://retrivium.ai/journal/runpod-ssh-public-key-setup/</guid><description>Prepare a Runpod SSH public key, use the current Connect command and distinguish basic proxied access from full TCP SSH with SCP or SFTP.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Runpod SSH not working: diagnose one connection layer at a time</title><link>https://retrivium.ai/journal/runpod-ssh-connection-debug/</link><guid isPermaLink="true">https://retrivium.ai/journal/runpod-ssh-connection-debug/</guid><description>Diagnose Runpod SSH failures by checking current Pod state, transport mode, mapped ports, sshd and public-key authentication in a clear order.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Runpod SSH port forwarding for a private local service</title><link>https://retrivium.ai/journal/runpod-private-port-forward/</link><guid isPermaLink="true">https://retrivium.ai/journal/runpod-private-port-forward/</guid><description>Forward a local Runpod service through full SSH by separating the external SSH port, internal application port and loopback port on your computer.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Jupyter on Runpod: where to save notebooks and results</title><link>https://retrivium.ai/journal/runpod-jupyter-files-persistence/</link><guid isPermaLink="true">https://retrivium.ai/journal/runpod-jupyter-files-persistence/</guid><description>Save Runpod Jupyter notebooks and outputs on the intended disk, distinguish kernel memory from files and verify an exported project in a clean session.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Expose a Pod HTTP service through Runpod Proxy</title><link>https://retrivium.ai/journal/runpod-http-port-proxy/</link><guid isPermaLink="true">https://retrivium.ai/journal/runpod-http-port-proxy/</guid><description>Publish a Runpod HTTP application using its internal port, a reachable bind address and the correct proxy URL, then verify route and authentication separately.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Runpod Community and Secure Cloud: storage and access boundaries</title><link>https://retrivium.ai/journal/runpod-community-vs-secure-boundaries/</link><guid isPermaLink="true">https://retrivium.ai/journal/runpod-community-vs-secure-boundaries/</guid><description>Compare Runpod Community and Secure Cloud using documented placement, network-volume support and the access requirements of a specific GPU project.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>What to save before terminating a Runpod Pod</title><link>https://retrivium.ai/journal/runpod-terminate-pod-backup/</link><guid isPermaLink="true">https://retrivium.ai/journal/runpod-terminate-pod-backup/</guid><description>Prepare for Runpod Terminate by inventorying results, exporting a secret-free environment recipe, checking recovery and deciding separately on network volumes.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vast.ai Stop and Destroy: instance and data lifecycles</title><link>https://retrivium.ai/journal/vast-ai-instance-lifecycle-stop-destroy/</link><guid isPermaLink="true">https://retrivium.ai/journal/vast-ai-instance-lifecycle-stop-destroy/</guid><description>Understand Vast.ai Stop, Restart and Destroy, including retained files, storage billing, GPU availability and a verified export before deletion.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Reading Vast.ai storage and bandwidth charges</title><link>https://retrivium.ai/journal/vast-ai-storage-network-charges/</link><guid isPermaLink="true">https://retrivium.ai/journal/vast-ai-storage-network-charges/</guid><description>Estimate the full Vast.ai offer using GPU time, allocated storage, transfer directions, paused retention and the cost of moving results.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Reading Vast.ai host metrics before renting a GPU</title><link>https://retrivium.ai/journal/vast-ai-host-score-fields/</link><guid isPermaLink="true">https://retrivium.ai/journal/vast-ai-host-score-fields/</guid><description>Read Vast.ai reliability, verification tier, maximum rental duration and allocated resources, then validate the full workflow with a small test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vast.ai SSH and Jupyter: choose the right access template</title><link>https://retrivium.ai/journal/vast-ai-ssh-jupyter-ports/</link><guid isPermaLink="true">https://retrivium.ai/journal/vast-ai-ssh-jupyter-ports/</guid><description>Choose Vast.ai SSH, Jupyter or Entrypoint launch modes, find current mapped ports and verify access before configuring notebooks or development tools.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vast.ai on-demand, reserved and interruptible instances</title><link>https://retrivium.ai/journal/vast-ai-reserved-interruptible-choice/</link><guid isPermaLink="true">https://retrivium.ai/journal/vast-ai-reserved-interruptible-choice/</guid><description>Compare Vast.ai rental types using priority, prepayment, instance-bound credits and restartable work rather than headline rate differences alone.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Moving data between Vast.ai instances</title><link>https://retrivium.ai/journal/vast-ai-copy-data-between-instances/</link><guid isPermaLink="true">https://retrivium.ai/journal/vast-ai-copy-data-between-instances/</guid><description>Move Vast.ai data using supported transfer paths, preserve the environment recipe and verify files, permissions and a control run before deleting the source.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Vast.ai templates: ports, environment variables and repeatable launches</title><link>https://retrivium.ai/journal/vast-ai-template-environment-variables/</link><guid isPermaLink="true">https://retrivium.ai/journal/vast-ai-template-environment-variables/</guid><description>Create a repeatable Vast.ai template with a fixed image, launch mode, startup logs, ports and explicit configuration while keeping secrets out of the recipe.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Hetzner GPU VPS searches and dedicated GEX servers</title><link>https://retrivium.ai/journal/hetzner-gpu-vps-vs-gex/</link><guid isPermaLink="true">https://retrivium.ai/journal/hetzner-gpu-vps-vs-gex/</guid><description>Distinguish Hetzner GPU VPS searches from dedicated GEX root servers, including resource format, administration, scaling expectations and the first pilot.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Recovering SSH access to a Hetzner GPU server with Rescue</title><link>https://retrivium.ai/journal/hetzner-gex-root-rescue-access/</link><guid isPermaLink="true">https://retrivium.ai/journal/hetzner-gex-root-rescue-access/</guid><description>Recover a Hetzner dedicated GPU server through Robot and Rescue System by separating panel access, OS diagnosis and a minimal reversible repair.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Hetzner GPU pricing: include setup fees in a short pilot</title><link>https://retrivium.ai/journal/hetzner-gpu-install-fee-short-rental/</link><guid isPermaLink="true">https://retrivium.ai/journal/hetzner-gpu-install-fee-short-rental/</guid><description>Include Hetzner GPU setup fees in a short pilot using a complete-period formula, an explicitly hypothetical example and a clear working calendar.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Hetzner GPU server auction: verify the actual listing</title><link>https://retrivium.ai/journal/hetzner-gpu-server-auction-status/</link><guid isPermaLink="true">https://retrivium.ai/journal/hetzner-gpu-server-auction-status/</guid><description>Check a Hetzner Server Auction listing for an explicitly specified GPU, distinguish it from GEX and verify the full resource before ordering.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Hourly or monthly GPU rental: compare the full working period</title><link>https://retrivium.ai/journal/cloud-gpu-hourly-monthly-break-even/</link><guid isPermaLink="true">https://retrivium.ai/journal/cloud-gpu-hourly-monthly-break-even/</guid><description>Compare hourly and monthly GPU rental with matched workloads, complete storage periods, setup costs and a clearly hypothetical break-even calculation.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Runpod pricing calculator: build a useful input worksheet</title><link>https://retrivium.ai/journal/cloud-gpu-budget-calculator-worksheet/</link><guid isPermaLink="true">https://retrivium.ai/journal/cloud-gpu-budget-calculator-worksheet/</guid><description>Prepare a Runpod cost worksheet with billable Pod time, disk type and capacity, retained-data lifetime, transfer and measured preparation assumptions.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Google Cloud GPU quota: checks before requesting an increase</title><link>https://retrivium.ai/journal/google-cloud-gpu-quota-request/</link><guid isPermaLink="true">https://retrivium.ai/journal/google-cloud-gpu-quota-request/</guid><description>Prepare a Google Cloud GPU quota request by checking global and regional model limits, provisioning mode, existing usage and the exact configuration.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Google Cloud GPU capacity errors despite available quota</title><link>https://retrivium.ai/journal/google-cloud-gpu-zone-resource-pool-exhausted/</link><guid isPermaLink="true">https://retrivium.ai/journal/google-cloud-gpu-zone-resource-pool-exhausted/</guid><description>Diagnose Google Cloud GPU resource-pool errors with sufficient quota by separating supported configurations, regional permission and physical zone capacity.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AWS GPU quotas: instance families and regional vCPU limits</title><link>https://retrivium.ai/journal/aws-gpu-vcpu-quota-workflow/</link><guid isPermaLink="true">https://retrivium.ai/journal/aws-gpu-vcpu-quota-workflow/</guid><description>Check AWS GPU vCPU quotas by region, P or G and VT family, purchase option and existing usage before submitting a Service Quotas increase.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU EC2 terminated: check the EBS volumes left behind</title><link>https://retrivium.ai/journal/aws-gpu-ebs-after-termination/</link><guid isPermaLink="true">https://retrivium.ai/journal/aws-gpu-ebs-after-termination/</guid><description>Find EBS resources left after GPU EC2 termination by checking DeleteOnTermination, volume IDs, snapshots, regions and a verified restoration route.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Preparing a GPU workload for AWS Spot interruptions</title><link>https://retrivium.ai/journal/aws-spot-checkpoint-resume-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/aws-spot-checkpoint-resume-gpu/</guid><description>Prepare AWS Spot GPU work with regular checkpoints, interruption handling, independent storage and a verified restart that handles incomplete outputs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Azure GPU quota: regional totals and VM family limits</title><link>https://retrivium.ai/journal/azure-gpu-regional-family-quotas/</link><guid isPermaLink="true">https://retrivium.ai/journal/azure-gpu-regional-family-quotas/</guid><description>Check Azure GPU deployment permission through Total Regional vCPUs, the selected VM-family quota and current subscription usage before diagnosing capacity.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Azure GPU VM Stopped or Deallocated: which costs remain</title><link>https://retrivium.ai/journal/azure-gpu-deallocated-cost-components/</link><guid isPermaLink="true">https://retrivium.ai/journal/azure-gpu-deallocated-cost-components/</guid><description>Distinguish Azure GPU VM Stopped from Deallocated, verify the actual power state and audit managed disks and networking after compute is released.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Starting a GPU project on Selectel: resource and access options</title><link>https://retrivium.ai/journal/selectel-gpu-server-access-options/</link><guid isPermaLink="true">https://retrivium.ai/journal/selectel-gpu-server-access-options/</guid><description>Start a Selectel GPU project by verifying the cloud configuration, dedicated PCI device, storage, Data Science image and an initial access test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>JupyterLab on Selectel GPU: access and saved notebooks</title><link>https://retrivium.ai/journal/selectel-gpu-jupyter-notebook-access/</link><guid isPermaLink="true">https://retrivium.ai/journal/selectel-gpu-jupyter-notebook-access/</guid><description>Use Selectel’s Data Science GPU image for JupyterLab, verify the documented network path and save a notebook that works from a clean kernel.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Configuring a Yandex Cloud GPU VM</title><link>https://retrivium.ai/journal/yandex-gpu-platform-configuration/</link><guid isPermaLink="true">https://retrivium.ai/journal/yandex-gpu-platform-configuration/</guid><description>Configure a Yandex Cloud GPU VM using the supported platform, GPU count, paired CPU and RAM, compatible image and current quota scope.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Yandex Cloud GPU clusters: when InfiniBand matters</title><link>https://retrivium.ai/journal/yandex-gpu-cluster-connectivity/</link><guid isPermaLink="true">https://retrivium.ai/journal/yandex-gpu-cluster-connectivity/</guid><description>Choose a Yandex Cloud GPU cluster only for a suitable distributed workload, checking InfiniBand, supported eight-GPU nodes, zone and cluster permission.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Preparing a Yandex Cloud GPU quota request</title><link>https://retrivium.ai/journal/yandex-gpu-quota-approval/</link><guid isPermaLink="true">https://retrivium.ai/journal/yandex-gpu-quota-approval/</guid><description>Prepare a Yandex Cloud GPU quota request with exact platform, zone, parallel VM count, current usage and the October 2026 quota-scope changes.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Yandex Cloud preemptible GPU VMs: disks and restart plans</title><link>https://retrivium.ai/journal/yandex-preemptible-gpu-disk-snapshot/</link><guid isPermaLink="true">https://retrivium.ai/journal/yandex-preemptible-gpu-disk-snapshot/</guid><description>Prepare a Yandex Cloud preemptible GPU VM with regular application progress, persistent files, deliberate snapshots and a tested restart from saved state.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Deploying a GPU VM on Cloud.ru Evolution</title><link>https://retrivium.ai/journal/cloud-ru-evolution-gpu-deployment/</link><guid isPermaLink="true">https://retrivium.ai/journal/cloud-ru-evolution-gpu-deployment/</guid><description>Deploy a Cloud.ru Evolution GPU VM by matching platform, GPU flavour, image, zone, network and SSH keys, then testing a small reproducible workload.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Cloud.ru Advanced or Evolution GPU: compare the actual platforms</title><link>https://retrivium.ai/journal/cloud-ru-advanced-vs-evolution-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/cloud-ru-advanced-vs-evolution-gpu/</guid><description>Compare Cloud.ru Advanced ECS with GPU and Evolution GPU VMs as separate platforms, including tools, dependencies, configurations and migration work.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SberCloud GPU and Cloud.ru: updating older instructions</title><link>https://retrivium.ai/journal/sbercloud-cloud-ru-gpu-name-change/</link><guid isPermaLink="true">https://retrivium.ai/journal/sbercloud-cloud-ru-gpu-name-change/</guid><description>Update older SberCloud GPU tutorials by identifying the current Cloud.ru platform, product, API, image and ordering terms before repeating technical steps.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>VK Cloud GPU: full devices, vGPU profiles and first checks</title><link>https://retrivium.ai/journal/vk-cloud-gpu-instance-options/</link><guid isPermaLink="true">https://retrivium.ai/journal/vk-cloud-gpu-instance-options/</guid><description>Choose VK Cloud GPU resources by distinguishing full devices from vGPU profiles, available VRAM, operating-system preparation and licensing requirements.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Timeweb Cloud GPU: checks before your first deployment</title><link>https://retrivium.ai/journal/timeweb-gpu-server-first-setup/</link><guid isPermaLink="true">https://retrivium.ai/journal/timeweb-gpu-server-first-setup/</guid><description>Check Timeweb Cloud GPU format, availability, creation workflow, billing-period wording and supported cloning before a first workload is deployed.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Servercore GPU: server format, location and billing checks</title><link>https://retrivium.ai/journal/servercore-gpu-server-options/</link><guid isPermaLink="true">https://retrivium.ai/journal/servercore-gpu-server-options/</guid><description>Evaluate Servercore GPU placement in Central Asia, the full server configuration and the difference between shutdown, pause and freeze in billing rules.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Accessing Jupyter on a cloud GPU through an SSH tunnel</title><link>https://retrivium.ai/journal/cloud-gpu-jupyter-ssh-tunnel/</link><guid isPermaLink="true">https://retrivium.ai/journal/cloud-gpu-jupyter-ssh-tunnel/</guid><description>Access Jupyter on a cloud GPU through a loopback SSH tunnel while preserving notebook authentication and distinguishing local from remote ports.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Runpod S3 storage: a network-volume API, with specific limits</title><link>https://retrivium.ai/journal/gpu-cloud-s3-model-cache-storage/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-cloud-s3-model-cache-storage/</guid><description>Use Runpod’s S3-compatible API for network-volume files, with the correct data-centre endpoint and explicit checks for unsupported Amazon S3 features.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU powered off, public IP retained: audit the network resource</title><link>https://retrivium.ai/journal/cloud-public-ip-lifetime-billing/</link><guid isPermaLink="true">https://retrivium.ai/journal/cloud-public-ip-lifetime-billing/</guid><description>Audit public IP resources after a GPU VM stops or is deleted, including AWS Elastic IP, Azure Public IP, DNS dependencies and remaining charges.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Resizing a cloud GPU VM without losing data</title><link>https://retrivium.ai/journal/cloud-gpu-resize-data-preservation/</link><guid isPermaLink="true">https://retrivium.ai/journal/cloud-gpu-resize-data-preservation/</guid><description>A practical GPU VM resize checklist covering supported changes, persistent data, a replacement instance, validation and a clear rollback point.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Moving a GPU VM to another region: what must move separately</title><link>https://retrivium.ai/journal/cloud-gpu-region-migration-plan/</link><guid isPermaLink="true">https://retrivium.ai/journal/cloud-gpu-region-migration-plan/</guid><description>Plan a GPU VM region migration across compute, images, disks, quotas, network dependencies and access, with a tested cutover and rollback.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Ephemeral and persistent disks on GPU VMs: a deletion checklist</title><link>https://retrivium.ai/journal/cloud-gpu-ephemeral-vs-persistent-checklist/</link><guid isPermaLink="true">https://retrivium.ai/journal/cloud-gpu-ephemeral-vs-persistent-checklist/</guid><description>Understand GPU VM disk lifecycles before stopping or deleting an instance: ephemeral storage, persistent volumes, backups and a restore test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU cloud team access: API keys and SSH keys have different jobs</title><link>https://retrivium.ai/journal/cloud-gpu-account-team-key-rotation/</link><guid isPermaLink="true">https://retrivium.ai/journal/cloud-gpu-account-team-key-rotation/</guid><description>Separate cloud API credentials, SSH keys and application tokens for a GPU team, with scoped automation and a tested rotation procedure.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Ending a GPU pilot: finding resources that still incur charges</title><link>https://retrivium.ai/journal/cloud-gpu-resource-cleanup-audit/</link><guid isPermaLink="true">https://retrivium.ai/journal/cloud-gpu-resource-cleanup-audit/</guid><description>Close a GPU pilot with an inventory of instances, disks, snapshots, addresses and access, then reconcile any remaining charges.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Setting up an OpenRouter API key for an application</title><link>https://retrivium.ai/journal/openrouter-api-key-setup/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-api-key-setup/</guid><description>Prepare an OpenRouter API key with clear ownership, bounded spending, server-side storage and a small test before a larger integration.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter base URL: configuring a compatible client</title><link>https://retrivium.ai/journal/openrouter-base-url/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-base-url/</guid><description>Configure the OpenRouter base URL correctly by separating an SDK base address from a full endpoint and inspecting the final HTTP request.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Your first verifiable OpenRouter request in Python</title><link>https://retrivium.ai/journal/openrouter-python-request/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-python-request/</guid><description>Make a small OpenRouter call from Python, checking environment variables, HTTP failures, model identity and usage before adding frameworks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Calling OpenRouter from Node.js without exposing the key</title><link>https://retrivium.ai/journal/openrouter-nodejs-request/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-nodejs-request/</guid><description>Call OpenRouter from a Node.js server while keeping the API key out of browser code and checking cancellation, errors and application limits.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Reading an OpenRouter streaming response incrementally</title><link>https://retrivium.ai/journal/openrouter-streaming-client/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-streaming-client/</guid><description>Parse OpenRouter streaming responses with correct SSE boundaries, incremental UTF-8 decoding, completion handling and partial-error reporting.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Structured output through OpenRouter: when to use a JSON schema</title><link>https://retrivium.ai/journal/openrouter-json-schema/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-json-schema/</guid><description>Use OpenRouter structured outputs with a supported route, a small JSON Schema and application checks for both structure and meaning.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Tool calling through OpenRouter: the model proposes, your app executes</title><link>https://retrivium.ai/journal/openrouter-tool-calling/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-tool-calling/</guid><description>Build an OpenRouter client-tool loop with route checks, argument validation, application authorization and explicit execution limits.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter error 429: limits, queues and controlled retries</title><link>https://retrivium.ai/journal/openrouter-429-error/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-429-error/</guid><description>Diagnose OpenRouter 429 errors by identifying the limiting layer, respecting Retry-After and testing recovery with a bounded queue.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter error 403: what to check before switching models</title><link>https://retrivium.ai/journal/openrouter-403-error/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-403-error/</guid><description>Investigate OpenRouter 403 errors through safe error details, permissions, scoped budgets, policy rules and recent configuration changes.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter error 404: API address, model ID or route</title><link>https://retrivium.ai/journal/openrouter-404-error/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-404-error/</guid><description>Trace an OpenRouter 404 through the final API path, model identifier, request protocol and intermediate backend before changing infrastructure.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter error 500: building a useful failure report</title><link>https://retrivium.ai/journal/openrouter-500-error/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-500-error/</guid><description>Build a useful OpenRouter 500 error report with a minimal request, safe diagnostics, bounded retries and a compatible fallback test.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter error 401: checking credentials and the runtime</title><link>https://retrivium.ai/journal/openrouter-401-error/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-401-error/</guid><description>Resolve OpenRouter 401 errors by checking the Bearer header, the actual runtime credential, revoked access and a controlled replacement process.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter error 402: credit balance and request limits</title><link>https://retrivium.ai/journal/openrouter-402-credits/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-402-credits/</guid><description>Investigate OpenRouter 402 using credit balance, key limits, potential request cost and concurrent-work budgets before retrying or adding funds.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Free model limits on OpenRouter: planning a bounded test</title><link>https://retrivium.ai/journal/openrouter-free-model-limits/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-free-model-limits/</guid><description>Plan a bounded OpenRouter free-model test with current account limits, valid free catalog entries, a finite queue and explicit fallback costs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter free model router: checking which model answered</title><link>https://retrivium.ai/journal/openrouter-free-model-router/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-free-model-router/</guid><description>Test the OpenRouter free router while recording the model that actually answered, required features, interruptions and differences from a fixed free entry.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Free OpenRouter API keys: what is free and what costs money</title><link>https://retrivium.ai/journal/openrouter-free-api-key/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-free-api-key/</guid><description>Separate a free OpenRouter API key from free model usage, account limits and paid fallback before building a small, verifiable experiment.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter BYOK pricing: separating the parts of the bill</title><link>https://retrivium.ai/journal/openrouter-byok-pricing/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-byok-pricing/</guid><description>Build an OpenRouter BYOK estimate that separates upstream inference, allowance, gateway fees, credit purchase fees and fallback usage.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter BYOK not working: credentials, region and fallback</title><link>https://retrivium.ai/journal/openrouter-byok-not-working/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-byok-not-working/</guid><description>Debug OpenRouter BYOK by checking one provider-model pair, upstream credentials, product and region eligibility, routing and the actual fallback used.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter provider routing: the difference between only and order</title><link>https://retrivium.ai/journal/openrouter-provider-only-order/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-provider-only-order/</guid><description>Understand OpenRouter provider.only, provider.order, fallbacks and required parameters, then test the boundary with a permitted negative case.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter prompt caching: verifying savings in usage data</title><link>https://retrivium.ai/journal/openrouter-cache-cost/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-cache-cost/</guid><description>Verify OpenRouter prompt-caching savings using comparable requests, cached-input usage, actual charges and the provider route that processed them.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter usage: reconciling tokens and request cost</title><link>https://retrivium.ai/journal/openrouter-usage-accounting/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-usage-accounting/</guid><description>Reconcile OpenRouter request IDs, actual model identity, token usage, finish states and charges across streaming, retries and BYOK.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Fetching the OpenRouter model catalog before deployment</title><link>https://retrivium.ai/journal/openrouter-model-catalog-api/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-model-catalog-api/</guid><description>Fetch and version the OpenRouter model catalog so applications can verify IDs, context, parameters and route requirements before deployment.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Errors inside an OpenRouter stream: why HTTP 200 is insufficient</title><link>https://retrivium.ai/journal/openrouter-stream-errors/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-stream-errors/</guid><description>Handle OpenRouter errors after streaming starts by distinguishing HTTP success, event-level failure, partial output and a separately identified retry.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter Zero Data Retention: restricting eligible routes</title><link>https://retrivium.ai/journal/openrouter-privacy-zdr/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-privacy-zdr/</guid><description>Evaluate OpenRouter Zero Data Retention across routing, provider endpoints, application logs and tools, including the announced screening-policy update.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenRouter fallback with a price cap: limiting backup routes</title><link>https://retrivium.ai/journal/openrouter-fallback-price-cap/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-fallback-price-cap/</guid><description>Limit OpenRouter fallback with per-component price caps, compatible backup routes and separate bounds on tokens, attempts and total task spending.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Starting a LiteLLM gateway with Docker Compose</title><link>https://retrivium.ai/journal/litellm-docker-compose-start/</link><guid isPermaLink="true">https://retrivium.ai/journal/litellm-docker-compose-start/</guid><description>Prepare a LiteLLM Docker Compose pilot with explicit gateway, Postgres, secret and volume responsibilities, then test persistence and accounting.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LiteLLM virtual keys: separate access for each application</title><link>https://retrivium.ai/journal/litellm-virtual-key-scopes/</link><guid isPermaLink="true">https://retrivium.ai/journal/litellm-virtual-key-scopes/</guid><description>Give each LiteLLM application a scoped virtual key with documented models, ownership, budget rules, revocation and persistence checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LiteLLM budgets: periods, shared limits and overrun tests</title><link>https://retrivium.ai/journal/litellm-budget-reset/</link><guid isPermaLink="true">https://retrivium.ai/journal/litellm-budget-reset/</guid><description>Configure LiteLLM budgets around the right entity, database-backed accounting, reset time and a controlled test of the effective spending boundary.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LiteLLM guardrails: choosing where to inspect requests and responses</title><link>https://retrivium.ai/journal/litellm-guardrails-boundary/</link><guid isPermaLink="true">https://retrivium.ai/journal/litellm-guardrails-boundary/</guid><description>Place LiteLLM guardrails at the right request or response boundary, then test false positives, dependency failures and streaming behavior.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Preparing LiteLLM UI for model and key management</title><link>https://retrivium.ai/journal/litellm-ui-setup/</link><guid isPermaLink="true">https://retrivium.ai/journal/litellm-ui-setup/</guid><description>Prepare LiteLLM Admin UI with persistent state, managed access, one tested model, a scoped application key and a recovery procedure.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DLP at an AI gateway: reducing sensitive data exposure</title><link>https://retrivium.ai/journal/ai-gateway-dlp/</link><guid isPermaLink="true">https://retrivium.ai/journal/ai-gateway-dlp/</guid><description>Design AI gateway DLP around outgoing fields, a narrow policy, inspected upstream payloads and explicit behavior when the check fails.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A local RAG server: placing components around the GPU</title><link>https://retrivium.ai/journal/rag-server-local-architecture/</link><guid isPermaLink="true">https://retrivium.ai/journal/rag-server-local-architecture/</guid><description>Plan a local RAG server across document preparation, embeddings, vector search, reranking and generation, assigning resources to each stage.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qdrant for RAG: deciding what belongs in RAM or on disk</title><link>https://retrivium.ai/journal/qdrant-memory-on-disk/</link><guid isPermaLink="true">https://retrivium.ai/journal/qdrant-memory-on-disk/</guid><description>Estimate Qdrant memory from vectors, graph structures, payload and replicas, then test RAM and on-disk placement against retrieval quality.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>PostgreSQL and pgvector for RAG on an existing server</title><link>https://retrivium.ai/journal/pgvector-rag-server/</link><guid isPermaLink="true">https://retrivium.ai/journal/pgvector-rag-server/</guid><description>Evaluate pgvector on an existing PostgreSQL server with exact and approximate search, post-scan filtering, resource limits and application workload checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Hosting Chroma: local persistence and server mode</title><link>https://retrivium.ai/journal/chroma-rag-hosting/</link><guid isPermaLink="true">https://retrivium.ai/journal/chroma-rag-hosting/</guid><description>Choose Chroma in-memory, persistent or client-server operation, then verify embedding location, collection consistency and recovery on your server.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>FAISS server memory: an index library versus a database service</title><link>https://retrivium.ai/journal/faiss-index-memory/</link><guid isPermaLink="true">https://retrivium.ai/journal/faiss-index-memory/</guid><description>Size a FAISS index using representation, graph or partition overhead, metadata services and a retrieval-quality test on the actual corpus.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Batch text embeddings on your own GPU</title><link>https://retrivium.ai/journal/text-embeddings-batch/</link><guid isPermaLink="true">https://retrivium.ai/journal/text-embeddings-batch/</guid><description>Run resumable batch text embeddings with a fixed model, documented query and document encoding, realistic lengths and verified index quality.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Embedding dimensions: calculating index memory</title><link>https://retrivium.ai/journal/embedding-dimensions-memory/</link><guid isPermaLink="true">https://retrivium.ai/journal/embedding-dimensions-memory/</guid><description>Calculate embedding coordinate memory with N × D × B, then add index structures, payload and measured service overhead before sizing RAM.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Evaluating embeddings for Russian language retrieval</title><link>https://retrivium.ai/journal/embeddings-russian-retrieval/</link><guid isPermaLink="true">https://retrivium.ai/journal/embeddings-russian-retrieval/</guid><description>Evaluate Russian-language embeddings on your own terminology, mixed-language documents and labeled retrieval questions before comparing resource use.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Reranking in RAG: how many candidates should you rescore?</title><link>https://retrivium.ai/journal/reranker-rag-latency/</link><guid isPermaLink="true">https://retrivium.ai/journal/reranker-rag-latency/</guid><description>Choose RAG reranker candidate depth by measuring query-passage pairs, text length, batch memory, end-to-end latency and ranking quality.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>BGE rerankers on GPU: testing memory and batching</title><link>https://retrivium.ai/journal/bge-reranker-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/bge-reranker-gpu/</guid><description>Test a BGE reranker on GPU using query-document pairs of realistic lengths, incremental batches and ranking checks before sizing capacity.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Qwen rerankers: separating relevance scoring from text generation</title><link>https://retrivium.ai/journal/qwen-reranker-serving/</link><guid isPermaLink="true">https://retrivium.ai/journal/qwen-reranker-serving/</guid><description>Serve a Qwen reranker with a relevance-scoring contract, stable instructions, preserved candidate IDs and a bounded GPU workload.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Choosing GPU memory for Whisper transcription</title><link>https://retrivium.ai/journal/whisper-gpu-requirements/</link><guid isPermaLink="true">https://retrivium.ai/journal/whisper-gpu-requirements/</guid><description>Choose GPU memory for Whisper using the official approximate model guidance, representative audio, concurrency and stage-by-stage measurements.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Whisper on CPU or GPU: comparing completion time and cost</title><link>https://retrivium.ai/journal/whisper-cpu-vs-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/whisper-cpu-vs-gpu/</guid><description>Compare Whisper on CPU and GPU using identical audio, model settings, real-time factor, transcript quality and total completed-file cost.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Running Whisper in a GPU container: a preflight checklist</title><link>https://retrivium.ai/journal/whisper-gpu-container/</link><guid isPermaLink="true">https://retrivium.ai/journal/whisper-gpu-container/</guid><description>Validate a Whisper GPU container across host drivers, container access, FFmpeg decoding, model execution and persistent output directories.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Long audio with Whisper: segments, queues and durable results</title><link>https://retrivium.ai/journal/whisper-long-audio/</link><guid isPermaLink="true">https://retrivium.ai/journal/whisper-long-audio/</guid><description>Plan long-audio Whisper jobs with stable recording and segment IDs, timestamps, bounded retries and a verified durable transcript.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OCR on CPU or GPU: where acceleration changes the pipeline</title><link>https://retrivium.ai/journal/ocr-gpu-vs-cpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/ocr-gpu-vs-cpu/</guid><description>Compare OCR on CPU and GPU across page preparation, recognition, structure reconstruction and durable output using the same labeled documents.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>PaddleOCR on GPU: validating installation and document quality</title><link>https://retrivium.ai/journal/paddleocr-gpu-pilot/</link><guid isPermaLink="true">https://retrivium.ai/journal/paddleocr-gpu-pilot/</guid><description>Validate PaddleOCR GPU installation, actual backend selection and document quality before changing pipeline components or scaling the workload.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Tesseract and GPU acceleration: why installing CUDA is insufficient</title><link>https://retrivium.ai/journal/tesseract-gpu-acceleration/</link><guid isPermaLink="true">https://retrivium.ai/journal/tesseract-gpu-acceleration/</guid><description>Understand Tesseract GPU limits, experimental OpenCL support and CPU process tuning before deciding whether another OCR engine needs a GPU. </description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A GPU OCR pipeline for a 1,000-page PDF workload</title><link>https://retrivium.ai/journal/pdf-ocr-gpu-pipeline/</link><guid isPermaLink="true">https://retrivium.ai/journal/pdf-ocr-gpu-pipeline/</guid><description>Estimate a 1,000-page PDF OCR job from representative page classes, complete pipeline timings, quality checks and explicit retry overhead.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>ComfyUI GPU requirements depend on the entire workflow</title><link>https://retrivium.ai/journal/comfyui-gpu-requirements/</link><guid isPermaLink="true">https://retrivium.ai/journal/comfyui-gpu-requirements/</guid><description>Choose a GPU for ComfyUI using the complete workflow, model and node versions, resolution, batch and memory peaks across generation and decoding.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>ComfyUI offloading: when moving data to RAM helps</title><link>https://retrivium.ai/journal/comfyui-gpu-offload/</link><guid isPermaLink="true">https://retrivium.ai/journal/comfyui-gpu-offload/</guid><description>Evaluate ComfyUI offloading with the installed Dynamic VRAM behavior, RAM and disk observations, repeated jobs and full-workflow timing.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Multiple GPUs for ComfyUI: one workflow or separate queues?</title><link>https://retrivium.ai/journal/comfyui-multi-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/comfyui-multi-gpu/</guid><description>Compare independent ComfyUI GPU workers with supported multi-device graph placement, preserving queue, storage and per-device memory measurements.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>ComfyUI in the cloud: keeping models, workflows and outputs</title><link>https://retrivium.ai/journal/comfyui-cloud-persistence/</link><guid isPermaLink="true">https://retrivium.ai/journal/comfyui-cloud-persistence/</guid><description>Preserve ComfyUI cloud models, node versions, workflows, inputs and outputs with an explicit storage map and a tested replacement-instance restore.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Stable Diffusion GPU requirements: resolution, batch and weights</title><link>https://retrivium.ai/journal/stable-diffusion-gpu-requirements/</link><guid isPermaLink="true">https://retrivium.ai/journal/stable-diffusion-gpu-requirements/</guid><description>Estimate Stable Diffusion GPU memory from the actual pipeline, resolution, batch, precision, extra components and VAE stage, then test useful outputs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Benchmarking GPUs for Stable Diffusion reproducibly</title><link>https://retrivium.ai/journal/stable-diffusion-gpu-benchmark/</link><guid isPermaLink="true">https://retrivium.ai/journal/stable-diffusion-gpu-benchmark/</guid><description>Benchmark Stable Diffusion GPUs with fixed pipeline settings, separate cold and warm timings, complete-image throughput and memory-aware comparisons.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LoRA and QLoRA: understanding fine-tuning memory</title><link>https://retrivium.ai/journal/lora-qlora-memory/</link><guid isPermaLink="true">https://retrivium.ai/journal/lora-qlora-memory/</guid><description>Compare full fine-tuning, LoRA and QLoRA by trainable parameters, base-weight format, activations, optimizer state and complete-step memory.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A bounded PEFT and LoRA experiment on your GPU</title><link>https://retrivium.ai/journal/peft-lora-gpu-budget/</link><guid isPermaLink="true">https://retrivium.ai/journal/peft-lora-gpu-budget/</guid><description>Plan a small PEFT and LoRA experiment with authorized data, a held-out baseline, measured training steps and a verified saved adapter.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A 128 GB RAM server for LLMs: useful roles beyond VRAM</title><link>https://retrivium.ai/journal/server-128gb-ram-llm/</link><guid isPermaLink="true">https://retrivium.ai/journal/server-128gb-ram-llm/</guid><description>Find useful roles for a 128 GB RAM server across CPU inference, supported offloading, document preparation and retrieval without confusing RAM with VRAM.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>256 GB RAM for RAG: when the index justifies the capacity</title><link>https://retrivium.ai/journal/server-256gb-ram-rag/</link><guid isPermaLink="true">https://retrivium.ai/journal/server-256gb-ram-rag/</guid><description>Size a 256 GB RAM RAG server from vectors, indexes, payload, replicas, updates and concurrent queries, then validate a representative collection.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>An inference API conformance matrix for providers</title><link>https://retrivium.ai/journal/provider-api-conformance-matrix/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-api-conformance-matrix/</guid><description>Build a verifiable inference API compatibility matrix covering parameters, response modes, fixtures, versions and the limits of provider integration evidence.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Unsupported inference parameters: rejection, ignoring and the contract</title><link>https://retrivium.ai/journal/provider-unsupported-parameter-policy/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-unsupported-parameter-policy/</guid><description>Define inference API behavior for unsupported parameters through explicit rejection, documented ignoring and tests that distinguish acceptance from application.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Absent fields, null and empty strings in an inference API</title><link>https://retrivium.ai/journal/provider-json-absent-null-empty/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-json-absent-null-empty/</guid><description>Test absent fields, null, empty strings and empty arrays in an inference API with fixtures covering roles, validation and safe normalization boundaries.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>finish_reason as a provider response state machine</title><link>https://retrivium.ai/journal/provider-finish-reason-state-machine/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-finish-reason-state-machine/</guid><description>Model finish_reason and native_finish_reason as state transitions covering choice completion, accounting frames, failures and valid streaming sequences.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Streaming tool calls: assembling arguments by index and ID</title><link>https://retrivium.ai/journal/provider-streamed-tool-argument-assembly/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-streamed-tool-argument-assembly/</guid><description>Validate streamed tool calls by assembling arguments per index, preserving IDs and preventing execution of incomplete JSON while response fragments arrive.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The final usage frame: validating a streaming response contract</title><link>https://retrivium.ai/journal/provider-final-usage-frame-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-final-usage-frame-contract/</guid><description>Validate a final usage chunk without counting completion twice, accounting for choices shape, DONE ordering and differences between external and upstream APIs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why prompt_tokens differs from tokenizing the visible text</title><link>https://retrivium.ai/journal/provider-prompt-token-template-accounting/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-prompt-token-template-accounting/</guid><description>Explain prompt-token differences through chat templates, control tokens and tokenizer revisions, then build a reproducible reconciliation fixture.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Output limits and reasoning tokens: the length-termination contract</title><link>https://retrivium.ai/journal/provider-output-limit-reasoning-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-output-limit-reasoning-contract/</guid><description>Test length termination under output limits with reasoning tokens, empty visible content, distinct counters and reproducible API contract fixtures.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Provider content parts: validating structure before generation</title><link>https://retrivium.ai/journal/provider-message-content-parts-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-message-content-parts-contract/</guid><description>Validate string content and text/image part arrays before model execution using role checks, nested-field fixtures and explicit capability boundaries.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Provider structured output: testing JSON and schema conformance separately</title><link>https://retrivium.ai/journal/provider-structured-output-conformance-tests/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-structured-output-conformance-tests/</guid><description>Test provider structured output across JSON syntax, required properties, types, extra fields and the actual support boundary of the selected backend.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The logprobs contract: aligning tokens and returned scores</title><link>https://retrivium.ai/journal/provider-logprobs-response-consistency/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-logprobs-response-consistency/</guid><description>Check logprobs and top_logprobs in an inference API across opt-in behavior, output-position alignment, streaming and limits on interpreting scores.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Model aliases and revisions: provider response identity</title><link>https://retrivium.ai/journal/provider-model-alias-revision-identity/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-model-alias-revision-identity/</guid><description>Connect a public model alias to its artifact revision, tokenizer and chat template through response identity checks and a verifiable release record.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SSE and UTF-8: a network chunk is not a JSON event</title><link>https://retrivium.ai/journal/provider-sse-utf8-chunk-boundaries/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-sse-utf8-chunk-boundaries/</guid><description>Understand why network reads are not SSE events and preserve UTF-8 across chunks with incremental decoding, framing, fragmentation fixtures and bounded buffers.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SSE completion: blank lines, DONE and unexpected EOF</title><link>https://retrivium.ai/journal/provider-sse-terminal-eof-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-sse-terminal-eof-contract/</guid><description>Distinguish SSE event completion, DONE and HTTP closure using minimal traces, unexpected EOF cases, usage checks and explicit completeness states.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SSE heartbeats and idle timeouts: what keeps a connection alive</title><link>https://retrivium.ai/journal/provider-sse-heartbeat-timeout-budget/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-sse-heartbeat-timeout-budget/</guid><description>Relate SSE comments, heartbeats and idle timeouts while measuring useful-output delays separately and testing the actual reverse-proxy configuration.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Slow SSE clients: backpressure and bounded memory</title><link>https://retrivium.ai/journal/provider-sse-slow-reader-backpressure/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-sse-slow-reader-backpressure/</guid><description>Test inference streams with slow readers through backpressure, bounded queues and memory, transport flow control and independently verified generation cancellation.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Testing SSE buffering at a reverse proxy</title><link>https://retrivium.ai/journal/provider-proxy-sse-buffering-test/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-proxy-sse-buffering-test/</guid><description>Measure reverse-proxy SSE buffering through direct and proxied paths, proxy_buffering, X-Accel-Buffering and an event-arrival timeline.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>HTTP response integrity: Content-Length, chunked transfer and truncation</title><link>https://retrivium.ai/journal/provider-http-message-framing-integrity/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-http-message-framing-integrity/</guid><description>Distinguish HTTP body integrity from SSE completion through Content-Length, chunked transfer, premature closure and controlled local fixtures.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>HTTP/2 GOAWAY during inference endpoint updates</title><link>https://retrivium.ai/journal/provider-http2-goaway-draining/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-http2-goaway-draining/</guid><description>Test HTTP/2 GOAWAY during inference updates through last-stream-ID, accepted requests, ambiguous POST outcomes and a bounded draining experiment.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SSE reconnection does not imply resuming an LLM generation</title><link>https://retrivium.ai/journal/provider-sse-reconnect-generation-resume/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-sse-reconnect-generation-resume/</guid><description>Explain why SSE reconnect and Last-Event-ID do not guarantee LLM generation resumption across EventSource, POST fetch, replay and deduplication boundaries.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Request cancellation: testing the full client-to-engine chain</title><link>https://retrivium.ai/journal/provider-client-disconnect-cancellation-chain/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-client-disconnect-cancellation-chain/</guid><description>Verify inference cancellation across client abort, proxy behavior, engine operations, in-flight counters and resource cleanup without assuming propagation.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Graceful inference-server termination with active streams</title><link>https://retrivium.ai/journal/provider-graceful-termination-active-streams/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-graceful-termination-active-streams/</guid><description>Terminate an inference server with active SSE through admission shutdown, draining, preStop, grace periods and checks of actual per-request outcomes.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Request deadlines: budgeting queueing, prefill and streaming</title><link>https://retrivium.ai/journal/provider-request-deadline-stage-budget/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-request-deadline-stage-budget/</guid><description>Budget inference request deadlines across queueing, prefill and output while distinguishing absolute duration, idle timeout, cancellation and observable boundaries.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>HTTP body limits and token limits: separate inference API checks</title><link>https://retrivium.ai/journal/provider-request-body-size-limits/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-request-body-size-limits/</guid><description>Separate HTTP body limits, JSON parsing and model context budgets with staged validation, compressed-input checks, fixtures and accurate rejection classification.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Provider overload: Retry-After as part of the contract</title><link>https://retrivium.ai/journal/provider-overload-retry-after-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-overload-retry-after-contract/</guid><description>Describe inference overload before SSE commitment through rate policy, Retry-After, bounded retries and tests of the provider’s actual rejection contract.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Retrying generation POSTs: idempotency must be explicit</title><link>https://retrivium.ai/journal/provider-post-retry-idempotency-ledger/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-post-retry-idempotency-ledger/</guid><description>Design generation POST retries without assumed idempotency by defining ambiguous outcomes, request ledgers, deduplication scope and testable interface behavior.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Provider admission control: bound the queue before latency grows</title><link>https://retrivium.ai/journal/provider-admission-queue-budget/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-admission-queue-budget/</guid><description>Bound inference admission through rate gates, in-flight limits, engine queues, controlled bursts and observable reasons for early rejection.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Keeping model capabilities and rollout state consistent</title><link>https://retrivium.ai/journal/provider-capability-rollout-consistency/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-capability-rollout-consistency/</guid><description>Keep advertised model capabilities aligned with replica rollout through feature matrices, readiness checks, tools and schema fixtures, publication and rollback.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Startup, readiness and liveness for a slow-loading model server</title><link>https://retrivium.ai/journal/provider-startup-readiness-liveness-separation/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-startup-readiness-liveness-separation/</guid><description>Separate startup, readiness and liveness during long model loading through distinct criteria, thresholds, restart failure modes and a bounded validation scenario.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Monotonic clocks for inference API latency measurements</title><link>https://retrivium.ai/journal/provider-monotonic-latency-measurement/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-monotonic-latency-measurement/</guid><description>Measure inference API latency with monotonic clocks while separating in-process durations, wall-clock correlation, host boundaries and event-record semantics.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>First byte, first chunk and first token are different latencies</title><link>https://retrivium.ai/journal/provider-first-byte-first-chunk-first-token/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-first-byte-first-chunk-first-token/</guid><description>Distinguish first byte, first chunk and first token in inference APIs across comments, role deltas, reasoning, useful content and versioned latency SLIs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Inter-token gaps and throughput: do not average different quantities</title><link>https://retrivium.ai/journal/provider-intertoken-gap-throughput-metrics/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-intertoken-gap-throughput-metrics/</guid><description>Distinguish TPOT, SSE event gaps and aggregate throughput through measurement boundaries, zero- and one-token outputs, weighting and a reproducible example.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Fleet p95: aggregate histograms rather than precomputed percentiles</title><link>https://retrivium.ai/journal/provider-latency-histogram-aggregation/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-latency-histogram-aggregation/</guid><description>Calculate p95 across inference replicas with histogram aggregation, compatible boundaries and cohort filters rather than averaging replica percentiles.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A successful stream for an SLO: define the event and denominator</title><link>https://retrivium.ai/journal/provider-stream-success-sli-denominator/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-stream-success-sli-denominator/</guid><description>Define a successful inference stream for SLOs across accepted, rejected, completed, failed and cancelled work, partial answers and explicit good-event denominators.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Inference SLO burn rates: multi-window alerting</title><link>https://retrivium.ai/journal/provider-error-budget-burn-rate-alerts/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-error-budget-burn-rate-alerts/</guid><description>Build inference SLO burn-rate alerts using error budgets, multiple windows, low-traffic handling and rule tests against synthetic time series.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Provider metric cardinality: request IDs do not belong in labels</title><link>https://retrivium.ai/journal/provider-metric-cardinality-budget/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-metric-cardinality-budget/</guid><description>Plan inference-provider metric cardinality through label products, model and outcome dimensions, histogram buckets and unique IDs kept in traces instead.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Request IDs and trace context across gateway, API and engine</title><link>https://retrivium.ai/journal/provider-request-id-trace-context/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-request-id-trace-context/</guid><description>Separate generation IDs, internal request IDs and trace/span IDs through uniqueness scopes, propagation, safe correlation and missing-context fixtures.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenTelemetry GenAI: pin the semantic-convention version</title><link>https://retrivium.ai/journal/provider-otel-genai-semconv-versioning/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-otel-genai-semconv-versioning/</guid><description>Pin OpenTelemetry GenAI convention versions across the current official repository, Development status, instrumentation scope, metric names and exporter migration tests.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Inference API telemetry without default prompt capture</title><link>https://retrivium.ai/journal/provider-telemetry-content-redaction/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-telemetry-content-redaction/</guid><description>Observe inference APIs without default prompt capture using metadata allowlists, nested tool arguments, error paths and exported-payload redaction tests.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>From a slow histogram bucket to a trace through an exemplar</title><link>https://retrivium.ai/journal/provider-metric-exemplar-trace-link/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-metric-exemplar-trace-link/</guid><description>Connect a slow histogram observation to a trace through exemplars while accounting for sampling, trace availability, metadata limits and navigation tests.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Terminal request records: reconcile stream, usage and logs</title><link>https://retrivium.ai/journal/provider-terminal-request-record-consistency/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-terminal-request-record-consistency/</guid><description>Build one terminal inference request record, reconcile stream completion and usage, and avoid duplicate outcomes when telemetry events are redelivered.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Golden inference API fixtures: test the contract rather than prose</title><link>https://retrivium.ai/journal/provider-golden-contract-fixtures/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-golden-contract-fixtures/</guid><description>A compact versioned JSON and SSE fixture suite for inference API contracts, covering required fields, terminal states, privacy and baseline updates.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>SSE property tests: one event stream under any byte partition</title><link>https://retrivium.ai/journal/provider-sse-fragmentation-property-tests/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-sse-fragmentation-property-tests/</guid><description>Test an SSE parser with randomized byte boundaries, stable event invariants, Unicode, CRLF cases, minimal counterexamples and bounded execution.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Differential API testing across two inference engines</title><link>https://retrivium.ai/journal/provider-engine-differential-api-tests/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-engine-differential-api-tests/</guid><description>Differential tests for two inference engines, comparing schemas and terminal states with an explicit differences register separate from text quality.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Open and closed load models for an inference API</title><link>https://retrivium.ai/journal/provider-open-closed-load-tests/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-open-closed-load-tests/</guid><description>Why fixed concurrency can hide inference API overload, and how to compare open arrivals with a closed load model in a bounded experiment.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A bounded cancellation soak test for request and connection leaks</title><link>https://retrivium.ai/journal/provider-cancel-soak-resource-leaks/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-cancel-soak-resource-leaks/</guid><description>A bounded inference completion and cancellation test with resource baselines, recovery pauses, stop conditions and investigation of suspicious growth.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Local fault injection: interrupting an upstream at a known stream boundary</title><link>https://retrivium.ai/journal/provider-midstream-fault-injection-tests/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-midstream-fault-injection-tests/</guid><description>A local fake upstream for SSE faults before headers, after headers and after content, with outcome classification, bounded retries and a replay artifact.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Seeds and fingerprints: testing an API reproducibility claim</title><link>https://retrivium.ai/journal/provider-seed-fingerprint-contract-tests/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-seed-fingerprint-contract-tests/</guid><description>How to test seed and system_fingerprint in an inference API, distinguishing field support, fixed environment repeatability and limits across versions.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A token-budgeted synthetic probe for an inference endpoint</title><link>https://retrivium.ai/journal/provider-bounded-synthetic-probe-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-bounded-synthetic-probe-contract/</guid><description>An external inference endpoint probe with a small request, token and frequency limits, schema and completion checks, and clear boundaries from user SLOs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Changing an inference API contract: deprecation and migration checks</title><link>https://retrivium.ai/journal/provider-api-contract-deprecation-migration/</link><guid isPermaLink="true">https://retrivium.ai/journal/provider-api-contract-deprecation-migration/</guid><description>How to evolve an inference API contract using schema diffs, client compatibility checks, Deprecation semantics and tested JSON and SSE fixture migrations.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM chat templates: fix string versus OpenAI content formats</title><link>https://retrivium.ai/journal/vllm-chat-content-format/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-chat-content-format/</guid><description>Fix a content format mismatch by aligning the client message with the model&apos;s chat template.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Match prompt token IDs between Hugging Face and vLLM</title><link>https://retrivium.ai/journal/vllm-render-token-parity/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-render-token-parity/</guid><description>Identical prompt text does not guarantee identical input tokens. To compare Hugging Face with vLLM, keep one message history, the same tokenizer revision, and the actual token IDs produced after templating.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why generation_config.json changes vLLM generation defaults</title><link>https://retrivium.ai/journal/vllm-generation-config-precedence/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-generation-config-precedence/</guid><description>vLLM responses can change after a model-repository update because of generation_config.json, even when the launch command stays identical.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>vLLM stop strings and EOS: diagnose premature response endings</title><link>https://retrivium.ai/journal/vllm-stop-eos-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-stop-eos-contract/</guid><description>Diagnose an early vLLM response ending by identifying the stopping mechanism: a stop string, an ID in stop_token_ids, and EOS serve different purposes.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Migrate vLLM structured-output backends without schema regressions</title><link>https://retrivium.ai/journal/vllm-structured-backend-migration/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-structured-backend-migration/</guid><description>Changing a vLLM structured-output backend requires fresh schema and regular-expression tests.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Align vLLM tool parsers, chat templates and tool-result messages</title><link>https://retrivium.ai/journal/vllm-tool-parser-template-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-tool-parser-template-contract/</guid><description>Reliable vLLM tool calling requires a compatible parser, chat template, and conversation history containing tool results.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Validate reasoning and answer boundaries in vLLM parser output</title><link>https://retrivium.ai/journal/vllm-reasoning-parser-boundaries/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-reasoning-parser-boundaries/</guid><description>A vLLM reasoning parser separates generated text into reasoning and final-answer fields.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Validate a draft and target model pair for vLLM speculative decoding</title><link>https://retrivium.ai/journal/vllm-draft-target-validation/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-draft-target-validation/</guid><description>Validate a vLLM speculative-decoding draft and target as one configuration, rather than choosing a small model by size alone.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Evaluate vLLM n-gram speculation without a draft model</title><link>https://retrivium.ai/journal/vllm-ngram-speculation-evaluation/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-ngram-speculation-evaluation/</guid><description>vLLM n-gram speculation proposes continuations from matches within the prompt without loading a separate draft model.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Tune vLLM chunked prefill token budgets for mixed traffic</title><link>https://retrivium.ai/journal/vllm-chunked-prefill-token-budget/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-chunked-prefill-token-budget/</guid><description>Tune the vLLM chunked-prefill token budget against a mixture of new long prompts and requests already generating answers.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Bound vLLM request queues and prefill token backlogs</title><link>https://retrivium.ai/journal/vllm-admission-token-backlog/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-admission-token-backlog/</guid><description>Bound vLLM backlog using the work accepted by the serving system: request count and pending prefill volume are different quantities.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Manage vLLM torch.compile caches across releases</title><link>https://retrivium.ai/journal/vllm-compile-cache-release/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-compile-cache-release/</guid><description>A vLLM compilation cache can shorten a compatible repeat startup, but copying its directory does not establish compatibility with a new release.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Detect vLLM CUDA Graph mode fallbacks after upgrades</title><link>https://retrivium.ai/journal/vllm-cuda-graph-mode-compatibility/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-cuda-graph-mode-compatibility/</guid><description>After upgrading vLLM, inspect the effective CUDA Graph mode rather than only the requested setting.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Choose vLLM safetensors loading strategies for local disks and NFS</title><link>https://retrivium.ai/journal/vllm-safetensors-load-strategy/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-safetensors-load-strategy/</guid><description>Choose a vLLM safetensors loading strategy from filesystem behavior and available RAM, not model quality.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Validate vLLM sleep and wake readiness transitions</title><link>https://retrivium.ai/journal/vllm-sleep-wake-readiness/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-sleep-wake-readiness/</guid><description>vLLM sleep mode needs an explicit procedure for returning a model to service. A live API process does not establish that weights are restored and KV memory is allocated.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Validate target-specific EAGLE draft checkpoints in SGLang</title><link>https://retrivium.ai/journal/sglang-eagle-draft-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-eagle-draft-contract/</guid><description>An EAGLE draft checkpoint in SGLang must match the particular target model and method implementation.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Diagnose tokenizer and detokenizer worker bottlenecks in SGLang</title><link>https://retrivium.ai/journal/sglang-tokenizer-worker-bottleneck/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-tokenizer-worker-bottleneck/</guid><description>When SGLang accepts requests slowly while the GPU is idle, inspect tokenizer and detokenizer workers before changing GPU memory fraction.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Tune SGLang schedule conservativeness for output-length uncertainty</title><link>https://retrivium.ai/journal/sglang-schedule-conservativeness/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-schedule-conservativeness/</guid><description>Tune SGLang schedule conservativeness around uncertainty in future answer length, not as a substitute for the GPU memory budget.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Compare SGLang Radix eviction policies under hot-set churn</title><link>https://retrivium.ai/journal/sglang-radix-eviction-hotset/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-radix-eviction-hotset/</guid><description>Choose a SGLang Radix-cache eviction policy from the pattern of prefix reuse. LRU, LFU, and SLRU can behave differently when a stable hot set encounters a burst of one-off inputs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Diagnose KV transfer stalls in SGLang prefill-decode disaggregation</title><link>https://retrivium.ai/journal/sglang-pd-kv-transfer-diagnosis/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-pd-kv-transfer-diagnosis/</guid><description>With SGLang prefill-decode disaggregation, separate KV-transfer delay from computation on both stages.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Validate FP8 and FP4 GEMM backends against SGLang checkpoints</title><link>https://retrivium.ai/journal/sglang-quantized-gemm-backends/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-quantized-gemm-backends/</guid><description>Check SGLang FP8 or FP4 compatibility across the checkpoint, scaling recipe, GPU architecture, and GEMM backend.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why temperature zero is not enough for deterministic SGLang output</title><link>https://retrivium.ai/journal/sglang-deterministic-batch-invariance/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-deterministic-batch-invariance/</guid><description>Temperature zero in SGLang does not guarantee identical output when batch composition changes.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Separate multimodal encoder data parallelism from SGLang language-model TP</title><link>https://retrivium.ai/journal/sglang-multimodal-encoder-dp/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-multimodal-encoder-dp/</guid><description>SGLang multimodal-encoder data parallelism is different from tensor parallelism in the language-model component.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Correlate SGLang request latency across workers with OpenTelemetry</title><link>https://retrivium.ai/journal/sglang-opentelemetry-request-traces/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-opentelemetry-request-traces/</guid><description>SGLang tracing can explain one request&apos;s latency across workers when aggregate TTFT is insufficient.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Gate SGLang readiness on actual checkpoint-engine weights</title><link>https://retrivium.ai/journal/sglang-checkpoint-readiness-gate/</link><guid isPermaLink="true">https://retrivium.ai/journal/sglang-checkpoint-readiness-gate/</guid><description>When SGLang uses a checkpoint engine, distinguish process readiness from receiving actual weights.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Make llama.cpp automatic fit settings reproducible</title><link>https://retrivium.ai/journal/llama-cpp-fit-reproducible-settings/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-cpp-fit-reproducible-settings/</guid><description>llama.cpp automatic fit can adjust unspecified settings to fit available device memory.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Reconcile llama.cpp unified KV pools and per-slot context limits</title><link>https://retrivium.ai/journal/llama-cpp-unified-kv-slot-limits/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-cpp-unified-kv-slot-limits/</guid><description>Account for a llama.cpp shared KV pool separately from the context of one parallel slot.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Manage resident models and eviction in the llama.cpp router</title><link>https://retrivium.ai/journal/llama-cpp-router-model-residency/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-cpp-router-model-residency/</guid><description>Validate the llama.cpp model router through actual residency and child-process state.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Validate JSON Schema to GBNF conversion in llama.cpp</title><link>https://retrivium.ai/journal/llama-cpp-json-schema-gbnf-validation/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-cpp-json-schema-gbnf-validation/</guid><description>Converting JSON Schema to GBNF for llama.cpp does not establish that every schema constraint is enforced.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Validate llama.cpp slot prompt-cache save and restore files</title><link>https://retrivium.ai/journal/llama-cpp-slot-cache-persistence/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-cpp-slot-cache-persistence/</guid><description>Validate llama.cpp slot prompt-cache persistence as a save-and-restore lifecycle for a specific state.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Tune llama.cpp CPU threads separately for prefill and decode</title><link>https://retrivium.ai/journal/llama-cpp-prefill-decode-cpu-threads/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-cpp-prefill-decode-cpu-threads/</guid><description>Tune llama.cpp CPU threads for prompt processing and token generation separately.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Build llama.cpp CUDA binaries for multiple GPU architectures</title><link>https://retrivium.ai/journal/llama-cpp-portable-cuda-build/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-cpp-portable-cuda-build/</guid><description>Before moving a llama.cpp CUDA binary to another GPU, check its compiled architecture targets.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Verify split GGUF shards before merging a llama.cpp model</title><link>https://retrivium.ai/journal/llama-cpp-split-gguf-integrity/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-cpp-split-gguf-integrity/</guid><description>Accept a split GGUF as a complete shard set rather than one plausibly named file.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Validate llama.cpp language-model and mmproj projector pairs</title><link>https://retrivium.ai/journal/llama-cpp-mmproj-pair-validation/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-cpp-mmproj-pair-validation/</guid><description>A llama.cpp language GGUF and mmproj must form a supported multimodal pair. A projector from a similar model is not interchangeable merely because its file size or family name resembles the intended artifact.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Use llama-bench to isolate prefill and generation regressions</title><link>https://retrivium.ai/journal/llama-bench-phase-regression/</link><guid isPermaLink="true">https://retrivium.ai/journal/llama-bench-phase-regression/</guid><description>To localize a llama.cpp regression, separate prompt processing from token generation with llama-bench first.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Handle final completion correctly in Triton decoupled streaming</title><link>https://retrivium.ai/journal/triton-decoupled-stream-completion/</link><guid isPermaLink="true">https://retrivium.ai/journal/triton-decoupled-stream-completion/</guid><description>In Triton decoupled mode, identify completion through the protocol signal rather than the last nonempty text fragment.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Identify which scheduler owns batching in Triton and TensorRT-LLM</title><link>https://retrivium.ai/journal/triton-llmapi-batching-boundaries/</link><guid isPermaLink="true">https://retrivium.ai/journal/triton-llmapi-batching-boundaries/</guid><description>For Triton and TensorRT-LLM, first identify which component forms batches in the selected deployment path.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Define variable-length token input contracts for Triton ragged batching</title><link>https://retrivium.ai/journal/triton-ragged-token-input-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/triton-ragged-token-input-contract/</guid><description>Triton ragged batching needs an agreed variable-length contract among client, model, and backend.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Verify Triton generation cancellation beyond a client disconnect</title><link>https://retrivium.ai/journal/triton-inference-cancellation/</link><guid isPermaLink="true">https://retrivium.ai/journal/triton-inference-cancellation/</guid><description>Validate Triton cancellation through a supported protocol action and terminated processing, not merely a closed client window.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Migrate legacy Triton TensorRT-LLM engine builds to the LLM API</title><link>https://retrivium.ai/journal/tensorrt-llm-triton-llmapi-migration/</link><guid isPermaLink="true">https://retrivium.ai/journal/tensorrt-llm-triton-llmapi-migration/</guid><description>Start a Triton TensorRT-LLM migration by identifying the deployment path rather than automatically repeating trtllm-build.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Check TensorRT engine portability across GPUs and runtime versions</title><link>https://retrivium.ai/journal/tensorrt-plan-portability/</link><guid isPermaLink="true">https://retrivium.ai/journal/tensorrt-plan-portability/</guid><description>A serialized TensorRT engine is not a universal file for every NVIDIA GPU and runtime release.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Coordinate Triton model reloads, control modes and version policies</title><link>https://retrivium.ai/journal/triton-model-control-version-policy/</link><guid isPermaLink="true">https://retrivium.ai/journal/triton-model-control-version-policy/</guid><description>Validate Triton repository updates together with model-control mode and version policy.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Validate tokenizer, inference and postprocessing contracts in Triton ensembles</title><link>https://retrivium.ai/journal/triton-tokenizer-ensemble-contract/</link><guid isPermaLink="true">https://retrivium.ai/journal/triton-tokenizer-ensemble-contract/</guid><description>Validate a Triton ensemble as a tensor-dataflow graph connecting preprocessing, inference, and postprocessing.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Separate Triton queue, input, inference and output latency</title><link>https://retrivium.ai/journal/triton-latency-stage-diagnosis/</link><guid isPermaLink="true">https://retrivium.ai/journal/triton-latency-stage-diagnosis/</guid><description>Diagnose Triton latency through queueing, input processing, inference, and output processing.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Validate ModelOpt quantized checkpoint scales and export provenance</title><link>https://retrivium.ai/journal/modelopt-quantized-checkpoint-provenance/</link><guid isPermaLink="true">https://retrivium.ai/journal/modelopt-quantized-checkpoint-provenance/</guid><description>Accept a quantized ModelOpt checkpoint together with scales, quantization configuration, and calibration provenance.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Prepare a complete pinned Hugging Face snapshot for offline serving</title><link>https://retrivium.ai/journal/huggingface-pinned-offline-snapshot/</link><guid isPermaLink="true">https://retrivium.ai/journal/huggingface-pinned-offline-snapshot/</guid><description>Offline LLM startup requires a complete, consistent model snapshot rather than only downloaded weights.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Pin and review custom model code before enabling trust_remote_code</title><link>https://retrivium.ai/journal/huggingface-remote-code-review/</link><guid isPermaLink="true">https://retrivium.ai/journal/huggingface-remote-code-review/</guid><description>trust_remote_code allows a loader to use Python implementation code from a custom model repository.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Validate safetensors weight artifacts separately from repository code</title><link>https://retrivium.ai/journal/safetensors-artifact-validation/</link><guid isPermaLink="true">https://retrivium.ai/journal/safetensors-artifact-validation/</guid><description>Distinguish safetensors from pickle by serialization mechanism, and validate weight integrity separately.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Keep tokenizer vocabulary, special tokens and chat templates in one release</title><link>https://retrivium.ai/journal/tokenizer-artifact-release-manifest/</link><guid isPermaLink="true">https://retrivium.ai/journal/tokenizer-artifact-release-manifest/</guid><description>Accept a tokenizer release as a consistent vocabulary, special-token, and chat-template package.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Validate vLLM automatic and explicitly pinned attention backends</title><link>https://retrivium.ai/journal/vllm-attention-backend-acceptance/</link><guid isPermaLink="true">https://retrivium.ai/journal/vllm-attention-backend-acceptance/</guid><description>Accept a vLLM attention backend through its effective selection and support for the model configuration.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Container stalls without OOM: reading memory.high and memory.events</title><link>https://retrivium.ai/journal/cgroup-v2-memory-high-events/</link><guid isPermaLink="true">https://retrivium.ai/journal/cgroup-v2-memory-high-events/</guid><description>Diagnose container stalls without OOM: reading memory.high and memory.events. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Idle GPU, throttled CPU: diagnosing container CPU quota</title><link>https://retrivium.ai/journal/cgroup-cpu-throttling-gpu-feeder/</link><guid isPermaLink="true">https://retrivium.ai/journal/cgroup-cpu-throttling-gpu-feeder/</guid><description>Diagnose idle GPU, throttled CPU: diagnosing container CPU quota. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Cannot create thread in a container: checking pids.max and pids.events</title><link>https://retrivium.ai/journal/container-pids-limit-thread-errors/</link><guid isPermaLink="true">https://retrivium.ai/journal/container-pids-limit-thread-errors/</guid><description>Diagnose cannot create thread in a container: checking pids.max and pids.events. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Out of /dev/shm: setting a GPU container IPC budget</title><link>https://retrivium.ai/journal/container-dev-shm-ipc-budget/</link><guid isPermaLink="true">https://retrivium.ai/journal/container-dev-shm-ipc-budget/</guid><description>Diagnose out of /dev/shm: setting a GPU container IPC budget. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OOMKilled or Evicted: identifying why a Pod stopped</title><link>https://retrivium.ai/journal/kubernetes-oomkilled-vs-evicted/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-oomkilled-vs-evicted/</guid><description>Diagnose oOMKilled or Evicted: identifying why a Pod stopped. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>High latency at moderate utilization: diagnosing Linux PSI</title><link>https://retrivium.ai/journal/linux-psi-inference-stalls/</link><guid isPermaLink="true">https://retrivium.ai/journal/linux-psi-inference-stalls/</guid><description>Diagnose high latency at moderate utilization: diagnosing Linux PSI. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Too many open files in a container: finding the exhausted limit</title><link>https://retrivium.ai/journal/container-file-descriptor-exhaustion/</link><guid isPermaLink="true">https://retrivium.ai/journal/container-file-descriptor-exhaustion/</guid><description>Diagnose too many open files in a container: finding the exhausted limit. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Container blocked on stdout: Docker log backpressure and rotation</title><link>https://retrivium.ai/journal/docker-log-rotation-application-blocking/</link><guid isPermaLink="true">https://retrivium.ai/journal/docker-log-rotation-application-blocking/</guid><description>Diagnose container blocked on stdout: Docker log backpressure and rotation. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why docker stop cannot stop a worker: PID 1, signals and zombies</title><link>https://retrivium.ai/journal/container-pid1-signals-zombies/</link><guid isPermaLink="true">https://retrivium.ai/journal/container-pid1-signals-zombies/</guid><description>Diagnose why docker stop cannot stop a worker: PID 1, signals and zombies. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Host swap exists but the container cannot use it: checking limits</title><link>https://retrivium.ai/journal/container-swap-limit-mismatch/</link><guid isPermaLink="true">https://retrivium.ai/journal/container-swap-limit-mismatch/</guid><description>Diagnose host swap exists but the container cannot use it: checking limits. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Pod restarts while loading: configuring a startup probe</title><link>https://retrivium.ai/journal/kubernetes-startup-probe-restart-loop/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-startup-probe-restart-loop/</guid><description>Diagnose pod restarts while loading: configuring a startup probe. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>preStop consumes the grace period: budgeting Pod termination</title><link>https://retrivium.ai/journal/kubernetes-prestop-termination-budget/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-prestop-termination-budget/</guid><description>Diagnose preStop consumes the grace period: budgeting Pod termination. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>kubectl drain blocked by a PDB: what a disruption budget protects</title><link>https://retrivium.ai/journal/kubernetes-pdb-voluntary-disruption/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-pdb-voluntary-disruption/</guid><description>Diagnose kubectl drain blocked by a PDB: what a disruption budget protects. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU Deployment rollout stuck: maxSurge without spare capacity</title><link>https://retrivium.ai/journal/kubernetes-gpu-rollout-surge-deadlock/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-gpu-rollout-surge-deadlock/</guid><description>Diagnose gPU Deployment rollout stuck: maxSurge without spare capacity. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Pod is Terminating but still receives traffic: checking EndpointSlices</title><link>https://retrivium.ai/journal/kubernetes-terminating-endpoints/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-terminating-endpoints/</guid><description>Diagnose pod is Terminating but still receives traffic: checking EndpointSlices. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>ImagePullBackOff before GPU startup: image names, registry and Secrets</title><link>https://retrivium.ai/journal/kubernetes-imagepullbackoff-registry-auth/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-imagepullbackoff-registry-auth/</guid><description>Diagnose imagePullBackOff before GPU startup: image names, registry and Secrets. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Init container downloads an artifact again: making preparation idempotent</title><link>https://retrivium.ai/journal/kubernetes-init-artifact-download/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-init-artifact-download/</guid><description>Diagnose init container downloads an artifact again: making preparation idempotent. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Resource stuck Terminating: diagnosing a Kubernetes finalizer</title><link>https://retrivium.ai/journal/kubernetes-finalizer-stuck-deletion/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-finalizer-stuck-deletion/</guid><description>Diagnose resource stuck Terminating: diagnosing a Kubernetes finalizer. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Node NotReady but the Pod does not move: tolerations and eviction</title><link>https://retrivium.ai/journal/kubernetes-node-notready-taint-delay/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-node-notready-taint-delay/</guid><description>Diagnose node NotReady but the Pod does not move: tolerations and eviction. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>No shell in the image: debugging a Pod with an ephemeral container</title><link>https://retrivium.ai/journal/kubernetes-ephemeral-container-debug/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-ephemeral-container-debug/</guid><description>Diagnose no shell in the image: debugging a Pod with an ephemeral container. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVIDIA_VISIBLE_DEVICES vs CUDA_VISIBLE_DEVICES: why GPU indexes differ</title><link>https://retrivium.ai/journal/nvidia-visible-vs-cuda-visible-devices/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-visible-vs-cuda-visible-devices/</guid><description>Diagnose nVIDIA_VISIBLE_DEVICES vs CUDA_VISIBLE_DEVICES: why GPU indexes differ. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CDI device not found: checking NVIDIA device names and specifications</title><link>https://retrivium.ai/journal/nvidia-cdi-device-selection/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-cdi-device-selection/</guid><description>Diagnose cDI device not found: checking NVIDIA device names and specifications. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVML Unknown Error after daemon-reload: when a container loses its GPU</title><link>https://retrivium.ai/journal/nvidia-container-nvml-systemd-reload/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-container-nvml-systemd-reload/</guid><description>Diagnose nVML Unknown Error after daemon-reload: when a container loses its GPU. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>nvidia-smi works but CUDA does not: checking compute and utility capabilities</title><link>https://retrivium.ai/journal/nvidia-driver-capabilities-compute-utility/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvidia-driver-capabilities-compute-utility/</guid><description>Diagnose nvidia-smi works but CUDA does not: checking compute and utility capabilities. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Slow DNS in a Pod: search domains and ndots</title><link>https://retrivium.ai/journal/kubernetes-dns-ndots-search-latency/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-dns-ndots-search-latency/</guid><description>Diagnose slow DNS in a Pod: search domains and ndots. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Some DNS queries fail: why TCP and UDP port 53 both matter</title><link>https://retrivium.ai/journal/kubernetes-dns-udp-tcp-policy/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-dns-udp-tcp-policy/</guid><description>Diagnose some DNS queries fail: why TCP and UDP port 53 both matter. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Ping works but transfers stall: recognizing an MTU black hole</title><link>https://retrivium.ai/journal/network-mtu-blackhole-diagnostics/</link><guid isPermaLink="true">https://retrivium.ai/journal/network-mtu-blackhole-diagnostics/</guid><description>Diagnose ping works but transfers stall: recognizing an MTU black hole. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>New connections disappear: checking Linux conntrack pressure</title><link>https://retrivium.ai/journal/linux-conntrack-table-pressure/</link><guid isPermaLink="true">https://retrivium.ai/journal/linux-conntrack-table-pressure/</guid><description>Diagnose new connections disappear: checking Linux conntrack pressure. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Server returns the wrong certificate: SNI, SAN and the default virtual host</title><link>https://retrivium.ai/journal/tls-sni-san-wrong-certificate/</link><guid isPermaLink="true">https://retrivium.ai/journal/tls-sni-san-wrong-certificate/</guid><description>Diagnose server returns the wrong certificate: SNI, SAN and the default virtual host. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>HTTPS works on the host but not in the container: CA trust and certificate chains</title><link>https://retrivium.ai/journal/container-ca-chain-validation/</link><guid isPermaLink="true">https://retrivium.ai/journal/container-ca-chain-validation/</guid><description>Diagnose hTTPS works on the host but not in the container: CA trust and certificate chains. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Wrong time after restart: TLS errors and misleading log chronology</title><link>https://retrivium.ai/journal/clock-skew-tls-telemetry/</link><guid isPermaLink="true">https://retrivium.ai/journal/clock-skew-tls-telemetry/</guid><description>Diagnose wrong time after restart: TLS errors and misleading log chronology. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Prometheus relabel_configs vs metric_relabel_configs: where to filter data</title><link>https://retrivium.ai/journal/prometheus-target-vs-metric-relabeling/</link><guid isPermaLink="true">https://retrivium.ai/journal/prometheus-target-vs-metric-relabeling/</guid><description>Diagnose prometheus relabel_configs vs metric_relabel_configs: where to filter data. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Prometheus remote_write falls behind: WAL, queues and shards</title><link>https://retrivium.ai/journal/prometheus-remote-write-wal-backlog/</link><guid isPermaLink="true">https://retrivium.ai/journal/prometheus-remote-write-wal-backlog/</guid><description>Diagnose prometheus remote_write falls behind: WAL, queues and shards. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OpenTelemetry Collector drops data during backend outages: queues and limits</title><link>https://retrivium.ai/journal/otel-collector-backpressure/</link><guid isPermaLink="true">https://retrivium.ai/journal/otel-collector-backpressure/</guid><description>Diagnose openTelemetry Collector drops data during backend outages: queues and limits. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Telemetry never reaches the Collector: OTLP gRPC, HTTP and endpoints</title><link>https://retrivium.ai/journal/otlp-protocol-endpoint-mismatch/</link><guid isPermaLink="true">https://retrivium.ai/journal/otlp-protocol-endpoint-mismatch/</guid><description>Diagnose telemetry never reaches the Collector: OTLP gRPC, HTTP and endpoints. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A metric disappeared from the graph: staleness, up and zero values</title><link>https://retrivium.ai/journal/prometheus-scrape-staleness/</link><guid isPermaLink="true">https://retrivium.ai/journal/prometheus-scrape-staleness/</guid><description>Diagnose a metric disappeared from the graph: staleness, up and zero values. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Head vs tail sampling: why a trace splits across Collectors</title><link>https://retrivium.ai/journal/otel-head-tail-sampling-collector-routing/</link><guid isPermaLink="true">https://retrivium.ai/journal/otel-head-tail-sampling-collector-routing/</guid><description>Diagnose head vs tail sampling: why a trace splits across Collectors. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Alerts keep disappearing: for, pending and keep_firing_for</title><link>https://retrivium.ai/journal/prometheus-alert-pending-flapping/</link><guid isPermaLink="true">https://retrivium.ai/journal/prometheus-alert-pending-flapping/</guid><description>Diagnose alerts keep disappearing: for, pending and keep_firing_for. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Rate metrics jump after restart: counter resets and rate before sum</title><link>https://retrivium.ai/journal/prometheus-counter-reset-rate/</link><guid isPermaLink="true">https://retrivium.ai/journal/prometheus-counter-reset-rate/</guid><description>Diagnose rate metrics jump after restart: counter resets and rate before sum. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>kubectl logs --previous is not enough: Pod log rotation and collection</title><link>https://retrivium.ai/journal/kubernetes-log-rotation-restarts/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-log-rotation-restarts/</guid><description>Diagnose kubectl logs --previous is not enough: Pod log rotation and collection. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Deployment rollback starts the new image: the mutable tag problem</title><link>https://retrivium.ai/journal/kubernetes-rollback-mutable-image-tag/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-rollback-mutable-image-tag/</guid><description>Diagnose deployment rollback starts the new image: the mutable tag problem. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>The digest matches, but whom do you trust: verifying container image signatures</title><link>https://retrivium.ai/journal/artifact-signature-verification/</link><guid isPermaLink="true">https://retrivium.ai/journal/artifact-signature-verification/</guid><description>Diagnose the digest matches, but whom do you trust: verifying container image signatures. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>ConfigMap changed but the process sees old values: env, volumes and subPath</title><link>https://retrivium.ai/journal/kubernetes-configmap-update-reload/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-configmap-update-reload/</guid><description>Diagnose configMap changed but the process sees old values: env, volumes and subPath. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Secret updated but credentials are still old: file rotation and reloading</title><link>https://retrivium.ai/journal/kubernetes-secret-volume-rotation/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-secret-volume-rotation/</guid><description>Diagnose secret updated but credentials are still old: file rotation and reloading. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>ServiceAccount token expired: audiences and projected token rotation</title><link>https://retrivium.ai/journal/kubernetes-projected-serviceaccount-token/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-projected-serviceaccount-token/</guid><description>Diagnose serviceAccount token expired: audiences and projected token rotation. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU works as root but not in a rootless container: runtime and device permissions</title><link>https://retrivium.ai/journal/rootless-nvidia-cdi-permissions/</link><guid isPermaLink="true">https://retrivium.ai/journal/rootless-nvidia-cdi-permissions/</guid><description>Diagnose gPU works as root but not in a rootless container: runtime and device permissions. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Operation not permitted in a GPU container: checking seccomp</title><link>https://retrivium.ai/journal/container-seccomp-permission-denied/</link><guid isPermaLink="true">https://retrivium.ai/journal/container-seccomp-permission-denied/</guid><description>Diagnose operation not permitted in a GPU container: checking seccomp. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Pod stays unready after deny-all: init container network dependencies</title><link>https://retrivium.ai/journal/kubernetes-egress-networkpolicy-bootstrap/</link><guid isPermaLink="true">https://retrivium.ai/journal/kubernetes-egress-networkpolicy-bootstrap/</guid><description>Diagnose pod stays unready after deny-all: init container network dependencies. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>No matching manifest or exec format error: checking container image platforms</title><link>https://retrivium.ai/journal/container-image-platform-manifest-errors/</link><guid isPermaLink="true">https://retrivium.ai/journal/container-image-platform-manifest-errors/</guid><description>Diagnose no matching manifest or exec format error: checking container image platforms. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Read-only container will not start: where to allow temporary and cache writes</title><link>https://retrivium.ai/journal/read-only-container-writable-caches/</link><guid isPermaLink="true">https://retrivium.ai/journal/read-only-container-writable-caches/</guid><description>Diagnose read-only container will not start: where to allow temporary and cache writes. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU ECC: volatile and aggregate error counters</title><link>https://retrivium.ai/journal/gpu-ecc-volatile-aggregate/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-ecc-volatile-aggregate/</guid><description>Read GPU ECC counters with their type, location and reset history. A practical evidence table separates new increments, historical totals and unavailable fields.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU row remapping: pending state, remapped rows and spares</title><link>https://retrivium.ai/journal/gpu-row-remapping-state/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-row-remapping-state/</guid><description>Interpret GPU row-remapping counts, pending state and spare information without confusing them with retired pages or a universal hardware replacement threshold.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU Xid errors: reconstructing an incident timeline</title><link>https://retrivium.ai/journal/gpu-xid-timeline/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-xid-timeline/</guid><description>Build an actionable GPU Xid incident timeline from device identity, original logs and workload context, while separating observed sequence from a root-cause hypothesis.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Xid 79: evidence to retain when a GPU falls off the bus</title><link>https://retrivium.ai/journal/gpu-xid-79-event-record/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-xid-79-event-record/</guid><description>Investigate Xid 79 using PCIe context, original logs and recovery history. Preserve evidence before deciding which component needs further examination.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU clock reductions: reading simultaneous event reasons</title><link>https://retrivium.ai/journal/gpu-clock-event-reasons/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-clock-event-reasons/</guid><description>Decode simultaneous GPU clock event reasons, distinguish unsupported fields and correlate sampled constraints with the workload before changing operating limits.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU P-states and bursty inference requests</title><link>https://retrivium.ai/journal/gpu-pstate-burst-inference/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-pstate-burst-inference/</guid><description>Test bursty GPU inference with controlled idle gaps and aligned telemetry. Separate P-state observations from model startup, connection setup and engine warm-up.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>BAR1 and VRAM: why GPU memory readings differ</title><link>https://retrivium.ai/journal/gpu-bar1-vs-framebuffer/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-bar1-vs-framebuffer/</guid><description>Separate GPU BAR1 mappings from framebuffer allocations. Diagnose the failed operation with matching units and scope instead of adding two unrelated free-memory values.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU resets and telemetry counter epochs</title><link>https://retrivium.ai/journal/gpu-reset-counter-epochs/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-reset-counter-epochs/</guid><description>Design GPU counter epochs across driver changes, resets and missing samples. Validate rate calculations with saved fixtures rather than resetting a live device.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DCGM active diagnostics and passive health history</title><link>https://retrivium.ai/journal/dcgm-active-passive-evidence/</link><guid isPermaLink="true">https://retrivium.ai/journal/dcgm-active-passive-evidence/</guid><description>Reconcile DCGM active diagnostic results with passive health history using watched systems, retention, test scope and workload conditions instead of a single health label.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>DCGM diagnostic JSON: Pass, Fail, Skip and schema versions</title><link>https://retrivium.ai/journal/dcgm-diagnostic-json-status/</link><guid isPermaLink="true">https://retrivium.ai/journal/dcgm-diagnostic-json-status/</guid><description>Parse DCGM diagnostic JSON with pinned versions, retained raw output and separate pass, fail, skip and unknown states. Test the consumer with non-disruptive fixtures.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU PCIe links: negotiated speed, width and maximum capability</title><link>https://retrivium.ai/journal/gpu-pcie-negotiated-link/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-pcie-negotiated-link/</guid><description>Compare GPU PCIe capability with negotiated generation and width during a controlled transfer, keeping slot allocation and actual application bottlenecks separate.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>A GPU topology matrix: device proximity and actual measurements</title><link>https://retrivium.ai/journal/gpu-topology-distance-matrix/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-topology-distance-matrix/</guid><description>Read GPU topology as a device-path map, then test the relevant transfer. Preserve the legend, identities and route used instead of treating distance as bandwidth.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU peer access: checking each pair and direction</title><link>https://retrivium.ai/journal/gpu-peer-access-matrix/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-peer-access-matrix/</guid><description>Build a directed GPU peer-access matrix, then verify the route used by transfers and the inference engine. Keep topology, capability and measured behavior distinct.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>First touch and NUMA: locating GPU host buffers</title><link>https://retrivium.ai/journal/gpu-host-memory-first-touch/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-host-memory-first-touch/</guid><description>Measure GPU host-buffer NUMA placement with allocation timing, actual page observations and fixed transfers. CPU affinity alone does not establish where existing pages live.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Pinned GPU host memory: setting a page-locked buffer budget</title><link>https://retrivium.ai/journal/gpu-pinned-host-memory-budget/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-pinned-host-memory-budget/</guid><description>Budget pinned GPU host memory by live buffers, pinning overhead, host RAM pressure, NUMA placement and verified buffer reuse.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CUDA: verifying copy and compute overlap</title><link>https://retrivium.ai/journal/gpu-async-copy-overlap/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-async-copy-overlap/</guid><description>Verify CUDA copy and compute overlap through pinned memory, streams, dependencies, a timeline and comparison with a sequential control run.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>CUDA events and request time: different measurement boundaries</title><link>https://retrivium.ai/journal/gpu-cuda-events-wall-time/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-cuda-events-wall-time/</guid><description>Why CUDA events and HTTP request duration measure different intervals, with host and device boundaries, completion checks and a comparable timing record.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVLink errors: counter deltas and hardware generations</title><link>https://retrivium.ai/journal/gpu-nvlink-error-deltas/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-nvlink-error-deltas/</guid><description>Interpret NVLink errors using counter scope, GPU generation, observation deltas and resets, while distinguishing cumulative counts from BER fields.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Resizable BAR: inventorying resources without changing BIOS</title><link>https://retrivium.ai/journal/gpu-resizable-bar-discovery/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-resizable-bar-discovery/</guid><description>A read-only Resizable BAR inventory separating device capability, assigned PCIe resources and BAR1 usage without a universal BIOS prescription.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU, NVMe and NIC contention on a shared PCIe path</title><link>https://retrivium.ai/journal/gpu-shared-pcie-root-contention/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-shared-pcie-root-contention/</guid><description>Test GPU, NVMe and NIC PCIe contention with a path inventory, isolated and concurrent transfers, CPU controls and a bounded reproducible experiment.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVMe Percentage Used: SSD endurance and the metric boundary</title><link>https://retrivium.ai/journal/nvme-percentage-used/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvme-percentage-used/</guid><description>What NVMe Percentage Used means, why 100 does not imply immediate failure, and how to interpret endurance estimates with an SSD history.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVMe unsafe shutdowns and media errors mean different things</title><link>https://retrivium.ai/journal/nvme-errors-unsafe-shutdowns/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvme-errors-unsafe-shutdowns/</guid><description>Why NVMe unsafe shutdowns, media errors and error log entries need separate interpretation, with definitions, deltas, CLI versions and causal checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVMe temperature and variable model-loading time</title><link>https://retrivium.ai/journal/nvme-thermal-model-loading/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvme-thermal-model-loading/</guid><description>Investigate NVMe temperature and model load time using startup phases, cache controls, bounded read-only tests, thermal counters and causal limits.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Model caches and SSD endurance: downloads, host writes and NAND</title><link>https://retrivium.ai/journal/model-cache-ssd-write-amplification/</link><guid isPermaLink="true">https://retrivium.ai/journal/model-cache-ssd-write-amplification/</guid><description>Assess model cache writes without inventing write amplification, separating downloads, temporary files, NVMe host writes and physical NAND telemetry.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>LLM loading: read-latency tails beyond one SSD speed</title><link>https://retrivium.ai/journal/nvme-read-latency-model-load/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvme-read-latency-model-load/</guid><description>Investigate model-loading variance with declared fio read workloads, latency tails and an application timeline instead of predicting startup from sequential SSD bandwidth.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>fio buffered and direct reads measure different paths</title><link>https://retrivium.ai/journal/fio-buffered-direct-read/</link><guid isPermaLink="true">https://retrivium.ai/journal/fio-buffered-direct-read/</guid><description>Compare fio buffered and direct reads with explicit cache history, read-only safeguards and supported I/O settings. Keep filesystem and device boundaries visible.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OS page cache and cold model loading: what to record</title><link>https://retrivium.ai/journal/model-load-os-page-cache/</link><guid isPermaLink="true">https://retrivium.ai/journal/model-load-os-page-cache/</guid><description>Define cold and warm model-loading scenarios across artifact locality, OS page cache, process startup and device residency without clearing caches on shared production nodes.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>RAID1 for models: disk availability and version recovery</title><link>https://retrivium.ai/journal/raid1-model-backup-boundary/</link><guid isPermaLink="true">https://retrivium.ai/journal/raid1-model-backup-boundary/</guid><description>Separate RAID1 availability from model-version backup and restoration. Build a recovery map covering pinned artifacts, verification and tested readiness steps.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Host RAM ECC and EDAC: separate from GPU memory errors</title><link>https://retrivium.ai/journal/host-ram-ecc-edac/</link><guid isPermaLink="true">https://retrivium.ai/journal/host-ram-ecc-edac/</guid><description>Host-RAM ECC errors and GPU-memory errors belong to different devices and counters.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>PCIe AER near a GPU: severity, requester and chronology</title><link>https://retrivium.ai/journal/pcie-aer-gpu-evidence/</link><guid isPermaLink="true">https://retrivium.ai/journal/pcie-aer-gpu-evidence/</guid><description>Read a PCIe AER report near a GPU through severity, requester identity, and reporting topology.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU, CPU and server energy: where measurement boundaries lie</title><link>https://retrivium.ai/journal/gpu-board-server-power-boundary/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-board-server-power-boundary/</guid><description>GPU power, CPU-package energy, and server AC input use different measurement boundaries.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU power bursts and sparse sampling</title><link>https://retrivium.ai/journal/gpu-power-sampling-aliasing/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-power-sampling-aliasing/</guid><description>Sparse GPU-power snapshots cannot reconstruct every short workload burst. Polling frequency and a sensor&apos;s internal window are different properties.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU power caps: an energy and latency experiment</title><link>https://retrivium.ai/journal/gpu-power-cap-latency-frontier/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-power-cap-latency-frontier/</guid><description>Evaluate GPU power caps as an energy-and-latency experiment using approved, supported operating points.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Dual PSUs: accounting for A/B inputs and redundancy</title><link>https://retrivium.ai/journal/dual-psu-input-accounting/</link><guid isPermaLink="true">https://retrivium.ai/journal/dual-psu-input-accounting/</guid><description>With dual PSUs, account for server energy through non-overlapping A and B inputs while describing redundancy separately.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>UPS runtime for a GPU node: a recovery-time budget</title><link>https://retrivium.ai/journal/ups-runtime-recovery-budget/</link><guid isPermaLink="true">https://retrivium.ai/journal/ups-runtime-recovery-budget/</guid><description>Choose UPS runtime for a GPU node from the actual protected load and required action sequence.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Inlet, GPU and memory temperatures: different sensors</title><link>https://retrivium.ai/journal/gpu-inlet-device-temperature/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-inlet-device-temperature/</guid><description>Inlet-air, GPU, and GPU-memory temperatures measure different locations. One universal “server temperature” threshold cannot describe all of them.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Server fans: why speed percentages are not watts</title><link>https://retrivium.ai/journal/server-fan-energy-boundary/</link><guid isPermaLink="true">https://retrivium.ai/journal/server-fan-energy-boundary/</guid><description>A fan-speed percentage is not electrical power and does not determine whole-server cooling energy.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Aligning energy-meter readings with a GPU test window</title><link>https://retrivium.ai/journal/power-meter-time-alignment/</link><guid isPermaLink="true">https://retrivium.ai/journal/power-meter-time-alignment/</guid><description>Compare GPU-test energy only after aligning the workload window with meter boundaries.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU benchmarks: median, spread and trial order</title><link>https://retrivium.ai/journal/gpu-benchmark-median-dispersion/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-benchmark-median-dispersion/</guid><description>Diagnose gPU benchmarks: median, spread and trial order. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU benchmark confidence intervals: what counts as an observation</title><link>https://retrivium.ai/journal/gpu-benchmark-confidence-interval/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-benchmark-confidence-interval/</guid><description>Diagnose gPU benchmark confidence intervals: what counts as an observation. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU drivers: a controlled comparison of two versions</title><link>https://retrivium.ai/journal/gpu-driver-controlled-ab/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-driver-controlled-ab/</guid><description>Diagnose gPU drivers: a controlled comparison of two versions. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU VBIOS and InfoROM: different baseline fields</title><link>https://retrivium.ai/journal/gpu-inforom-vbios-baseline/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-inforom-vbios-baseline/</guid><description>Diagnose gPU VBIOS and InfoROM: different baseline fields. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OAM accelerator modules and their system boundary</title><link>https://retrivium.ai/journal/oam-gpu-module-system-boundary/</link><guid isPermaLink="true">https://retrivium.ai/journal/oam-gpu-module-system-boundary/</guid><description>Diagnose oAM accelerator modules and their system boundary. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Display-attached GPUs: the VRAM baseline before model loading</title><link>https://retrivium.ai/journal/display-attached-vram-baseline/</link><guid isPermaLink="true">https://retrivium.ai/journal/display-attached-vram-baseline/</guid><description>Diagnose display-attached GPUs: the VRAM baseline before model loading. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU-server RAM: equal capacity and different DIMM channel layouts</title><link>https://retrivium.ai/journal/gpu-host-ram-channel-population/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-host-ram-channel-population/</guid><description>Diagnose gPU-server RAM: equal capacity and different DIMM channel layouts. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>GPU N+1 capacity: measuring maintenance headroom on a workload</title><link>https://retrivium.ai/journal/gpu-n-plus-one-maintenance-capacity/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-n-plus-one-maintenance-capacity/</guid><description>Diagnose gPU N+1 capacity: measuring maintenance headroom on a workload. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>NVMe Available Spare is not filesystem free space</title><link>https://retrivium.ai/journal/nvme-spare-threshold-capacity/</link><guid isPermaLink="true">https://retrivium.ai/journal/nvme-spare-threshold-capacity/</guid><description>Diagnose nVMe Available Spare is not filesystem free space. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Heterogeneous GPUs in one report: aggregating benchmark results</title><link>https://retrivium.ai/journal/heterogeneous-gpu-benchmark-aggregation/</link><guid isPermaLink="true">https://retrivium.ai/journal/heterogeneous-gpu-benchmark-aggregation/</guid><description>Diagnose heterogeneous GPUs in one report: aggregating benchmark results. Evidence to collect, a worked operational example and recovery checks.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>AMD SMI in a mixed GPU fleet: units and metric support</title><link>https://retrivium.ai/journal/amd-smi-cross-vendor-telemetry/</link><guid isPermaLink="true">https://retrivium.ai/journal/amd-smi-cross-vendor-telemetry/</guid><description>Map AMD SMI telemetry into a mixed GPU fleet with explicit units, device scope and query status. Compare coverage before treating common labels as comparable measurements.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Intel xpu-smi: telemetry does not prove LLM-service readiness</title><link>https://retrivium.ai/journal/intel-xpu-telemetry-boundary/</link><guid isPermaLink="true">https://retrivium.ai/journal/intel-xpu-telemetry-boundary/</guid><description>Separate Intel xpu-smi discovery and version-dependent telemetry from compute-runtime checks, model loading and inference API readiness in a layered acceptance record.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate></item><item><title>How to rent out your GPU for LLM inference</title><link>https://retrivium.ai/journal/rent-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/rent-gpu/</guid><description>What GPU owners need before joining an LLM inference pool: hardware specifications, hosting conditions, a technical pilot and questions to settle before operation.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>What to do with GPU servers after a grant-funded project</title><link>https://retrivium.ai/journal/grant-hardware/</link><guid isPermaLink="true">https://retrivium.ai/journal/grant-hardware/</guid><description>How to assess idle grant-funded hardware: verify ownership and restrictions, protect research workloads and prepare a technical LLM inference scenario.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>GPU inference economics: what to calculate before joining a pool</title><link>https://retrivium.ai/journal/inference-economics/</link><guid isPermaLink="true">https://retrivium.ai/journal/inference-economics/</guid><description>Understand the operating costs of language-model GPUs and why token prices, server utilization and the equipment owner’s revenue are different measures.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>What is LLM inference, and why does it need your GPU?</title><link>https://retrivium.ai/journal/what-is-inference/</link><guid isPermaLink="true">https://retrivium.ai/journal/what-is-inference/</guid><description>A plain-language guide for hardware owners to LLM inference: how models handle requests, what tokens are and which part of the service a GPU provides.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>What hardware is suitable for an LLM inference pool?</title><link>https://retrivium.ai/journal/gpu-requirements/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-requirements/</guid><description>Five areas to assess in a GPU server: video memory, software compatibility, host resources, hosting conditions and predictable availability.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>VRAM for LLMs: why model size is only part of the calculation</title><link>https://retrivium.ai/journal/vram-and-models/</link><guid isPermaLink="true">https://retrivium.ai/journal/vram-and-models/</guid><description>How to estimate video memory for a language model: weights, KV cache, working buffers, context length and headroom for concurrent GPU requests.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Can NVIDIA RTX cards be used for LLM inference?</title><link>https://retrivium.ai/journal/rtx-for-inference/</link><guid isPermaLink="true">https://retrivium.ai/journal/rtx-for-inference/</guid><description>What RTX workstation owners should check before offering inference capacity: memory, sustained load, site conditions and maintenance access.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>How to prepare a GPU server for a technical pilot</title><link>https://retrivium.ai/journal/server-preparation/</link><guid isPermaLink="true">https://retrivium.ai/journal/server-preparation/</guid><description>A practical preparation sequence for an LLM inference pilot: inventory, backups, agreed access, a test environment and restoration of the original setup.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>How a GPU pool connects to OpenRouter</title><link>https://retrivium.ai/journal/openrouter-provider/</link><guid isPermaLink="true">https://retrivium.ai/journal/openrouter-provider/</guid><description>OpenRouter’s role in selling LLM inference, the difference between a hardware owner and an API provider, and the onboarding stages and demand limitations.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>How laboratories can assess spare GPU capacity</title><link>https://retrivium.ai/journal/lab-idle-capacity/</link><guid isPermaLink="true">https://retrivium.ai/journal/lab-idle-capacity/</guid><description>A practical way to describe underused laboratory servers: workload schedules, reserves, operating costs and boundaries for external use.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Grant-funded equipment: a checklist before external workloads</title><link>https://retrivium.ai/journal/grant-checklist/</link><guid isPermaLink="true">https://retrivium.ai/journal/grant-checklist/</guid><description>Questions for equipment owners and grant coordinators before connecting GPUs to an external service: authority, approvals, access, costs and usage accounting.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>LLM inference versus training: what GPU owners should know</title><link>https://retrivium.ai/journal/inference-vs-training/</link><guid isPermaLink="true">https://retrivium.ai/journal/inference-vs-training/</guid><description>How language-model operations differ from training and fine-tuning: workload profiles, memory, scheduling and service requirements for GPU owners.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Multiple GPUs in a pool: one service or one large model?</title><link>https://retrivium.ai/journal/multi-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/multi-gpu/</guid><description>Why a distributed GPU pool is not one graphics card: independent replicas, model distribution, memory limits and the role of connections between nodes.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>GPU networking and availability: beyond internet speed</title><link>https://retrivium.ai/journal/network-and-uptime/</link><guid isPermaLink="true">https://retrivium.ai/journal/network-and-uptime/</guid><description>How to assess an LLM inference server connection: network stability, latency, recovery after interruptions, operating schedules and responsibility boundaries.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Equipment security when joining a GPU pool</title><link>https://retrivium.ai/journal/hardware-security/</link><guid isPermaLink="true">https://retrivium.ai/journal/hardware-security/</guid><description>Access boundaries GPU owners should discuss with operators: separate environments, permissions, data, logs, updates and revocation after a pilot.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Power and cooling: the overlooked conditions of GPU operation</title><link>https://retrivium.ai/journal/power-and-cooling/</link><guid isPermaLink="true">https://retrivium.ai/journal/power-and-cooling/</guid><description>What sustained GPU server operation requires: measured whole-machine consumption, room cooling, site limitations and responsibility for maintenance.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>GPU inference pilot: what to check before an operating agreement</title><link>https://retrivium.ai/journal/pilot-checklist/</link><guid isPermaLink="true">https://retrivium.ai/journal/pilot-checklist/</guid><description>A technical pilot plan for GPU owners and operators: objectives, model, request profile, success criteria, expenses, recovery and the final decision.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Choosing an LLM for your server: start with its model and terms</title><link>https://retrivium.ai/journal/model-licenses/</link><guid isPermaLink="true">https://retrivium.ai/journal/model-licenses/</guid><description>How to prepare a language-model choice for external inference: version, model card, license, compatibility, quality checks and change tracking.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>What should a report on your GPU’s operation contain?</title><link>https://retrivium.ai/journal/capacity-reporting/</link><guid isPermaLink="true">https://retrivium.ai/journal/capacity-reporting/</guid><description>Metrics equipment owners should agree with operators: node availability, successful requests, tokens, expenses, interruptions and payment reconciliation.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>GPU rental or revenue sharing: which terms should you discuss?</title><link>https://retrivium.ai/journal/revenue-share/</link><guid isPermaLink="true">https://retrivium.ai/journal/revenue-share/</guid><description>How fixed GPU rental, availability payments and inference revenue sharing differ, with questions about costs, demand risk, reporting and ending cooperation.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Mining rigs for LLMs: which components can be reused?</title><link>https://retrivium.ai/journal/mining-gpus-for-inference/</link><guid isPermaLink="true">https://retrivium.ai/journal/mining-gpus-for-inference/</guid><description>How owners of former mining rigs can assess LLM inference: check GPUs, host hardware, cooling and a pilot scenario before buying a replacement fleet.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Idle render farms: assessing a second GPU workload</title><link>https://retrivium.ai/journal/render-farm-idle-gpus/</link><guid isPermaLink="true">https://retrivium.ai/journal/render-farm-idle-gpus/</guid><description>How studios can evaluate LLM inference on underused render farms while separating schedules, resources, environments and obligations to their own projects.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Workstation GPUs at night: when scheduled operation makes sense</title><link>https://retrivium.ai/journal/studio-workstations-night/</link><guid isPermaLink="true">https://retrivium.ai/journal/studio-workstations-night/</guid><description>How to offer a studio workstation GPU outside working hours: assess the available window, model startup, workload shutdown and readiness for the next workday.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Spare game-studio GPUs: separating resources for inference</title><link>https://retrivium.ai/journal/game-dev-gpu-capacity/</link><guid isPermaLink="true">https://retrivium.ai/journal/game-dev-gpu-capacity/</guid><description>How game studios can evaluate external GPU workloads without disrupting editors, testing or builds: select machines, schedules and production-restoration criteria.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>GPU integrators and suppliers: offering a fleet for a pilot</title><link>https://retrivium.ai/journal/gpu-reseller-partnership/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-reseller-partnership/</guid><description>How server suppliers and GPU integrators can start a technical partnership with an inference operator: configuration, demonstration nodes, test criteria and roles.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Keep your GPU on site or move it to a data center?</title><link>https://retrivium.ai/journal/colocation-vs-on-premise/</link><guid isPermaLink="true">https://retrivium.ai/journal/colocation-vs-on-premise/</guid><description>How to compare GPU operation at your own site and in a data center: total costs, availability, maintenance, relocation and inference-service requirements.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Used GPUs: which checks are needed before a pilot?</title><link>https://retrivium.ai/journal/used-gpu-health-check/</link><guid isPermaLink="true">https://retrivium.ai/journal/used-gpu-health-check/</guid><description>How to prepare used GPUs for inference assessment: operating history, inventory, diagnostics, reproducible testing and a clear final equipment record.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Mixed GPU fleets: how to offer them to an inference operator</title><link>https://retrivium.ai/journal/mixed-gpu-fleet/</link><guid isPermaLink="true">https://retrivium.ai/journal/mixed-gpu-fleet/</guid><description>How to describe a heterogeneous GPU fleet for LLM inference: group by memory and compatibility, distinguish independent nodes and onboard equipment gradually.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Reserve GPU servers: useful workloads without losing the reserve</title><link>https://retrivium.ai/journal/reserve-gpu-capacity/</link><guid isPermaLink="true">https://retrivium.ai/journal/reserve-gpu-capacity/</guid><description>How reserve GPU server owners can assess external work: define the reserve’s purpose, return time, internal-work priority and a tested switching procedure.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Joining a GPU pool: the decisions at each stage</title><link>https://retrivium.ai/journal/gpu-pool-onboarding/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-pool-onboarding/</guid><description>An equipment owner’s roadmap from first message to GPU operation: resource specifications, technical assessment, pilot, commercial terms and production onboarding.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>GPUs free for a few months: offering temporary capacity</title><link>https://retrivium.ai/journal/seasonal-gpu-capacity/</link><guid isPermaLink="true">https://retrivium.ai/journal/seasonal-gpu-capacity/</guid><description>How owners of temporarily idle GPUs can assess a limited operating period: start and return dates, preparation, useful time, costs and extension decisions.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Who can reach your GPU server? Physical support for remote nodes</title><link>https://retrivium.ai/journal/remote-hands-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/remote-hands-gpu/</guid><description>How to agree on remote-site GPU maintenance: contacts, allowed actions, diagnostics, spare components, work confirmation and costs.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>I have one GPU: how do I start an onboarding conversation?</title><link>https://retrivium.ai/journal/single-gpu-owner/</link><guid isPermaLink="true">https://retrivium.ai/journal/single-gpu-owner/</guid><description>A first-contact guide for single-GPU owners: important specifications, what can remain unknown and how to test inference without expanding your hardware.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Finding spare GPUs inside a company and preparing a proposal</title><link>https://retrivium.ai/journal/corporate-gpu-inventory/</link><guid isPermaLink="true">https://retrivium.ai/journal/corporate-gpu-inventory/</guid><description>How to inventory a company GPU fleet in practice: ownership, purpose, actual availability, restrictions and selecting hardware for an inference pilot.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Returning your GPU to your own work after leaving a pool</title><link>https://retrivium.ai/journal/gpu-exit-plan/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-exit-plan/</guid><description>What GPU owners should agree before cooperation ends: notice, workload removal, environment restoration, access revocation, files and final reconciliation.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Prefill and decode: the work your GPU performs during inference</title><link>https://retrivium.ai/journal/llm-prefill-decode/</link><guid isPermaLink="true">https://retrivium.ai/journal/llm-prefill-decode/</guid><description>Why long-input processing and response generation stress a server differently, and how GPU owners can choose a useful technical-pilot workload.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Continuous batching: why concurrent requests change GPU value</title><link>https://retrivium.ai/journal/continuous-batching/</link><guid isPermaLink="true">https://retrivium.ai/journal/continuous-batching/</guid><description>How to test shared LLM request execution on a server, and why equipment owners need queue, quality and latency measures alongside GPU utilization.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Prefix caching: when repeated context helps a GPU pool</title><link>https://retrivium.ai/journal/prefix-caching/</link><guid isPermaLink="true">https://retrivium.ai/journal/prefix-caching/</guid><description>How to evaluate reuse of a shared LLM request prefix, and why selecting a GPU requires separate cold-cache and warm-cache tests.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Long-context LLMs: testing a server for document workloads</title><link>https://retrivium.ai/journal/long-context-capacity/</link><guid isPermaLink="true">https://retrivium.ai/journal/long-context-capacity/</guid><description>How GPU owners can assess long-document serving: input profiles, quality checks, latency, mixed traffic and the model’s practical operating limits.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>KV cache and GPU economics: accounting for active-request memory</title><link>https://retrivium.ai/journal/kv-cache-economics/</link><guid isPermaLink="true">https://retrivium.ai/journal/kv-cache-economics/</guid><description>How request memory affects useful GPU server capacity: context profiles, resource occupancy time, constraint costs and comparisons between configurations.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>LLM quantization: checking quality before choosing a GPU</title><link>https://retrivium.ai/journal/quantization-quality/</link><guid isPermaLink="true">https://retrivium.ai/journal/quantization-quality/</guid><description>How to compare original and quantized models on a specific GPU: tasks, response formats, memory, speed and criteria for a technical decision.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>A GPU inference benchmark you can trust</title><link>https://retrivium.ai/journal/inference-benchmark-method/</link><guid isPermaLink="true">https://retrivium.ai/journal/inference-benchmark-method/</guid><description>How to build a reproducible GPU test protocol: versions, request profiles, warmup, multiple load levels and reporting for owners and infrastructure partners.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Throughput and latency: choosing a GPU operating point</title><link>https://retrivium.ai/journal/throughput-latency-tradeoff/</link><guid isPermaLink="true">https://retrivium.ai/journal/throughput-latency-tradeoff/</guid><description>Why maximum token output may not deliver the best user experience, and how to compare GPU server configurations through throughput and latency together.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Validating model demand before expanding a GPU pool</title><link>https://retrivium.ai/journal/model-demand-validation/</link><guid isPermaLink="true">https://retrivium.ai/journal/model-demand-validation/</guid><description>How to separate model popularity from confirmed service demand: choose a task, interview users, test an endpoint, define quality and decide whether to expand.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Routing and fallback: which role could your GPU serve?</title><link>https://retrivium.ai/journal/inference-routing-fallback/</link><guid isPermaLink="true">https://retrivium.ai/journal/inference-routing-fallback/</guid><description>How future GPU pools can distribute node requests, what to test during failures and why a reserve machine differs from a continuously loaded replica.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>GPU monitoring without excess charts: five observation levels</title><link>https://retrivium.ai/journal/gpu-monitoring-scorecard/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-monitoring-scorecard/</guid><description>Signals GPU owners and inference operators need: device condition, resources, service readiness, useful results and actions when behavior changes.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Reproducible inference stacks: preserving a GPU pilot’s result</title><link>https://retrivium.ai/journal/software-stack-reproducibility/</link><guid isPermaLink="true">https://retrivium.ai/journal/software-stack-reproducibility/</guid><description>What to record in a GPU server environment to repeat technical checks: weights, driver, engine, launch settings, test inputs and rollback procedures.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Planning a GPU pool: when is the next server actually needed?</title><link>https://retrivium.ai/journal/inference-capacity-planning/</link><guid isPermaLink="true">https://retrivium.ai/journal/inference-capacity-planning/</guid><description>How observations can guide LLM inference expansion: workload profiles, operating capacity, reserve, site limitations and criteria for the next investment.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Embeddings and rerankers: other tasks for an idle GPU</title><link>https://retrivium.ai/journal/embeddings-rerankers-gpu/</link><guid isPermaLink="true">https://retrivium.ai/journal/embeddings-rerankers-gpu/</guid><description>Why useful AI workloads extend beyond text generation: testing embedding and reranking models on existing GPUs and choosing the right unit of useful output.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Updating an LLM on a GPU: testing a new version with a small rollout</title><link>https://retrivium.ai/journal/model-update-canary/</link><guid isPermaLink="true">https://retrivium.ai/journal/model-update-canary/</guid><description>How to change models without changing an entire pool at once: record versions, compare quality, limit the test and establish rollback in advance.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Funding a GPU pool: from an idea to a defined project</title><link>https://retrivium.ai/journal/fund-gpu-pool/</link><guid isPermaLink="true">https://retrivium.ai/journal/fund-gpu-pool/</guid><description>What to discuss before financing GPUs and operations: use of funds, technical pilots, equipment ownership, reporting and decisions about pool expansion.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Working capital for LLM inference: what happens after buying GPUs?</title><link>https://retrivium.ai/journal/working-capital-inference/</link><guid isPermaLink="true">https://retrivium.ai/journal/working-capital-inference/</guid><description>Why GPU pools need operating funding: payment schedules, model deployment, delayed receipts and an operational reserve for an agreed period.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>How to assess a GPU pool project before funding it</title><link>https://retrivium.ai/journal/gpu-project-due-diligence/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-project-due-diligence/</guid><description>Evidence to request before financing GPUs: infrastructure specifications, a reproducible pilot, budget, sales-channel status and operational responsibility.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Milestone GPU funding: paying for the next verifiable step</title><link>https://retrivium.ai/journal/milestone-funding/</link><guid isPermaLink="true">https://retrivium.ai/journal/milestone-funding/</guid><description>How to divide GPU pool funding into preparation, pilot, procurement and operation, with defined outcomes, budgets and decisions at every stage.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Buying or renting GPUs: what to compare before funding</title><link>https://retrivium.ai/journal/gpu-purchase-vs-rental/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-purchase-vs-rental/</guid><description>How to compare buying and renting GPUs for one inference scenario: total expenses, task duration, flexibility, acceptance and project exit conditions.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Inference unit economics: choosing the unit a funding partner needs</title><link>https://retrivium.ai/journal/inference-unit-economics/</link><guid isPermaLink="true">https://retrivium.ai/journal/inference-unit-economics/</guid><description>Choose a useful unit for GPU-pool economics: successful requests, a million tokens or a service workload. Define costs and compare like periods.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>GPU-pool budgeting: allocating funds between hardware and operations</title><link>https://retrivium.ai/journal/gpu-budget-allocation/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-budget-allocation/</guid><description>Build a concrete GPU-project budget covering hardware, preparation, hosting, operations, shared tasks and contingency without universal spending ratios.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Reporting to a GPU-pool funding partner</title><link>https://retrivium.ai/journal/gpu-funding-reporting/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-funding-reporting/</guid><description>What a GPU-funding report should cover: funds, equipment status, technical results, budget variances and the basis for subsequent spending decisions.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Risks to discuss before funding GPU inference</title><link>https://retrivium.ai/journal/gpu-funding-risks/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-funding-risks/</guid><description>Connect GPU-project risks with decisions: uncertain demand, technical fit, launch timing, operating expense and dependence on external distribution channels.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Procuring GPUs for a pool: specification and acceptance before scaling</title><link>https://retrivium.ai/journal/procurement-before-scale/</link><guid isPermaLink="true">https://retrivium.ai/journal/procurement-before-scale/</guid><description>Prepare GPU procurement from pilot results, a complete specification, delivery conditions, acceptance criteria and the budget for putting hardware to work.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Demand before GPUs: evidence to gather before purchasing</title><link>https://retrivium.ai/journal/gpu-demand-before-capex/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-demand-before-capex/</guid><description>Validate a GPU pool’s commercial hypothesis before expansion: user scenarios, service requirements, pilot measurements and evidence for the next funding stage.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Questions to ask a GPU-pool team at the first meeting</title><link>https://retrivium.ai/journal/financial-partner-questions/</link><guid isPermaLink="true">https://retrivium.ai/journal/financial-partner-questions/</guid><description>Questions for an initial GPU-funding conversation: current stage, purpose of funds, available resources, results, expenses, responsibility and next decisions.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Discussing future compute demand and capacity reservations</title><link>https://retrivium.ai/journal/compute-offtake/</link><guid isPermaLink="true">https://retrivium.ai/journal/compute-offtake/</guid><description>Use preliminary inference-demand discussions to plan GPUs: workload, resources, timing, payment and the distinction between interest and confirmed commitments.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>The GPU asset lifecycle: planning beyond the purchase</title><link>https://retrivium.ai/journal/gpu-asset-lifecycle/</link><guid isPermaLink="true">https://retrivium.ai/journal/gpu-asset-lifecycle/</guid><description>Plan GPU acceptance, condition monitoring, maintenance, changing workloads and the end of participation in a compute pool as parts of one asset lifecycle.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Growing a GPU pool when additional machines are actually needed</title><link>https://retrivium.ai/journal/responsible-pool-growth/</link><guid isPermaLink="true">https://retrivium.ai/journal/responsible-pool-growth/</guid><description>What justifies GPU-pool growth: a measured constraint, defined need, operating readiness and budget. Avoid treating the card count as the result.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Finding an operating budget for grant-funded GPUs after a project</title><link>https://retrivium.ai/journal/grant-gpu-operating-budget/</link><guid isPermaLink="true">https://retrivium.ai/journal/grant-gpu-operating-budget/</guid><description>A server is already purchased, but keeping it working needs funding. Prepare power, support and pilot expenses a laboratory can discuss with a partner.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Cloud credits or owned GPUs: what can be offered to an operator?</title><link>https://retrivium.ai/journal/grant-cloud-credits/</link><guid isPermaLink="true">https://retrivium.ai/journal/grant-cloud-credits/</guid><description>Cloud credits and grant-funded servers are different resources. Describe the support, check programme restrictions and identify a permitted collaboration scenario.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Preparing a laboratory proposal for GPU cooperation</title><link>https://retrivium.ai/journal/research-gpu-partner-proposal/</link><guid isPermaLink="true">https://retrivium.ai/journal/research-gpu-partner-proposal/</guid><description>A short GPU-partnership proposal for management and a technical partner: available resources, pilot objective, constraints, expenses and verifiable results.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Funding a research compute window</title><link>https://retrivium.ai/journal/research-compute-sponsorship/</link><guid isPermaLink="true">https://retrivium.ai/journal/research-compute-sponsorship/</guid><description>Support a defined GPU research window by specifying the task, operating budget, responsible people and results a funding partner can verify.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Shared GPU resources: agreeing laboratory, operator and partner roles</title><link>https://retrivium.ai/journal/research-pool-governance/</link><guid isPermaLink="true">https://retrivium.ai/journal/research-pool-governance/</guid><description>A responsibility matrix for a joint GPU pilot: equipment, funding, configuration changes, acceptance, technical stops and decisions to continue.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate></item></channel></rss>