<?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[Why the same machine gives different numbers each run]]></title><description><![CDATA[<p dir="auto">If you run the same benchmark twice and get different answers, nothing is broken.</p>
<p dir="auto">The usual causes, roughly in order:</p>
<ol>
<li><strong>Heat.</strong> Laptops especially will slow themselves down after sustained load. A second run often lands lower than the first purely for this reason.</li>
<li><strong>Other software.</strong> A browser with many tabs, or anything using the GPU, competes for exactly the resource that limits generation speed.</li>
<li><strong>Cold vs warm model.</strong> The first run after loading includes work that later runs skip.</li>
</ol>
<p dir="auto">This is why comparisons should be run <strong>alternating</strong> — A, B, A, B — rather than all of A then all of B. Otherwise you're partly measuring how warm the machine got.</p>
<p dir="auto">If your numbers swing by more than about 20% with nothing else running, that's worth posting about.</p>
]]></description><link>https://community.lizard-llm.qendryx.com/topic/13/why-the-same-machine-gives-different-numbers-each-run</link><generator>RSS for Node</generator><lastBuildDate>Mon, 24 Aug 2026 03:19:08 GMT</lastBuildDate><atom:link href="https://community.lizard-llm.qendryx.com/topic/13.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 18 Jul 2026 10:51:00 GMT</pubDate><ttl>60</ttl></channel></rss>