<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Lizard inference engineering: Stop oversized models from thrashing]]></title><description><![CDATA[<p dir="auto"><strong>Inference Engineering · Day 2 · Evening</strong></p>
<p dir="auto">A model that almost fits can create the worst failure mode: it runs, but it thrashes.</p>
<p dir="auto">On a tight GPU budget, repeatedly evicting and re-uploading layers can reduce decode to a crawl. A single “GPU or CPU” decision is too coarse.</p>
<p dir="auto">Lizard plans prefill and decode independently. It can keep GPU-assisted prompt processing while moving decode to a bounded, stable path when full residency is unsafe.</p>
<p dir="auto">The engineering lesson: split the phases before you split the blame.</p>
<p dir="auto"><strong>Engineering fact:</strong> When a model exceeds the usable GPU weight budget, Lizard can keep GPU-assisted prompt processing and use bounded hybrid decode instead of repeated eviction.</p>
<p dir="auto"><a href="https://lizard-llm.qendryx.com/docs.html#lizard-native" rel="nofollow ugc">Read the relevant Lizard page</a></p>
<p dir="auto">#VRAM #LLMInference #GPUPerformance #LizardNative #LocalAI</p>
<p dir="auto">&lt;!-- lizard-marketing-slot:day-02-pm --&gt;</p>
]]></description><link>https://community.lizard-llm.qendryx.com/topic/38/lizard-inference-engineering-stop-oversized-models-from-thrashing</link><generator>RSS for Node</generator><lastBuildDate>Mon, 24 Aug 2026 01:38:30 GMT</lastBuildDate><atom:link href="https://community.lizard-llm.qendryx.com/topic/38.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 25 Jul 2026 11:00:06 GMT</pubDate><ttl>60</ttl></channel></rss>