<?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: Context length belongs in lived performance history]]></title><description><![CDATA[<p dir="auto"><strong>Inference Engineering · Day 27 · Evening</strong></p>
<p dir="auto"><img src="https://lizard-llm.qendryx.com/diagrams/lizard-native-stack.png" alt="Context length belongs in lived performance history editorial visual — lizard-llm.qendryx.com" class=" img-fluid img-markdown" /></p>
<p dir="auto">Conversation length changes the workload before decode begins.</p>
<p dir="auto">As context grows, prompt processing and KV-cache pressure can change even when the model and hardware stay the same. Lizard records context tokens and includes a context bucket in comparable turn history.</p>
<p dir="auto">That keeps a long-conversation slowdown from looking like an unexplained engine regression.</p>
<p dir="auto">At what context length does your current local model begin to feel different?</p>
<p dir="auto"><strong>Engineering fact:</strong> Lizard records context tokens and groups native turn history into context buckets because longer conversations change prefill and KV-cache costs.</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-27-pm --&gt;</p>
]]></description><link>https://community.lizard-llm.qendryx.com/topic/94/lizard-inference-engineering-context-length-belongs-in-lived-performance-history</link><generator>RSS for Node</generator><lastBuildDate>Mon, 24 Aug 2026 00:47:18 GMT</lastBuildDate><atom:link href="https://community.lizard-llm.qendryx.com/topic/94.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 19 Aug 2026 11:00:13 GMT</pubDate><ttl>60</ttl></channel></rss>