<?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: Integrated GPUs need a shared-memory plan]]></title><description><![CDATA[<p dir="auto"><strong>Inference Engineering · Day 19 · Morning</strong></p>
<p dir="auto"><img src="https://lizard-llm.qendryx.com/diagrams/lizard-native-stack.png" alt="Integrated GPUs need a shared-memory plan editorial visual — lizard-llm.qendryx.com" class=" img-fluid img-markdown" /></p>
<p dir="auto">Integrated GPUs change the memory question, not just the adapter name.</p>
<p dir="auto">On a shared-memory system, the model, KV cache, application, compositor, and CPU all compete inside one physical budget. Lizard distinguishes this configuration when planning fit and execution rather than treating advertised graphics memory as an isolated pool.</p>
<p dir="auto">The useful number is the memory currently available to the whole workload.</p>
<p dir="auto">How does your runtime budget an iGPU while the desktop and other applications are active?</p>
<p dir="auto"><strong>Engineering fact:</strong> Lizard's hardware planning distinguishes integrated-memory and discrete-memory systems so model fit and execution choices can account for shared RAM instead of treating every GPU like a separate VRAM device.</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">#LizardNative #LizardLLM #LocalAI #GGUF #InferenceEngineering</p>
<p dir="auto">&lt;!-- lizard-marketing-slot:day-19-am --&gt;</p>
]]></description><link>https://community.lizard-llm.qendryx.com/topic/77/lizard-inference-engineering-integrated-gpus-need-a-shared-memory-plan</link><generator>RSS for Node</generator><lastBuildDate>Mon, 24 Aug 2026 01:36:29 GMT</lastBuildDate><atom:link href="https://community.lizard-llm.qendryx.com/topic/77.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 11 Aug 2026 01:00:07 GMT</pubDate><ttl>60</ttl></channel></rss>