<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet type="text/css" href="https://techfuelhq.com/feed.css"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>TechFuel HQ</title><link>https://techfuelhq.com/</link><description>Recent content on TechFuel HQ</description><generator>Hugo</generator><language>en-us</language><managingEditor>contact@techfuelhq.com (LK Wood IV)</managingEditor><lastBuildDate>Wed, 18 Nov 2026 01:02:20 +0000</lastBuildDate><atom:link href="https://techfuelhq.com/index.xml" rel="self" type="application/rss+xml"/><atom:link href="https://pubsubhubbub.appspot.com/" rel="hub"/><item><title>When Will RAM Prices Go Down?</title><link>https://techfuelhq.com/articles/when-will-ram-prices-go-down/</link><pubDate>Wed, 18 Nov 2026 01:02:20 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/when-will-ram-prices-go-down/</guid><atom:updated>2026-11-18T01:02:20Z</atom:updated><description>&lt;p>Not in 2026, according to the companies that make memory and the firms that track it, and none of their forecasts published since July expects a fall in 2027. None of them names a month. I don&amp;rsquo;t forecast here: every timing statement below belongs to a named source, with its date, and the sources are listed at the bottom of the page.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>2026:&lt;/strong> TrendForce (November 11, 2026) forecasts PC DRAM contract prices up 13–18% in the fourth quarter, a slower climb than the quarter before.&lt;/li>
&lt;li>&lt;strong>2027:&lt;/strong> TrendForce (July 30) expects the DRAM supply-demand gap to widen. Micron (September 30) expects memory and storage conditions &amp;ldquo;much tighter&amp;rdquo; in calendar 2027 and 2028 than in 2026. TeamGroup&amp;rsquo;s chief executive, Gerry Chen, sees &amp;ldquo;no downward price trend whatsoever&amp;rdquo; next year (Fortune, November 10, reporting his November 2 earnings call as BigGo Finance described it).&lt;/li>
&lt;li>&lt;strong>2028 and after:&lt;/strong> TrendForce expects substantial new-fab output only in 2028, and Chen sees supply and demand balancing in the second half of 2028 at the earliest. SK hynix (October 28) expects demand to exceed supply through 2030.&lt;/li>
&lt;/ul>
&lt;h2 id="where-ddr5-prices-are-today">Where DDR5 prices are today&lt;/h2>
&lt;p>My own number is the &lt;a href="https://techfuelhq.com/data/ddr5-clock/">DDR5 Clock&lt;/a>, a fixed basket of 32GB DDR5 kits read from Newegg&amp;rsquo;s affiliate catalogue. The figure below is printed from the price files when the site builds, so it matches the Clock.&lt;/p>
&lt;div class="callout ddr5-clock-latest">
&lt;p class="callout-label">Latest DDR5 Clock reading&lt;/p>
&lt;p>&lt;strong>$20.94 per GB&lt;/strong> on &lt;time datetime="2026-11-17">November 17, 2026&lt;/time> (UTC). That is the median price per gigabyte across the 8 of 12 tracked 32GB (2x16GB) DDR5 kits that had a qualifying in-stock listing in Newegg’s affiliate catalogue that day. The median kit was $669.99; the cheapest kit worked out to $20.00 per GB and the dearest to $22.19.&lt;/p>
&lt;p>This is the first reading under the current method, which started on November 17, 2026. &lt;a href="https://techfuelhq.com/data/ddr5-clock/">Open the DDR5 Clock&lt;/a> for its status and citation, or the &lt;a href="https://techfuelhq.com/data/ddr5-clock/2026-11-17/">frozen page for November 17, 2026&lt;/a>.&lt;/p>
&lt;/div>
&lt;p>The method changed on November 17, 2026: from that date the &lt;a href="https://techfuelhq.com/data/ram-price-index/">DDR5 RAM price index&lt;/a> reads Newegg&amp;rsquo;s affiliate catalogue, which names no seller. Earlier rows came from Newegg&amp;rsquo;s product pages or from a list of named US retailers, under different rules, so I don&amp;rsquo;t calculate a change across that boundary. The Clock reports a change only between two readings taken the same way, and on the day I wrote this there was one, so my own data can&amp;rsquo;t yet show a direction. Once a kit has enough daily observations, &lt;a href="https://techfuelhq.com/data/deal-or-mirage/">Deal or Mirage&lt;/a> labels its price against its own history. For an older snapshot by capacity, &lt;a href="https://techfuelhq.com/articles/ddr5-ram-prices-2026/">my August price check&lt;/a> has 16GB to 128GB kits as they stood on August 1, 2026.&lt;/p>
&lt;h2 id="why-ram-got-expensive-in-short">Why RAM got expensive, in short&lt;/h2>
&lt;p>TrendForce (September 22) wrote that a surge in AI-driven server DRAM orders limited suppliers&amp;rsquo; allocations for PC and consumer products, and its September 30 release says suppliers still prioritise advanced-process capacity for high-performance server products, including high-bandwidth memory (HBM). Its July 30 release adds a wrinkle: HBM takes significantly more wafer input than conventional DRAM, so more wafer starts don&amp;rsquo;t turn into proportionally more memory. Micron went further: on December 3, 2025 it announced its exit from the Crucial consumer business, with consumer shipments continuing only until the end of February 2026. The full explanation, with the price history, is in &lt;a href="https://techfuelhq.com/articles/ram-ssd-price-crisis-2026/">why RAM and SSD prices rose in 2026&lt;/a>.&lt;/p>
&lt;h2 id="what-would-have-to-change-for-prices-to-fall">What would have to change for prices to fall&lt;/h2>
&lt;p>Four things, going by the sources. In none of them did I find a source describing a quick change.&lt;/p>
&lt;h3 id="new-fabs-on-their-owners-dates">New fabs, on their owners&amp;rsquo; dates&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Micron&lt;/strong> (September 30, 2026): its ID1 fab in Idaho &amp;ldquo;is on track to commence wafer output in mid-calendar 2027,&amp;rdquo; and ID2 in late calendar 2028. A DRAM fab expansion in Japan is due to give initial output in late calendar 2028 &amp;ldquo;to support technology node transitions,&amp;rdquo; the Tongluo facility in Taiwan meaningful shipments in mid-calendar 2027, and the first New York fab initial wafer output in 2030. Most of Micron&amp;rsquo;s added construction spending is aimed at cleanroom space for &amp;ldquo;late calendar 2028 and beyond.&amp;rdquo;&lt;/li>
&lt;li>&lt;strong>SK hynix&lt;/strong> (October 28, 2026): it will ramp M15X to maximum capacity by the end of 2026 to make more HBM4, and expects Yongin Phase 1 to enter full-scale operation in 2027.&lt;/li>
&lt;li>&lt;strong>TrendForce&lt;/strong> (July 30, 2026): construction schedules, equipment installation and raw-material preparation will delay meaningful ramp-ups of the new capacity planned for 2027 until the second half of that year, and &amp;ldquo;substantial output contributions are not expected to materialize until 2028.&amp;rdquo;&lt;/li>
&lt;/ul>
&lt;p>None of these statements says how much of the new output will go to desktop memory.&lt;/p>
&lt;h3 id="the-split-between-server-and-pc-memory">The split between server and PC memory&lt;/h3>
&lt;p>TrendForce wrote on September 30 that PC DRAM supply &amp;ldquo;could decline in 2027 as more capacity shifts to server applications,&amp;rdquo; and on November 11 that memory makers have tentatively planned cuts to PC DRAM supply in 2027. SK hynix says long-term agreements with 14 major customers, including large cloud providers, already cover more than half of its production capacity for 2027 and 2028. No source I read expects that allocation to swing back toward PCs.&lt;/p>
&lt;p>One note in that release is softer. The same November 11 release says falling notebook sales have left PC makers holding more DRAM inventory, and that suppliers have &amp;ldquo;some flexibility to slightly moderate price increases.&amp;rdquo; So TrendForce&amp;rsquo;s fourth-quarter forecast is a slower rise, not a fall.&lt;/p>
&lt;h3 id="new-suppliers">New suppliers&lt;/h3>
&lt;p>China&amp;rsquo;s CXMT has its fifth-generation process in mass production and expects to start sampling its first DDR5 RDIMMs on a new 4F² architecture by the end of 2026, with servers among the first targets (TrendForce News, November 12). Nanya, Winbond and PSMC, which stay on mature processes, have been picking up demand the three largest makers can no longer fully serve, TrendForce wrote on September 7. None of these sources says a new supplier will bring desktop DDR5 prices down.&lt;/p>
&lt;h3 id="demand">Demand&lt;/h3>
&lt;p>The demand forecasts I read run the other way. TrendForce (October 14) projects capital spending by the nine leading cloud providers to pass $1.5 trillion in 2027, about 60% above 2026. Its July 30 caveat: if memory stays expensive through 2027, whether that changes cloud providers&amp;rsquo; plans &amp;ldquo;remains a key variable to watch.&amp;rdquo; Consumer demand is the weak side; notebook shipments fell 15.8% from the second quarter of 2026 to the third (TrendForce, November 11).&lt;/p>
&lt;h2 id="will-ram-prices-go-down-in-2026">Will RAM prices go down in 2026?&lt;/h2>
&lt;p>No source I read expects it. TrendForce forecasts conventional DRAM contract prices up 10–15% in the fourth quarter (September 30) and PC DRAM contract prices up 13–18% (November 11). Counterpoint (November 6) has prices rising in every segment in the fourth quarter, more slowly than in the third, with PC DRAM that &amp;ldquo;keeps climbing quarter after quarter.&amp;rdquo; Fortune (November 10), citing BigGo Finance&amp;rsquo;s account of TeamGroup&amp;rsquo;s November 2 earnings call, has Chen calling the stretch from then through the end of the second quarter of 2027 the most severe.&lt;/p>
&lt;p>Contract prices are what memory makers charge their customers, and TrendForce News (November 12), relaying Lanjing News, said the latest rises reach manufacturers and module makers before consumers. The same roundup&amp;rsquo;s retail reports were mixed: 16GB DDR5 modules in Shenzhen&amp;rsquo;s Huaqiangbei market quoted around RMB 1,600, below a reported RMB 2,000 average contract price (Lanjing News), against The Paper&amp;rsquo;s report that consumer memory prices had risen too.&lt;/p>
&lt;p>&lt;strong>DDR5 and DDR4.&lt;/strong> TrendForce&amp;rsquo;s spot-market note of November 4 split them. Some DDR5 chip buyers raised their target prices under delivery pressure, while DDR4 chip spot prices sat above suppliers&amp;rsquo; official prices and buyers held off, expecting a correction; the mainstream DDR4 chip slipped 0.09% to $46.82 that week. Those are spot prices for memory chips, not the price of a finished kit.&lt;/p>
&lt;h2 id="will-ram-prices-go-down-in-2027">Will RAM prices go down in 2027?&lt;/h2>
&lt;p>The 2027 forecasts are the most consistent part of this page. None of them expects a fall:&lt;/p>
&lt;ul>
&lt;li>TrendForce (July 30) expects DRAM prices &amp;ldquo;on an upward trajectory&amp;rdquo; and the supply-demand gap to widen; its August 4 release says DRAM supply will remain tight through 2027.&lt;/li>
&lt;li>Micron (September 30) expects industry DRAM bit shipments to grow in the low-20s percent in calendar 2027 and 2028, with the industry supply-constrained in both years.&lt;/li>
&lt;li>Samsung (October 29) says that in 2027 &amp;ldquo;increasing AI-driven demand will far exceed the industry supply in comparison with 2026.&amp;rdquo;&lt;/li>
&lt;li>Counterpoint (November 6) says early 2027 negotiations signal another first-quarter increase, and its September 2 report says long-term agreements make &amp;ldquo;a gradual price decline unlikely for at least the next year and a half.&amp;rdquo; TrendForce (November 6) expects DRAM price increases to &amp;ldquo;gain further momentum in 1Q27.&amp;rdquo;&lt;/li>
&lt;li>TeamGroup&amp;rsquo;s Chen sees no downward price trend in 2027 (Fortune, November 10).&lt;/li>
&lt;/ul>
&lt;p>The one view I found that put improvement inside 2027 is older: analyst Patrick Moorhead of Moor Insights &amp;amp; Strategy told PCWorld on April 24, 2026 that the situation &amp;ldquo;should start getting better in Q4 2027.&amp;rdquo; None of the forecasts I read from July onward names an improvement in 2027.&lt;/p>
&lt;p>I found no 2027 forecast for DDR4 on its own. TrendForce has reported that, spurred by tariffs and suppliers&amp;rsquo; DDR4 end-of-life plans, some module makers stocked up on DDR4 chips in the second quarter of 2025 (September 22), and that DDR4 and DDR3 contract prices rose significantly in the second quarter of 2026 (September 7).&lt;/p>
&lt;h2 id="will-ram-prices-go-down-in-2028">Will RAM prices go down in 2028?&lt;/h2>
&lt;p>No source I read forecasts lower prices in 2028, though it is the year TrendForce expects substantial output from new fabs, and Micron&amp;rsquo;s ID2 and Japan expansion are due to start output late that year. Micron still expects the industry to be supply-constrained in 2028, Chen (as Fortune reported) puts balance in the second half of 2028 at the earliest, and SK hynix expects demand to exceed supply through 2030.&lt;/p>
&lt;h2 id="when-will-ram-prices-go-back-to-normal">When will RAM prices go back to normal?&lt;/h2>
&lt;p>No source I read defines normal as a price or dates a return to one. On supply, the dates run from the second half of 2028 at the earliest (TeamGroup&amp;rsquo;s Chen, per Fortune) to 2030: SK hynix (October 28) expects demand to exceed supply through 2030, and Moorhead told PCWorld in April that he didn&amp;rsquo;t think the market would be &amp;ldquo;normalized until 2030.&amp;rdquo; Micron (September 30) gives no date at all, saying it does not &amp;ldquo;have line of sight to when supply and demand will return to balance.&amp;rdquo;&lt;/p>
&lt;h2 id="ram-and-storage-are-on-different-clocks">RAM and storage are on different clocks&lt;/h2>
&lt;p>If the question is when RAM and storage prices go down, the sources split the two. TrendForce (July 21) expects supply constraints in NAND flash, the chips inside SSDs, to ease in the second half of 2027, while it expects DRAM to stay tight (July 30). Micron disagrees: on September 30 it said it expects the NAND industry to remain supply-constrained in 2027 and 2028. In the short run, TrendForce News reported on November 17 that NAND spot prices had fallen 20% in two weeks, and TrendForce expects client SSD contract prices to rise less than 5% in the fourth quarter (November 11). My &lt;a href="https://techfuelhq.com/data/ssd-price-index/">SSD price index&lt;/a> has dated Newegg prices for 2TB drives.&lt;/p>
&lt;h2 id="the-price-fixing-lawsuit">The price-fixing lawsuit&lt;/h2>
&lt;p>On November 14, 2026, Judge Noël Wise of the US District Court for the Northern District of California denied Samsung, SK hynix and Micron&amp;rsquo;s motion to dismiss a putative class action alleging that they cut production, coordinated a pivot to HBM, exited DDR3 and DDR4 and otherwise restricted conventional DRAM supply (Garciaguirre v. Samsung Electronics, 26-cv-06345-NW). The ruling lets the case proceed; it does not decide whether anyone colluded. Answers are due by December 7, 2026. TrendForce News, citing NewsPim, reported that industry observers expect limited immediate financial impact because US antitrust cases can take years, and no source I read ties the case to a date for lower prices.&lt;/p>
&lt;h2 id="what-i-would-do-meanwhile">What I would do meanwhile&lt;/h2>
&lt;p>This part is my judgment, not a forecast.&lt;/p>
&lt;p>&lt;strong>Buy the capacity you need now, and no more.&lt;/strong> If a build can&amp;rsquo;t wait, nothing above suggests that holding out into 2027 gets you a lower price. Work out what your workload needs with the &lt;a href="https://techfuelhq.com/articles/ddr5-ram-buying-guide-2025/">DDR5 buying guide&lt;/a> and stop there. I wouldn&amp;rsquo;t buy extra capacity &amp;ldquo;to be safe&amp;rdquo; at these prices.&lt;/p>
&lt;p>&lt;strong>Keep a working machine working.&lt;/strong> The cheapest memory is the memory already in a system that does its job. If DDR5 is what blocks a build, the explainer prices &lt;a href="https://techfuelhq.com/articles/ram-ssd-price-crisis-2026/#the-ddr4am4-escape-hatch">the DDR4 route&lt;/a>; I don&amp;rsquo;t track DDR4 myself.&lt;/p>
&lt;p>&lt;strong>Don&amp;rsquo;t wait for&lt;/strong> a 2026 drop, which no source forecasts; for the new fabs, since Micron&amp;rsquo;s ID1 starts wafer output in mid-2027 by Micron&amp;rsquo;s own date and TrendForce doesn&amp;rsquo;t expect substantial new output until 2028; for the lawsuit, which has only just cleared a motion to dismiss; or for new Chinese supply, since the first DDR5 product CXMT has announced on its new architecture is a server module (RDIMM).&lt;/p>
&lt;p>&lt;strong>Compare part numbers, not names.&lt;/strong> The same kit family is sold in several timings, CL30 and CL36 among them. My index had to correct for exactly that in October.&lt;/p>
&lt;h3 id="if-you-have-to-buy-now">If you have to buy now&lt;/h3>
&lt;p>These were the three cheapest tracked kits in Newegg&amp;rsquo;s affiliate catalogue in my November 17, 2026 capture, all 32GB (2x16GB) DDR5-6000 CL30. The catalogue names no seller, and these are catalogue prices from that date, not live quotes.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;ul>
&lt;li>&lt;strong>TeamGroup T-Force Delta RGB&lt;/strong>, part FF3D532G6000HC30DC01: $639.99 in Newegg&amp;rsquo;s catalogue on November 17, 2026. &lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=FF3D532G6000HC30DC01&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/when-will-ram-prices-go-down/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2FN82E16820331845" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/when-will-ram-prices-go-down/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>
&lt;/a>
&lt;/span>&lt;/li>
&lt;li>&lt;strong>Corsair Vengeance&lt;/strong>, part CMK32GX5M2B6000C30: $644.99 in Newegg&amp;rsquo;s catalogue on November 17, 2026. &lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=CMK32GX5M2B6000C30&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/when-will-ram-prices-go-down/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2FN82E16820982007" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/when-will-ram-prices-go-down/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>
&lt;/a>
&lt;/span>&lt;/li>
&lt;li>&lt;strong>Corsair Vengeance RGB&lt;/strong>, part CMH32GX5M2N6000Z30: $654.99 in Newegg&amp;rsquo;s catalogue on November 17, 2026. &lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=CMH32GX5M2N6000Z30&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/when-will-ram-prices-go-down/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2FN82E16820982184" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/when-will-ram-prices-go-down/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="product">
&lt;span class="buy-action__label">Check Newegg&lt;/span>
&lt;/a>
&lt;/span>&lt;/li>
&lt;/ul>
&lt;p>The Newegg buttons open each kit&amp;rsquo;s item page. The Amazon buttons are part-number searches, so match the part before you pay. The &lt;a href="https://techfuelhq.com/articles/ddr5-6000-cl30-explained-2026/">DDR5-6000 CL30 explainer&lt;/a> covers what CL30 buys you over looser kits.&lt;/p></description></item><item><title>Watchtower Docker: Archived, What It Does, and Alternatives (2026)</title><link>https://techfuelhq.com/tutorials/watchtower-docker-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/watchtower-docker-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;p>&lt;strong>Watchtower is archived.&lt;/strong> The &lt;code>containrrr/watchtower&lt;/code> repository is read-only on GitHub, its README opens with &amp;ldquo;This project is no longer maintained,&amp;rdquo; and the last tagged release is v1.7.1 from November 11, 2023. The last commit, on December 17, 2025, only added that notice. If you came here to install it, the project&amp;rsquo;s docs still show you how to run it, but nobody is going to fix it, and you should know what that means before you hand it control of your containers.&lt;/p>
&lt;h2 id="what-the-project-says-about-itself">What the project says about itself&lt;/h2>
&lt;p>The notice points to a GitHub discussion, &amp;ldquo;Goodbye containrrr/watchtower!&amp;rdquo;, posted December 17, 2025 by one of the two maintainers. They say they are looking to archive the repository because neither of them is a big Docker user anymore, and they lost interest and time. They also say there are a few forks, that they know nothing about them and can&amp;rsquo;t vouch for their legitimacy, and that anyone who wants to keep using Watchtower should assess a fork themselves. The poster also says a few of the active forks he had looked at are poor quality and that, while they might work, he wouldn&amp;rsquo;t advise using any of them. He doesn&amp;rsquo;t name them, so I can&amp;rsquo;t say whether that applies to the fork below.&lt;/p>
&lt;p>So there is &lt;strong>no successor the project endorses.&lt;/strong> It points at no fork. Forks do exist. One, &lt;code>nicholas-fedor/watchtower&lt;/code>, published its v1.24.0 on November 4, 2026, ships its image as &lt;code>nickfedor/watchtower&lt;/code>, and says in its README that it was tested against Docker API v1.43 and higher and negotiates the API version by default. I have not reviewed its code, and the original maintainers&amp;rsquo; warning applies to it as much as any other: read what you are about to give your Docker socket to.&lt;/p>
&lt;h2 id="what-watchtower-does">What Watchtower does&lt;/h2>
&lt;p>Per its documentation, Watchtower monitors your running containers and watches for changes to the images they were started from. When an image has changed, it pulls the new image, gracefully shuts down the existing container, and restarts it with the same options that were used when it was deployed initially. By default it watches all containers on the daemon it points at, and by default it checks every 24 hours.&lt;/p>
&lt;p>It is itself a container, and it needs the Docker API to do any of this, so the docs have you mount &lt;code>/var/run/docker.sock&lt;/code> into it.&lt;/p>
&lt;h2 id="a-compose-example-from-the-docs">A compose example from the docs&lt;/h2>
&lt;p>This is the compose file from the project&amp;rsquo;s quick start, except that I dropped its &lt;code>version: &amp;quot;3&amp;quot;&lt;/code> line, which Docker&amp;rsquo;s docs say is obsolete and only produces a warning.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">watchtower&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">containrrr/watchtower&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">volumes&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/var/run/docker.sock:/var/run/docker.sock&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>That is a complete Watchtower. With no arguments it checks all running containers every 24 hours and updates any whose image has changed. To change that behavior you add arguments or environment variables. This version uses the environment variable names from the project&amp;rsquo;s arguments page; I assembled it from that page and haven&amp;rsquo;t run it:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">watchtower&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">containrrr/watchtower&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">TZ&lt;/span>: &lt;span style="color:#ae81ff">America/Chicago&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">WATCHTOWER_SCHEDULE&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;0 0 4 * * *&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">WATCHTOWER_CLEANUP&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;true&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">WATCHTOWER_LABEL_ENABLE&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;true&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">volumes&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/var/run/docker.sock:/var/run/docker.sock&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">someapp&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">example/someapp:latest &lt;/span> &lt;span style="color:#75715e"># replace with your own image&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">labels&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#e6db74">&amp;#34;com.centurylinklabs.watchtower.enable=true&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>If you keep your variables in a &lt;code>.env&lt;/code> file instead, &lt;a href="https://techfuelhq.com/tutorials/docker-compose-environment-variables-2026/">Docker Compose environment variables&lt;/a> covers how Compose reads them.&lt;/p>
&lt;h2 id="the-options-that-matter">The options that matter&lt;/h2>
&lt;p>All of these are from Watchtower&amp;rsquo;s arguments and container-selection pages.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">What you want&lt;/th>
&lt;th scope="col">Option&lt;/th>
&lt;th scope="col">Default and notes&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="What you want">Check on a clock&lt;/td>
&lt;td data-label="Option">&lt;code>--schedule&lt;/code>, &lt;code>WATCHTOWER_SCHEDULE&lt;/code>&lt;/td>
&lt;td data-label="Default and notes">A cron expression with six fields (not the usual five), for example &lt;code>0 0 4 * * *&lt;/code>. Use it or &lt;code>--interval&lt;/code>, not both.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you want">Check every N seconds&lt;/td>
&lt;td data-label="Option">&lt;code>--interval&lt;/code>, &lt;code>WATCHTOWER_POLL_INTERVAL&lt;/code>&lt;/td>
&lt;td data-label="Default and notes">86400 seconds (24 hours).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you want">Time zone for logs and the schedule&lt;/td>
&lt;td data-label="Option">&lt;code>TZ&lt;/code>&lt;/td>
&lt;td data-label="Default and notes">UTC unless set. Set it, or your 4 a.m. schedule is 4 a.m. UTC.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you want">Delete the old image after an update&lt;/td>
&lt;td data-label="Option">&lt;code>--cleanup&lt;/code>, &lt;code>WATCHTOWER_CLEANUP&lt;/code>&lt;/td>
&lt;td data-label="Default and notes">Off. The docs say it prevents orphaned images accumulating. See &lt;a href="https://techfuelhq.com/tutorials/docker-cleanup-disk-space-2026/">Docker cleanup&lt;/a> for what else eats disk.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you want">Check and notify, but don&amp;rsquo;t update&lt;/td>
&lt;td data-label="Option">&lt;code>--monitor-only&lt;/code>, &lt;code>WATCHTOWER_MONITOR_ONLY&lt;/code>&lt;/td>
&lt;td data-label="Default and notes">Off. Per container: label &lt;code>com.centurylinklabs.watchtower.monitor-only=true&lt;/code>. The docs note the latest image is still pulled so it can tell what changed.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you want">Only update containers you opt in&lt;/td>
&lt;td data-label="Option">&lt;code>--label-enable&lt;/code>, &lt;code>WATCHTOWER_LABEL_ENABLE&lt;/code>&lt;/td>
&lt;td data-label="Default and notes">Off. With it on, only containers labeled &lt;code>com.centurylinklabs.watchtower.enable=true&lt;/code> are watched.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you want">Exclude one container&lt;/td>
&lt;td data-label="Option">label &lt;code>com.centurylinklabs.watchtower.enable=false&lt;/code> on that container&lt;/td>
&lt;td data-label="Default and notes">Set on the container to ignore, not on Watchtower.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you want">Exclude by name&lt;/td>
&lt;td data-label="Option">&lt;code>--disable-containers&lt;/code>, &lt;code>WATCHTOWER_DISABLE_CONTAINERS&lt;/code>&lt;/td>
&lt;td data-label="Default and notes">Excludes the listed names even if they carry the enable label.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you want">Update once and exit&lt;/td>
&lt;td data-label="Option">&lt;code>--run-once&lt;/code>&lt;/td>
&lt;td data-label="Default and notes">Runs an update attempt on the container names you pass and exits.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you want">Remove anonymous volumes on update&lt;/td>
&lt;td data-label="Option">&lt;code>--remove-volumes&lt;/code>&lt;/td>
&lt;td data-label="Default and notes">Off. Named volumes are not removed.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Two details from those pages are easy to miss. First, arguments take precedence over labels by default, so a global &lt;code>--monitor-only&lt;/code> beats a container&amp;rsquo;s &lt;code>monitor-only=false&lt;/code> label unless you also set &lt;code>--label-take-precedence&lt;/code>. Second, &lt;code>--remove-volumes&lt;/code> is off by default and removes anonymous volumes only, the same category the &lt;a href="https://techfuelhq.com/tutorials/docker-cleanup-disk-space-2026/">Docker cleanup page&lt;/a> shows can hold real data when you never named a volume.&lt;/p>
&lt;p>I found no mention of rollback in the project&amp;rsquo;s documentation. Think of an update as a one-way move, and &lt;a href="https://techfuelhq.com/homelab/restic-vs-borg-vs-kopia-2026/">back up&lt;/a> anything stateful before it runs unattended.&lt;/p>
&lt;h2 id="what-the-project-says-about-production">What the project says about production&lt;/h2>
&lt;p>Plainly: don&amp;rsquo;t. The README says Watchtower is intended for homelabs, media centers and local dev environments, and that the project does not recommend using it in a commercial or production environment. It points those users to Kubernetes, or to MicroK8s and k3s if Kubernetes is too big a step.&lt;/p>
&lt;p>Two things from Docker&amp;rsquo;s side are worth knowing alongside that.&lt;/p>
&lt;p>&lt;strong>The socket.&lt;/strong> Mounting &lt;code>docker.sock&lt;/code> is what lets Watchtower work, and it is control of the Docker daemon. Docker&amp;rsquo;s security page says only trusted users should be allowed to control the daemon, and that a container can be started with the host&amp;rsquo;s &lt;code>/&lt;/code> shared into it. That is the page&amp;rsquo;s reasoning for the daemon in general, not a statement about Watchtower, and I&amp;rsquo;d weigh it that way for any container you give the socket.&lt;/p>
&lt;p>&lt;strong>Current Docker Engine.&lt;/strong> Docker&amp;rsquo;s release notes say Engine 29.0.0 (November 10, 2025) raised the daemon&amp;rsquo;s minimum API version to 1.44, and 29.3.0 (March 5, 2026) lowered it to 1.40. Watchtower&amp;rsquo;s arguments page gives its default API version as 1.24. An issue opened November 14, 2025 against the repository, still open today, reports the error &amp;ldquo;client version 1.25 is too old&amp;rdquo; on Docker 29.0.0. Both Watchtower numbers are below 1.40, so I would not assume it runs on a current daemon. I haven&amp;rsquo;t tested it. People in that thread report setting the &lt;code>DOCKER_API_VERSION&lt;/code> variable (the arguments page lists it) as a workaround; the project&amp;rsquo;s docs say nothing about this, and the repository is archived, so don&amp;rsquo;t expect an official answer. Check &lt;code>docker version&lt;/code> on your host before relying on it.&lt;/p>
&lt;h2 id="docker-hub-limits">Docker Hub limits&lt;/h2>
&lt;p>Watchtower polls registries, and Docker Hub rate-limits pulls. Docker&amp;rsquo;s documentation says unauthenticated users get 100 pulls per six hours per IPv4 address or IPv6 /64 subnet, authenticated Docker Personal users get 200, and paid plans have no pull rate limit. It also says version checks do not count towards usage pricing, and that in its rate-limit check a HEAD request doesn&amp;rsquo;t count where a GET does. Watchtower&amp;rsquo;s docs say its HEAD digest check lets it skip pulling when nothing changed, and the default of its &lt;code>--warn-on-head-failure&lt;/code> option (auto) warns about failed HEAD requests to registries known to handle them that may rate-limit pulls, mainly docker.io. I haven&amp;rsquo;t measured how many pulls a given Watchtower setup triggers. As for the free question, Docker&amp;rsquo;s pricing page lists Docker Personal at $0, with those limits.&lt;/p>
&lt;h2 id="alternatives-described-from-their-own-documentation">Alternatives, described from their own documentation&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Tool&lt;/th>
&lt;th scope="col">What its docs say it does&lt;/th>
&lt;th scope="col">Status I found on 2026-11-17&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Tool">&lt;strong>Diun&lt;/strong>&lt;/td>
&lt;td data-label="What its docs say it does">It &amp;ldquo;watches container images and tells you when an update is available.&amp;rdquo; It checks registries for new tags or digest changes and notifies you. Its README describes notifications, not applying updates.&lt;/td>
&lt;td data-label="Status I found on 2026-11-17">Not archived; v4.33.1 released October 24, 2026; MIT.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tool">&lt;strong>What&amp;rsquo;s Up Docker (WUD)&lt;/strong>&lt;/td>
&lt;td data-label="What its docs say it does">Monitors containers across Docker, Compose, Swarm, Kubernetes and Nomad, does semantic-version analysis and tag filtering, and notifies. The README also lists automated updates: pulling new images and recreating containers on demand for Docker, Compose and Nomad.&lt;/td>
&lt;td data-label="Status I found on 2026-11-17">Not archived; 9.8.0 released November 7, 2026; MIT.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tool">&lt;strong>Podman auto-update&lt;/strong>&lt;/td>
&lt;td data-label="What its docs say it does">&lt;code>podman auto-update&lt;/code> pulls new images and restarts containers configured for auto-updates. Containers must run inside a systemd unit and carry the &lt;code>io.containers.autoupdate&lt;/code> label. It ships a &lt;code>podman-auto-update.service&lt;/code> triggered daily at midnight by a timer, and has a &lt;code>--dry-run&lt;/code> option.&lt;/td>
&lt;td data-label="Status I found on 2026-11-17">Part of Podman; requires Podman, not Docker.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tool">&lt;strong>Forks of Watchtower&lt;/strong>&lt;/td>
&lt;td data-label="What its docs say it does">&lt;code>nicholas-fedor/watchtower&lt;/code> is one: same idea, own image name, see above.&lt;/td>
&lt;td data-label="Status I found on 2026-11-17">v1.24.0 released November 4, 2026; Apache-2.0. The original maintainers do not vouch for any fork.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Tool">&lt;strong>Manual compose&lt;/strong>&lt;/td>
&lt;td data-label="What its docs say it does">&lt;code>docker compose pull&lt;/code> pulls service images; &lt;code>docker compose up&lt;/code> recreates a container when its configuration or image changed, preserving mounted volumes.&lt;/td>
&lt;td data-label="Status I found on 2026-11-17">Part of Docker Compose.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The choice is mostly about who decides when an update lands. If you want to know about updates and apply them yourself, Diun, or Watchtower in monitor-only mode, fit that, and the manual compose route costs you two commands. If you want unattended updates, WUD is the closest tool I found that lists automated updates in its README, and Podman covers it natively if you run Podman. A Watchtower fork is the other candidate, with the maintainers&amp;rsquo; warning above attached. For anything that matters, I&amp;rsquo;d rather get the notification and do the update on a day I&amp;rsquo;m watching. A web UI for your stacks is a different tool again; &lt;a href="https://techfuelhq.com/homelab/komodo-vs-portainer-vs-dockge-2026/">Komodo, Portainer and Dockge compared&lt;/a> and the &lt;a href="https://techfuelhq.com/tutorials/dockge-docker-compose-manager-2026/">Dockge walkthrough&lt;/a> cover that side, and the &lt;a href="https://techfuelhq.com/tools/docker-ram-planner/">Docker RAM planner&lt;/a> will tell you what a stack costs in memory before you add more containers.&lt;/p></description></item><item><title>How to Turn Off the FPS Counter on Windows 11: Find the Overlay, Then Switch It Off</title><link>https://techfuelhq.com/tutorials/turn-off-fps-counter-windows-11-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/turn-off-fps-counter-windows-11-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;p>An FPS counter on Windows 11 is not a Windows setting you can flip in one place. Some program is drawing it, and each program has its own switch. Find the program, use its switch, and you&amp;rsquo;re done in under a minute.&lt;/p>
&lt;p>Here is the short version, in the order I&amp;rsquo;d try them:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">If the counter comes from&lt;/th>
&lt;th scope="col">Documented off switch&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="If the counter comes from">NVIDIA app&lt;/td>
&lt;td data-label="Documented off switch">Press &lt;strong>Alt+R&lt;/strong> to toggle the statistics overlay&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="If the counter comes from">AMD Software&lt;/td>
&lt;td data-label="Documented off switch">Press &lt;strong>Ctrl+Shift+O&lt;/strong>, or turn off &lt;strong>Show Metrics Overlay&lt;/strong> on the Overlay tab of Performance Metrics&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="If the counter comes from">Steam&lt;/td>
&lt;td data-label="Documented off switch">&lt;strong>Settings &amp;gt; In Game&lt;/strong>, Performance Overlay section&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="If the counter comes from">Xbox Game Bar&lt;/td>
&lt;td data-label="Documented off switch">&lt;strong>Win+G&lt;/strong> opens it; Microsoft documents no off switch for the Performance widget (see below)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="If the counter comes from">Intel Arc Control&lt;/td>
&lt;td data-label="Documented off switch">&lt;strong>Alt+I&lt;/strong>, Performance tab, telemetry overlay switch&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>If you don&amp;rsquo;t know which row you&amp;rsquo;re in, the next section sorts that out.&lt;/p>
&lt;h2 id="work-out-which-program-is-drawing-it">Work out which program is drawing it&lt;/h2>
&lt;p>Don&amp;rsquo;t judge by the corner. NVIDIA&amp;rsquo;s support article says its overlay appears on the top right of the screen, and AMD&amp;rsquo;s article lists Top Right as the default location for its metrics overlay. Two different programs, same corner.&lt;/p>
&lt;p>Judge by what&amp;rsquo;s installed and by the documented hotkeys instead.&lt;/p>
&lt;p>&lt;strong>See which of these programs exist on the PC.&lt;/strong> On my bench machine I read the installed-program list and the Game Bar app package. It has the NVIDIA app and Steam, and no Xbox Game Bar app registered for my user account (details in the methodology note). So on my PC a counter can only be one of those two or something inside a game. Yours will differ, and that check takes ten seconds.&lt;/p>
&lt;p>&lt;strong>Then use the hotkey each vendor documents.&lt;/strong> NVIDIA and AMD both describe their keys as toggles, so pressing again puts things back:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Alt+R&lt;/strong> is NVIDIA&amp;rsquo;s statistics toggle. In AMD&amp;rsquo;s older Radeon Overlay documentation, Alt+R is the default hotkey that opens a menu, not a counter, so on a Radeon system it behaves differently.&lt;/li>
&lt;li>&lt;strong>Ctrl+Shift+O&lt;/strong> is AMD&amp;rsquo;s default for toggling the performance overlay.&lt;/li>
&lt;li>&lt;strong>Win+G&lt;/strong> opens Xbox Game Bar.&lt;/li>
&lt;li>&lt;strong>Alt+Z&lt;/strong> opens the NVIDIA app overlay, and &lt;strong>Alt+I&lt;/strong> opens Intel Arc Control.&lt;/li>
&lt;/ul>
&lt;p>If a hotkey changes the counter, you&amp;rsquo;ve found the culprit. If it opens a menu instead, you&amp;rsquo;ve still found a program, just not the one drawing the counter.&lt;/p>
&lt;h2 id="nvidia-app-turn-off-the-statistics-overlay">NVIDIA app: turn off the statistics overlay&lt;/h2>
&lt;p>NVIDIA&amp;rsquo;s support article for the in-game overlay says the shortcut is &lt;strong>Alt+R&lt;/strong>, &amp;ldquo;to toggle the statistics overlay on/off&amp;rdquo;, and that Alt+Shift+R cycles through different metrics. NVIDIA&amp;rsquo;s app update post says the same: once the statistics are configured they show in-game and can be toggled on or off with Alt+R.&lt;/p>
&lt;p>To change that key, NVIDIA says to press Alt+Z, click the Settings cog and choose Shortcuts. To change what the overlay shows, the path is Alt+Z, then Statistics, then Configure heads up display. The overlay&amp;rsquo;s side bar has Statistics at the bottom.&lt;/p>
&lt;p>NVIDIA&amp;rsquo;s Reflex analyzer guide, dated March 2022 and written for the older GeForce Experience overlay, adds that if the latency stats stop working you should toggle the overlay off with Alt+R, wait at least 30 seconds, then toggle it back on.&lt;/p>
&lt;p>NVIDIA&amp;rsquo;s article also says the In-Game Overlay has to be enabled under Settings &amp;gt; Features in the NVIDIA app for this to work. It does not describe turning that switch off as a way to remove the counter, so I won&amp;rsquo;t claim it does. Alt+R is the documented off switch.&lt;/p>
&lt;p>I own an RTX 5080 with NVIDIA App 11.0.9.585 and driver 621.24 installed. I didn&amp;rsquo;t launch the overlay while writing this, so the path above is NVIDIA&amp;rsquo;s wording, not a click-through.&lt;/p>
&lt;h2 id="amd-software-turn-off-the-metrics-overlay">AMD Software: turn off the metrics overlay&lt;/h2>
&lt;p>AMD&amp;rsquo;s article on performance metrics, last updated in November 2024 and based on Adrenalin Edition 23.9.1 by its own note, gives two routes. In AMD Software, search for &amp;ldquo;Metrics&amp;rdquo;, open the Performance Metrics result, and go to the Overlay tab. The &lt;strong>Show Metrics Overlay&lt;/strong> item is described as enabling or disabling the on-screen overlay metrics stats.&lt;/p>
&lt;p>The faster route is the hotkey. The default for Toggle Performance Overlay is &lt;strong>Ctrl+Shift+O&lt;/strong>, and Ctrl+Shift+L toggles performance logging. To see or change the hotkeys, search for &amp;ldquo;Hotkey&amp;rdquo; in AMD Software and open Hotkey Settings. AMD says pressing Delete on the keyboard unbinds a hotkey, and a Reset icon restores the defaults.&lt;/p>
&lt;p>Older Radeon Software worked differently. AMD&amp;rsquo;s Radeon Overlay article, last modified in April 2024, says Radeon Overlay is enabled by default and opens with Alt+R, and that you disable it by unchecking Show Overlay in Radeon Settings under the Preference section. It also says the performance monitoring display can be toggled with Show Metrics or Ctrl+Shift+O. If your menus look like the older layout, that article is the one that matches.&lt;/p>
&lt;h2 id="steam-the-in-game-counter-is-now-a-performance-overlay">Steam: the in-game counter is now a Performance Overlay&lt;/h2>
&lt;p>Valve changed this in 2025. Its Steam Client Beta post says the In-Game FPS counter was expanded into the In-Game Overlay Performance monitor, that the lowest level of detail shows an FPS counter like before, and that you adjust detail and appearance in Settings &amp;gt; In Game.&lt;/p>
&lt;p>The release post on 30 June 2025 gives the path: go to &lt;strong>Settings &amp;gt; In Game&lt;/strong> and find the Performance Overlay section. Valve says that&amp;rsquo;s where you enable the overlay, adjust its size and position, and set a hotkey. The overlay has four levels of detail, from a single FPS value up to FPS, CPU, GPU and RAM, and Valve says they can be adjusted live in-game. Valve&amp;rsquo;s June post also says the overlay can break out frames generated by DLSS or FSR from the game&amp;rsquo;s actual frame rate. If you use frame generation, &lt;a href="https://techfuelhq.com/articles/frame-generation-explained-2026/">frame generation explained&lt;/a> covers what those generated frames are.&lt;/p>
&lt;p>What I can&amp;rsquo;t give you is the exact label of the off choice. Valve&amp;rsquo;s post and support FAQ, as I read them, don&amp;rsquo;t name it, and I haven&amp;rsquo;t opened Steam for this page. The two Valve pages also name the section differently: the June 2025 post says the Performance Overlay section, while the support FAQ says the Performance Monitor settings under Settings &amp;gt; In Game. Open Settings &amp;gt; In Game and look at the controls there. Valve&amp;rsquo;s support FAQ, &amp;ldquo;Understanding the In-Game Overlay Performance Monitor&amp;rdquo;, explains every number the overlay shows.&lt;/p>
&lt;h2 id="xbox-game-bar-no-documented-off-switch">Xbox Game Bar: no documented off switch&lt;/h2>
&lt;p>Microsoft added an FPS counter to the Game Bar&amp;rsquo;s Performance overlay in 2019 (an Insider-program note and an October 2019 Xbox Wire post), and its 2019 posts say you get to Game Bar with Win+G. The settings gear in the upper right of Game Bar shows the version, and Microsoft&amp;rsquo;s 2019 note says the counter needs version V3.33.26001.0 or later. In October 2020 Microsoft said you can choose which metrics the Performance widget tracks through the widget&amp;rsquo;s settings.&lt;/p>
&lt;p>I could not find a Microsoft page that says how to switch the Performance widget off. Microsoft&amp;rsquo;s 2019 Game Bar post says you can pin widgets so they stay visible, and its developer reference for Game Bar widgets describes a pin button in the title bar of widgets that support pinning, and a Pinned state. Neither names the Performance widget, and both are about widgets in general. Pinning is a guess I can draw from those pages, not an instruction from Microsoft, so I am not giving it to you as a step. I haven&amp;rsquo;t opened Game Bar on this PC either (the Game Bar app isn&amp;rsquo;t registered for my user, as noted above).&lt;/p>
&lt;p>I also checked the Windows policy key that Microsoft documents as AllowGameDVR, which controls Windows Game Recording and Broadcasting. It reads 0 on my PC. Microsoft&amp;rsquo;s description of that policy doesn&amp;rsquo;t mention the Performance widget, so I&amp;rsquo;m reporting the value and not drawing a conclusion from it.&lt;/p>
&lt;h2 id="intel-arc-control-and-intel-graphics-software">Intel: Arc Control and Intel Graphics Software&lt;/h2>
&lt;p>Intel&amp;rsquo;s article on Arc Control, last reviewed in December 2024, gives the steps: press Alt+I to open Arc Control, go to the Performance tab, and turn the telemetry overlay switch off or on. The article lists Windows 11 Family as its operating system and does not say which Arc Control versions it covers. Intel&amp;rsquo;s other article, last reviewed in July 2026, says a Performance Overlay feature has been available in Intel Graphics Software since version 26.18.2353.2, but it doesn&amp;rsquo;t say how to switch it off, so I won&amp;rsquo;t guess.&lt;/p>
&lt;h2 id="if-none-of-that-is-it">If none of that is it&lt;/h2>
&lt;p>I don&amp;rsquo;t have a vendor page that covers a counter drawn by a game itself, and I couldn&amp;rsquo;t load MSI&amp;rsquo;s Afterburner pages or Epic&amp;rsquo;s support pages today, so I&amp;rsquo;m not covering those rather than quoting forum posts.&lt;/p>
&lt;p>If you want a number back later, the &lt;a href="https://techfuelhq.com/tools/fps-calculator/">FPS calculator&lt;/a> looks up measured results for tested hardware, &lt;a href="https://techfuelhq.com/articles/pc-stuttering-in-games-2026/">why a PC stutters in games&lt;/a> covers reading 1% lows, and the &lt;a href="https://techfuelhq.com/tools/pc-bottleneck-calculator/">bottleneck calculator&lt;/a> is the lookup for CPU and GPU indexes.&lt;/p></description></item><item><title>Motherboard Standoffs: How Many, Where, and How to Check Before Power-On (2026)</title><link>https://techfuelhq.com/tutorials/motherboard-standoffs-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/motherboard-standoffs-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;p>Put a standoff under every screw hole in your motherboard and nowhere else. The ATX specification defines nine mounting locations for a full ATX board, and ASUS&amp;rsquo;s manual for the board in my bench PC says to use nine screws. Smaller boards use a different set, and a Mini-ITX board I checked uses four, so count the holes on yours before you touch the case. Then check that every standoff has a hole above it and every hole has a screw.&lt;/p>
&lt;h2 id="what-standoffs-are-for">What standoffs are for&lt;/h2>
&lt;p>A standoff is a post that screws into the case&amp;rsquo;s motherboard tray and lifts the board off the metal. Intel names a motherboard screwed directly to the case without the required standoffs as a common cause of an electrical short. The ATX specification also sets the gap: the chassis must leave 0.250 inch of clearance below the board, and the specification excludes the standoffs at the mounting holes from that rule. ASUS&amp;rsquo;s installation article says to install the standoffs for the 9 screw holes of its example board, then set the board on them with the rear I/O aligned.&lt;/p>
&lt;h2 id="how-many-and-where">How many, and where&lt;/h2>
&lt;p>Use the board, not the case, as your guide.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Form factor&lt;/th>
&lt;th scope="col">What a source says&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Form factor">ATX&lt;/td>
&lt;td data-label="What a source says">The ATX 2.2 specification lists the locations A, C, F, G, H, J, K, L and M, which is nine. ASUS&amp;rsquo;s manuals for the B650-A and its install article both say nine screws or holes.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Form factor">microATX&lt;/td>
&lt;td data-label="What a source says">The same specification table lists B, C, F, H, J, L, M, R and S for microATX, and says R and S were added for it. It also says the ATX holes line up with microATX holes where possible. The table lists nine locations for microATX. I did not open the separate microATX specification, so that table is my only specification source for it.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Form factor">Mini-ITX&lt;/td>
&lt;td data-label="What a source says">ASUS&amp;rsquo;s manual for its ROG STRIX B650E-I Mini-ITX board says four screws.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The letters are the specification&amp;rsquo;s labels, not what your case prints on the tray. NZXT&amp;rsquo;s H6 article, for example, labels mounts A and U. A few specification details matter in practice. The specification says hole F must be implemented in ATX 2.2 chassis. Hole B was previously required at the rear edge but is no longer needed for ATX, and if a case builder uses it the specification says a removable standoff should be used so boards that skip it are not affected. So a standoff at B under an ATX board is a case to check.&lt;/p>
&lt;p>Case makers say the same thing in their own words. ASUS says different board sizes have holes in different places, so cases offer several standoff positions, and you should install only the standoffs your board needs. Fractal Design&amp;rsquo;s manuals carry a warning to match the motherboard mounting holes to the standoffs.&lt;/p>
&lt;p>If you are not sure which board you own, the &lt;a href="https://techfuelhq.com/tutorials/how-to-check-motherboard-model-2026/">motherboard model guide&lt;/a> shows how to check.&lt;/p>
&lt;h2 id="screws-and-thread-types-as-case-makers-document-them">Screws and thread types as case makers document them&lt;/h2>
&lt;p>Every case manual I opened lists 6-32 for the board screws:&lt;/p>
&lt;ul>
&lt;li>Corsair FRAME 4000 and 3200D: 18 motherboard and HDD screws, 6-32 UNC, 6 mm.&lt;/li>
&lt;li>NZXT H5 Flow: a 6-32 x 5 mm screw for motherboard installation, and the H6 article gives 6-32 x 5 mm mounting screws.&lt;/li>
&lt;li>Fractal Design Meshify 2 and North: a mounting screw marked 6-32, plus a standoff tool and a spare standoff in the Meshify 2 kit.&lt;/li>
&lt;/ul>
&lt;p>NZXT&amp;rsquo;s H5 Flow manual lists a separate M3 x 5 mm screw for 2.5-inch drives, so a case can ship both threads in one bag. I found no case maker that documents an M3 board screw and no source that says what happens if you swap the two, so follow your case manual. Your motherboard will not supply the screws: ASUS&amp;rsquo;s package contents for the B650-A list cables, antennas, M.2 parts and a cable-tie pack, with no case screws.&lt;/p>
&lt;h2 id="pre-installed-standoffs-and-the-centre-post">Pre-installed standoffs and the centre post&lt;/h2>
&lt;p>Some cases ship with standoffs already fitted. Corsair&amp;rsquo;s FRAME 4000 and 3200D tips say that if the pre-installed standoffs do not align with your board, remove the unused ones and move them to the open mounting points. NZXT&amp;rsquo;s H6 ships configured for ATX and ITX, and for microATX you move some standoffs from the lower mounts marked A to the upper mounts marked U.&lt;/p>
&lt;p>One case documents a centre post. NZXT&amp;rsquo;s H6 article says the case includes a raised centre standoff that helps align the board, and tells you to lower the board so all the standoffs meet the screw holes. I could not find a second case maker that describes one, so check your manual instead of assuming yours has it.&lt;/p>
&lt;h2 id="what-a-misplaced-standoff-can-do">What a misplaced standoff can do&lt;/h2>
&lt;p>ASUS and MSI warn about extra standoffs, and neither names the exact part. ASUS says to remove any standoff that does not match a hole, to avoid extras touching the back of the board and causing damage. MSI says any unnecessary standoff between the board&amp;rsquo;s circuits and the case is prohibited, and says its MAG B650M MORTAR has &amp;ldquo;Case standoff keep out zone&amp;rdquo; signs printed on the back. Intel names the opposite error, a board with no standoffs at all.&lt;/p>
&lt;p>The ATX specification explains the geometry. It forbids components within a 0.400 inch square around each required mounting hole on the underside, and allows other underside parts up to 0.098 inch tall, including conductive parts the specification calls intolerant of direct connection to chassis ground. Those are the specification&amp;rsquo;s underside limits; neither it nor ASUS nor MSI says which part a stray standoff would touch.&lt;/p>
&lt;h2 id="check-before-you-power-on">Check before you power on&lt;/h2>
&lt;ol>
&lt;li>Count the holes on the board and the standoffs under it. They should match.&lt;/li>
&lt;li>Lower the board and look. Any standoff with no hole above it comes out, which is what ASUS and Corsair tell you to do.&lt;/li>
&lt;li>Put a screw in every hole, and do not overtighten. ASUS&amp;rsquo;s manual warns that overtightening can damage the board.&lt;/li>
&lt;li>If your board prints keep-out signs on the back, make sure no standoff sits under one. MSI describes this on the MAG B650M MORTAR; check whether yours has them.&lt;/li>
&lt;li>Look for loose screws or metal in the case. MSI&amp;rsquo;s manual says to make sure there are none before you turn the computer on, and Intel&amp;rsquo;s troubleshooting page says to look for anything that could cause an electrical short.&lt;/li>
&lt;/ol>
&lt;p>If the PC does not start, the &lt;a href="https://techfuelhq.com/articles/pc-wont-post-2026/">no-POST guide&lt;/a> and the &lt;a href="https://techfuelhq.com/articles/computer-wont-turn-on-2026/">no-power checklist&lt;/a> give the order to work in. A stray piece of metal is easier to find with the board still accessible, and the &lt;a href="https://techfuelhq.com/tutorials/how-to-clean-pc-2026/">PC cleaning guide&lt;/a> covers opening the case safely. Once the build works, &lt;a href="https://techfuelhq.com/tutorials/how-to-overclock-cpu-2026/">overclocking&lt;/a> is a separate job.&lt;/p>
&lt;h2 id="if-you-need-a-kit">If you need a kit&lt;/h2>
&lt;p>The cases I read include the board screws. A separate kit only helps if you lost them or need extra standoffs. Match the 6-32 thread your case manual lists.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=motherboard&amp;#43;standoff&amp;#43;screw&amp;#43;kit&amp;#43;6-32&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/tutorials/motherboard-standoffs-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3Dmotherboard%2Bstandoff%2Bscrew%2Bkit" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/tutorials/motherboard-standoffs-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>The &lt;a href="https://techfuelhq.com/tools/pc-builder/">PC Builder&lt;/a> holds the rest of the parts list while you check case and board compatibility.&lt;/p></description></item><item><title>How to Overclock Your CPU: AMD and Intel, With the Vendor Limits (2026)</title><link>https://techfuelhq.com/tutorials/how-to-overclock-cpu-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/how-to-overclock-cpu-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;p>Overclocking splits by platform, and the vendors disagree about how much of it they will stand behind. On AMD you tune with Precision Boost Overdrive (PBO) and Curve Optimizer. On Intel you need a K or KF chip on a Z-series board and tune with the BIOS or Intel Extreme Tuning Utility (XTU). Before either: fix your cooling, find out what your board can feed the chip, and record a baseline. Change one setting, stress-test it, then change the next.&lt;/p>
&lt;p>My bench PC is a Ryzen 7 7800X3D on an ASUS ROG STRIX B650-A. This page is built from AMD, Intel and ASUS documents, not from a tuning run of mine, so every figure below is theirs and I say where a vendor gives no number.&lt;/p>
&lt;h2 id="which-chips-and-boards-allow-it">Which chips and boards allow it&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">AMD (AM5)&lt;/th>
&lt;th scope="col">Intel&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">Chips&lt;/td>
&lt;td data-label="AMD (AM5)">AMD says every Ryzen is multiplier-unlocked. Its pages for the 7800X3D, 7700X and 9800X3D list PBO and Curve Optimizer as Yes.&lt;/td>
&lt;td data-label="Intel">K and KF. XTU works only with processor numbers carrying K, KF, HK, X or XE.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Boards&lt;/td>
&lt;td data-label="AMD (AM5)">AMD&amp;rsquo;s AM5 table marks CPU overclocking Yes for X870E, X870, B850, X670E and X670, and No for B840 and A620. It does not list B650 or B650E.&lt;/td>
&lt;td data-label="Intel">Intel&amp;rsquo;s example is a Z-series chipset. For desktop, XTU needs a board with full overclocking (IA, BCLK, memory). B- and W-series boards allow memory overclocking only.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Software&lt;/td>
&lt;td data-label="AMD (AM5)">BIOS, or Ryzen Master for PBO and Curve Optimizer.&lt;/td>
&lt;td data-label="Intel">BIOS, or XTU. XTU 10.0 or newer for Core Ultra (Series 2); 7.14 for 14th gen and older.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>One detail for X3D owners: AMD&amp;rsquo;s 7700X and 9800X3D pages carry an &amp;ldquo;Unlocked for Overclocking: Yes&amp;rdquo; row, and the 7800X3D page has no such row. It does list PBO and Curve Optimizer. That is a gap in AMD&amp;rsquo;s own pages: its Ryzen Master page says every Ryzen is multiplier-unlocked, and I found no AMD document that describes a manual multiplier overclock on the 7800X3D, so I give no steps for one.&lt;/p>
&lt;p>Another gap that matters for my own board: AMD&amp;rsquo;s chipset table does not list B650 or B650E at all, but AMD&amp;rsquo;s 7800X3D, 7700X and 9800X3D pages list both among their supporting chipsets. I read ASUS&amp;rsquo;s BIOS manual only for the X670E series, and the B650-A user manual has no BIOS menus, so I cannot tell you from a vendor document which of these menus the B650-A shows.&lt;/p>
&lt;h2 id="check-these-three-things-first">Check these three things first&lt;/h2>
&lt;p>&lt;strong>Cooling.&lt;/strong> Intel says to use an adequate cooler, and that there is no point overclocking a system that already overheats. AMD&amp;rsquo;s 7800X3D page lists the cooler as not included and recommends liquid cooling for optimal performance. If you are not sure your cooler is healthy, read the &lt;a href="https://techfuelhq.com/articles/cpu-overheating-2026/">CPU overheating guide&lt;/a> first.&lt;/p>
&lt;p>&lt;strong>What the board can supply.&lt;/strong> ASUS describes PBO as letting the processor run past its defined PPT, EDC and TDC limits up to the limits of the board, and its manual says those limits can only be raised up to what the motherboard is programmed for. Intel says boards are designed to sustain a certain level of power, and that Over Power Protection throttles and eventually shuts the system down when that is exceeded. Neither vendor gives a rating for a particular board here, so read yours. My B650-A manual lists a 24-pin, an 8-pin and a 4-pin +12V connector, and ASUS&amp;rsquo;s troubleshooting article suggests connecting all of the CPU and main connectors the board has.&lt;/p>
&lt;p>&lt;strong>A baseline.&lt;/strong> Intel&amp;rsquo;s list is the right one: core voltage under load (idle readings are misleading), peak and hottest-core temperature, system power draw, and one benchmark score you can repeat. Intel adds that large temperature gaps between cores can point to cooler mounting or paste problems. AMD&amp;rsquo;s Ryzen Master page describes real-time monitoring of per-core clock rates, temperature and voltages, and Intel&amp;rsquo;s XTU guide says XTU has built-in temperature monitoring.&lt;/p>
&lt;h2 id="how-to-overclock-a-cpu-on-amd">How to overclock a CPU on AMD&lt;/h2>
&lt;p>AMD calls PBO operation outside specifications and in excess of factory settings, and says using it invalidates the warranty. ASUS&amp;rsquo;s X670E manual lists Curve Optimizer on the same BIOS pages as PBO.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Find the menu.&lt;/strong> AMD says PBO and Curve Optimizer settings can be managed on the fly in Ryzen Master or through the BIOS so they persist across restarts. ASUS&amp;rsquo;s X670E BIOS manual shows PBO twice, on the Ai Tweaker page and on an AMD Overclocking page, with different option lists and a different Curve Optimizer magnitude range ([0] to [60] on one, [0] to [30] on the other). That is a different board from mine, so open your own BIOS and read what it offers. ASUS also shows a warning on the AMD Overclocking page that damage from running outside specification is not covered by the board maker&amp;rsquo;s warranty.&lt;/li>
&lt;li>&lt;strong>Know what each setting does.&lt;/strong> Per ASUS: PBO lets the chip boost at higher voltages for longer than default. The PBO Scalar raises the maximum boost voltage and the time spent there, from 1X to 10X. Boost Clock Override raises the maximum boost target in steps of 25, up to 200 on the manual&amp;rsquo;s scale. Curve Optimizer shifts the voltage and frequency curve: Negative uses lower voltages, Positive higher, and a larger magnitude is a larger shift.&lt;/li>
&lt;li>&lt;strong>Move one number at a time.&lt;/strong> The AMD documents I read give no safe Curve Optimizer offset and no safe voltage. The ASUS range is a menu limit, not a recommendation. AMD&amp;rsquo;s own Curve Optimizer FAQ, written for Ryzen 5000, says values derived by a stress test can cause instability if applied as they are, and tells you to verify with your own workloads.&lt;/li>
&lt;li>&lt;strong>Test per core.&lt;/strong> CoreCycler&amp;rsquo;s readme argues an all-core stress test is not effective for single-core stability, because cores cannot boost as high when all are loaded. Its author ran 24 hours of all-core Prime95 at -30 with a +75 MHz boost override on a Ryzen 9 5900X, yet with the override removed one core needed -9 in single-core testing. That is one chip, not a rule. For a 9800X3D walkthrough, see the &lt;a href="https://techfuelhq.com/articles/9800x3d-undervolt-guide-2026/">Curve Optimizer guide&lt;/a>.&lt;/li>
&lt;/ol>
&lt;p>The ASUS manual also lists a Platform Thermal Throttle Limit that lets you lower the maximum allowed processor temperature. For memory, the profile switch is separate: see &lt;a href="https://techfuelhq.com/tutorials/how-to-enable-xmp-expo-2026/">XMP and EXPO&lt;/a>.&lt;/p>
&lt;h2 id="how-to-overclock-a-cpu-on-intel">How to overclock a CPU on Intel&lt;/h2>
&lt;p>Intel&amp;rsquo;s own method is the one to follow, and its page is generic: its example board is a Z390, and it does not tie its numbers to a processor generation.&lt;/p>
&lt;ol>
&lt;li>Use a K or KF chip on a Z-series board and an adequate cooler.&lt;/li>
&lt;li>Benchmark at stock and record the baseline.&lt;/li>
&lt;li>Set every core to the same multiplier and raise it in steps of one, which adds 100 MHz at a 100 MHz base clock. Apply, restart, test.&lt;/li>
&lt;li>If it is unstable, raise core voltage by 0.05 V at a time, or lower the multiplier. Intel says to find the lowest stable voltage.&lt;/li>
&lt;li>Hold to Intel&amp;rsquo;s limits. With air or liquid cooling, Intel says never push voltage beyond 1.4 V, and keep maximum CPU temperature below 100 C for brief bursts and at 80 C or below for longer workloads. Those figures come from the generic guide above, which gives them as ceilings and not as a voltage or temperature that is safe for a particular chip.&lt;/li>
&lt;/ol>
&lt;p>XTU does the same job in Windows. Intel&amp;rsquo;s XTU guide says it is aimed at intermediate users with some basic knowledge of overclocking, and can also be a good way to start. It describes the XTU stress test as covering CPU, memory or integrated graphics.&lt;/p>
&lt;p>Intel lists safeguards you may hit: over-temperature, over-power, over-current (adjustable as Processor Core ICCMAX in XTU), over-voltage, under-voltage and short-circuit protection. It advises against modifying any you do not understand.&lt;/p>
&lt;p>&lt;strong>Intel&amp;rsquo;s warranty position.&lt;/strong> Intel says altering clock frequency or voltage may void warranties, and that it may be able to detect the alteration. Its one documented exception is the 200S Boost profile, for unlocked Core Ultra 200S processors on compatible Z890 boards with XMP memory. It raises fabric, die-to-die and memory frequencies, and Intel says eligible processors retain the three-year limited warranty provided by Intel. The limits Intel lists: the 200S Boost warranty applies to boxed processors, the profile is designed for one memory module per channel, and Intel&amp;rsquo;s warranty does not cover damage to non-Intel components.&lt;/p>
&lt;h2 id="read-the-thermal-limits-from-the-vendor-not-a-forum">Read the thermal limits from the vendor, not a forum&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Chip&lt;/th>
&lt;th scope="col">Figure&lt;/th>
&lt;th scope="col">Source label&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Chip">Ryzen 7 7800X3D&lt;/td>
&lt;td data-label="Figure">89 C&lt;/td>
&lt;td data-label="Source label">AMD &amp;ldquo;Max. Operating Temperature (Tjmax)&amp;rdquo;&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Chip">Ryzen 7 7700X, Ryzen 7 9800X3D&lt;/td>
&lt;td data-label="Figure">95 C&lt;/td>
&lt;td data-label="Source label">AMD &amp;ldquo;Max. Operating Temperature (Tjmax)&amp;rdquo;&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Chip">Core i7-14700K&lt;/td>
&lt;td data-label="Figure">100 C&lt;/td>
&lt;td data-label="Source label">Intel Ark &amp;ldquo;TJUNCTION&amp;rdquo; and &amp;ldquo;Max Operating Temperature&amp;rdquo;&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Chip">Core Ultra 7 265K&lt;/td>
&lt;td data-label="Figure">105 C&lt;/td>
&lt;td data-label="Source label">Intel Ark &amp;ldquo;Max Operating Temperature&amp;rdquo;&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Intel says exceeding the Tjunction limit risks damage even with safeguards, and that you want results well below it. AMD&amp;rsquo;s pages add that max boost varies with thermal paste, system cooling and board design. For what temperatures mean day to day, see &lt;a href="https://techfuelhq.com/articles/safe-cpu-temp-2026/">safe CPU temperatures&lt;/a>.&lt;/p>
&lt;h2 id="stress-test-and-what-each-tool-says-it-tests">Stress test, and what each tool says it tests&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Prime95 torture test.&lt;/strong> Its stress.txt calls it a good stress test for the CPU, memory, L1 and L2 caches, CPU cooling and case cooling. It compares results with known-correct ones, so any mismatch is a problem, and it says it is not a disk stress test. The author recommends 6 to 24 hours.&lt;/li>
&lt;li>&lt;strong>OCCT.&lt;/strong> Its CPU + RAM test stresses the whole CPU and memory chain. Its CPU test runs inside the processor caches and generates heat; OCCT says an error there likely comes from the CPU. Both allow per-core testing. The free edition limits tests to one hour.&lt;/li>
&lt;li>&lt;strong>y-cruncher.&lt;/strong> The project says it places heavy load on both the CPU and the memory subsystem and may expose instability others miss. Its developer&amp;rsquo;s page also says the dedicated stress tester has increasingly poor coverage in today&amp;rsquo;s processors. Development is on hiatus but the project says it will be maintained; release 0.8.7 is dated November 23, 2025.&lt;/li>
&lt;li>&lt;strong>Intel XTU stress test.&lt;/strong> Intel suggests 5 minutes for a quick check, 30 minutes for solid stability, and 3 to 5 hours or longer to validate a 24/7 setting.&lt;/li>
&lt;li>&lt;strong>Your real workload.&lt;/strong> Intel&amp;rsquo;s BIOS guide says to choose the stability software that most closely mirrors how you use the system.&lt;/li>
&lt;/ul>
&lt;p>CoreCycler&amp;rsquo;s readme says SSE loads let a core boost higher than AVX loads, so it can expose instability AVX misses, and that you should test both. If the system fails to restart or crashes after a change, Intel&amp;rsquo;s BIOS guide says to go back into the BIOS and return to the last known viable settings.&lt;/p>
&lt;h2 id="back-out-with-a-cmos-clear">Back out with a CMOS clear&lt;/h2>
&lt;p>If the system will not boot, power off, unplug it and clear CMOS. ASUS documents a Clear CMOS button held for about 5 to 10 seconds, shorting the CLRTC pins for about 5 to 10 seconds, or removing the CMOS battery. My B650-A manual has a CLRTC header and warns not to leave a jumper on it, which would cause a boot failure. ASUS says clearing erases the date, time, BIOS password and setup parameters, so you will have to re-enter any BIOS settings you had changed. After the reset, press F1, then F5 for Load Optimized Defaults, then F10 to save. The B650-A also has a CPU Over Voltage jumper that defaults to disabled; I would leave it there, since ASUS describes it only as allowing higher CPU voltage depending on the CPU. If a clear does not help, work through the &lt;a href="https://techfuelhq.com/articles/pc-wont-post-2026/">no-POST checklist&lt;/a> and the &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">diagnostic workbench&lt;/a>.&lt;/p>
&lt;h2 id="the-risks-plainly">The risks, plainly&lt;/h2>
&lt;p>AMD&amp;rsquo;s notice says users assume all risks, including failed or damaged hardware, lower performance and data loss or corruption. Intel says tuning can reduce stability, security, performance and the life of the processor and other components. Neither vendor publishes a voltage that is safe for a given chip. The only voltage figure in the Intel documents I read is the 1.4 V ceiling for air or liquid cooling, from a generic guide. If a number you find in a forum is not in the vendor&amp;rsquo;s documents, treat it as one person&amp;rsquo;s silicon.&lt;/p></description></item><item><title>Ollama Alternatives in 2026: Seven Local LLM Runtimes Compared</title><link>https://techfuelhq.com/self-hosted/ollama-alternatives-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/self-hosted/ollama-alternatives-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;p>Ollama is still maintained, so the reason to leave is never &amp;ldquo;it&amp;rsquo;s dead&amp;rdquo;. On 2026-11-17 its repository was not archived and had been updated that day. Move only when one of the things below applies to you, and pick the replacement by the job.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">If you want&lt;/th>
&lt;th scope="col">Use&lt;/th>
&lt;th scope="col">The documented reason&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="If you want">A lean server you script, with the engine&amp;rsquo;s own flags&lt;/td>
&lt;td data-label="Use">llama.cpp (&lt;code>llama-server&lt;/code>)&lt;/td>
&lt;td data-label="The documented reason">OpenAI-compatible routes, parallel decoding, continuous batching and a model router are in its server README&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="If you want">A desktop app with a model browser&lt;/td>
&lt;td data-label="Use">LM Studio, or Jan if you want open source&lt;/td>
&lt;td data-label="The documented reason">LM Studio&amp;rsquo;s app is closed source; Jan&amp;rsquo;s README says Apache 2.0&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="If you want">Concurrent requests from many clients, on Linux&lt;/td>
&lt;td data-label="Use">vLLM&lt;/td>
&lt;td data-label="The documented reason">Continuous batching is its headline feature; no native Windows&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="If you want">One API for text, speech, images and embeddings&lt;/td>
&lt;td data-label="Use">LocalAI&lt;/td>
&lt;td data-label="The documented reason">Its README lists more than 80 backends behind OpenAI-format endpoints&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="If you want">Chat, story or roleplay front ends in one file&lt;/td>
&lt;td data-label="Use">KoboldCpp or TextGen&lt;/td>
&lt;td data-label="The documented reason">Both bundle a web UI and an OpenAI-compatible API&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The sections below give each project&amp;rsquo;s licence, platforms, model formats, API and GPU support as its own documentation states them. I did not run any of them for this page. The speed numbers I do quote come from the three measured comparisons I already published on one RTX 5080, linked in each section, and I give their conditions every time.&lt;/p>
&lt;h2 id="what-ollama-is-and-why-people-move-off-it">What Ollama is, and why people move off it&lt;/h2>
&lt;p>Ollama&amp;rsquo;s README opens with &amp;ldquo;Start building with open models&amp;rdquo; and shows a CLI (&lt;code>ollama run gemma4&lt;/code>) plus a REST API on &lt;code>localhost:11434&lt;/code>. It runs on macOS, Windows, Linux and in an official Docker image, is MIT licensed per its repository, and lists llama.cpp as its supported backend. Its docs describe an OpenAI-compatible API, import of Safetensors and GGUF models through a Modelfile, and GPU support for Nvidia (compute capability 5.0 and up with driver 550 or newer, and driver 570 or newer for compute capability 5.0 through 6.2), AMD through ROCm, Apple&amp;rsquo;s Metal, and Vulkan on Windows and Linux.&lt;/p>
&lt;p>I found five reasons in the documentation that could justify a move. None of them is a verdict on Ollama.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Concurrency defaults.&lt;/strong> Ollama&amp;rsquo;s FAQ says &lt;code>OLLAMA_NUM_PARALLEL&lt;/code>, the number of parallel requests each model handles, defaults to 1, and that the RAM needed scales with that number times &lt;code>OLLAMA_CONTEXT_LENGTH&lt;/code>. llama.cpp&amp;rsquo;s server README lists parallel decoding with multi-user support and continuous batching, vLLM&amp;rsquo;s README lists continuous batching, and LM Studio&amp;rsquo;s docs say Max Concurrent Predictions defaults to 4.&lt;/li>
&lt;li>&lt;strong>Context window.&lt;/strong> Ollama&amp;rsquo;s context-length page sets the default by VRAM: 4k under 24 GiB, 32k from 24 to 48 GiB, 256k at 48 GiB or more (its FAQ gives 4096 tokens as the default and the &lt;code>OLLAMA_CONTEXT_LENGTH&lt;/code> override). llama.cpp&amp;rsquo;s &lt;code>--ctx-size&lt;/code> defaults to 0, meaning the size is loaded from the model. On my LM Studio comparison, an Ollama app context slider left at 256k (clamped to the model&amp;rsquo;s 131,072 maximum) took Llama 3.2 3B from 351 to 102 tokens per second on a 16 GB RTX 5080, so check this setting before you blame the runtime.&lt;/li>
&lt;li>&lt;strong>The cloud features.&lt;/strong> Ollama&amp;rsquo;s docs describe cloud models and web search, and the FAQ gives a switch to turn them off: &lt;code>OLLAMA_NO_CLOUD=1&lt;/code>, or &lt;code>disable_ollama_cloud&lt;/code> in &lt;code>~/.ollama/server.json&lt;/code>. If you want a runtime with no hosted side at all, that setting does it inside Ollama. Moving does not obviously help: LM Studio&amp;rsquo;s pricing page and Jan&amp;rsquo;s README both describe optional hosted or remote models too.&lt;/li>
&lt;li>&lt;strong>Formats.&lt;/strong> Ollama imports GGUF and Safetensors. If your model ships as something else, vLLM&amp;rsquo;s docs cover Hugging Face models and quantization formats such as AWQ and GPTQ, and TextGen&amp;rsquo;s README lists ExLlamaV3 and Transformers backends.&lt;/li>
&lt;li>&lt;strong>Open-source GUI.&lt;/strong> If you want a desktop app and want the source, that is Jan, not LM Studio.&lt;/li>
&lt;/ol>
&lt;p>If none of those describes you, stay.&lt;/p>
&lt;h2 id="llamacpp-and-its-server">llama.cpp and its server&lt;/h2>
&lt;p>llama.cpp&amp;rsquo;s README calls it &amp;ldquo;LLM inference in C/C++&amp;rdquo; and states the goal as minimal setup and state-of-the-art performance on a wide range of hardware. It is MIT licensed. The README&amp;rsquo;s quick start now uses &lt;code>llama cli&lt;/code> and &lt;code>llama serve&lt;/code>, with Docker images and pre-built releases alongside; the server README and its Docker examples still call the binary &lt;code>llama-server&lt;/code>.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Model formats:&lt;/strong> GGUF. The models doc says llama.cpp requires GGUF and that other formats convert with the repo&amp;rsquo;s &lt;code>convert_*.py&lt;/code> scripts. &lt;code>-hf &amp;lt;user&amp;gt;/&amp;lt;model&amp;gt;&lt;/code> downloads a GGUF from Hugging Face directly.&lt;/li>
&lt;li>&lt;strong>OpenAI-compatible API:&lt;/strong> yes. The server README lists chat completions, responses and embeddings routes, plus an Anthropic Messages-compatible route, and says that while no strong claims of compatibility are made, it supports many apps.&lt;/li>
&lt;li>&lt;strong>Model switching:&lt;/strong> a router mode (&lt;code>--models-dir&lt;/code>, &lt;code>--models-max&lt;/code>, default 4 loaded at once, autoload on by default) is documented. It is the nearest thing I found to choosing the model by name in each request, and you configure it yourself.&lt;/li>
&lt;li>&lt;strong>GPU:&lt;/strong> the build docs cover CUDA (Nvidia), HIP (AMD, with ROCm), Vulkan, SYCL (Intel), Metal (on by default on macOS), CPU and several other backends.&lt;/li>
&lt;li>&lt;strong>Suits:&lt;/strong> someone comfortable with flags who wants the engine without a model library in the way.&lt;/li>
&lt;/ul>
&lt;p>My measured comparison, &lt;a href="https://techfuelhq.com/self-hosted/ollama-vs-llamacpp-rtx-5080-2026/">Ollama vs llama.cpp on an RTX 5080&lt;/a>, used Ollama 0.32.1 against llama.cpp b10507 (&lt;code>llama-server&lt;/code>), full GPU offload, 4096 context, 256-token generations, decode medians of five runs:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Model&lt;/th>
&lt;th scope="col" style="text-align: right">Ollama decode&lt;/th>
&lt;th scope="col" style="text-align: right">llama.cpp decode&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Model">Llama 3.2 3B&lt;/td>
&lt;td style="text-align: right" data-label="Ollama decode">319 t/s&lt;/td>
&lt;td style="text-align: right" data-label="llama.cpp decode">338 t/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Model">Qwen 2.5 14B&lt;/td>
&lt;td style="text-align: right" data-label="Ollama decode">99.4 t/s&lt;/td>
&lt;td style="text-align: right" data-label="llama.cpp decode">101.4 t/s&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The page also reports Ollama prefilling 4-7% faster at prompts of about 420 tokens, and a portability catch: Ollama&amp;rsquo;s gpt-oss file is tagged &amp;ldquo;gptoss&amp;rdquo;, which upstream llama.cpp refuses, so that comparison used different conversions of the model.&lt;/p>
&lt;h2 id="lm-studio">LM Studio&lt;/h2>
&lt;p>LM Studio is a desktop application, not open source. Its App Terms of Service (dated August 23, 2026) grant a non-exclusive licence for personal or internal business use and describe the software&amp;rsquo;s source code as a trade secret. Its homepage now markets the app as LM Studio Bionic, an agent for open models, and its pricing page lists a free plan that includes local models plus paid plans for hosted inference.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Platforms:&lt;/strong> Apple Silicon Macs on macOS 14 or newer (Intel Macs are not supported), Windows on x64 and ARM, and Linux on x64 and ARM64 as an AppImage.&lt;/li>
&lt;li>&lt;strong>Model formats:&lt;/strong> GGUF through llama.cpp on all three platforms; MLX models as well on Apple Silicon.&lt;/li>
&lt;li>&lt;strong>OpenAI-compatible API:&lt;/strong> yes: &lt;code>/v1/responses&lt;/code>, &lt;code>/v1/chat/completions&lt;/code>, &lt;code>/v1/completions&lt;/code>, &lt;code>/v1/embeddings&lt;/code> and &lt;code>/v1/models&lt;/code>, plus an Anthropic-compatible route. The docs&amp;rsquo; examples use port 1234.&lt;/li>
&lt;li>&lt;strong>Headless:&lt;/strong> &lt;code>llmster&lt;/code> is documented as the GUI-free version, started with &lt;code>lms daemon up&lt;/code>.&lt;/li>
&lt;li>&lt;strong>GPU:&lt;/strong> the system requirements page recommends at least 4 GB of dedicated VRAM on Windows. It does not enumerate GPU vendors.&lt;/li>
&lt;li>&lt;strong>Suits:&lt;/strong> a model browser and per-model tuning in a GUI, with the server a click away.&lt;/li>
&lt;/ul>
&lt;p>On my &lt;a href="https://techfuelhq.com/self-hosted/ollama-vs-lm-studio-rtx-5080-2026/">Ollama vs LM Studio&lt;/a> bench (Ollama 0.32.15, LM Studio 0.4.21, one RTX 5080, context 4096, full GPU offload, temperature 0, seed 42, one serving slot, medians of five fresh-prompt runs), Ollama decoded 350.5 t/s and LM Studio 316.0 t/s on Llama 3.2 3B; on Qwen 2.5 14B it was 102.2 against 97.6. LM Studio prefilled faster on both at prompts of about 450 tokens, 20,337 against 17,862 t/s on the 3B model. Those are different Ollama and llama.cpp builds from the table above, so do not compare numbers across the two captures.&lt;/p>
&lt;h2 id="vllm">vLLM&lt;/h2>
&lt;p>vLLM&amp;rsquo;s README describes &amp;ldquo;a fast and easy-to-use library for LLM inference and serving&amp;rdquo;, built around PagedAttention, continuous batching and chunked prefill. The repository&amp;rsquo;s licence is Apache 2.0.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Platforms:&lt;/strong> the GPU install docs list Linux as the OS, Python 3.11 to 3.14, and state that vLLM does not support Windows natively; they point to WSL or community forks. The quickstart adds macOS on Apple Silicon through vLLM-Metal.&lt;/li>
&lt;li>&lt;strong>Model formats:&lt;/strong> Hugging Face models, with quantization including FP8, GPTQ/AWQ and others. The GGUF page says GGUF support is &amp;ldquo;highly experimental and under-optimized&amp;rdquo; and now lives in a separate plugin.&lt;/li>
&lt;li>&lt;strong>OpenAI-compatible API:&lt;/strong> yes, plus an Anthropic Messages API.&lt;/li>
&lt;li>&lt;strong>GPU:&lt;/strong> NVIDIA GPUs with compute capability 7.5 or higher, AMD GPUs (the docs list MI200, MI300, MI350, Radeon RX 7900 and 9000 series, and Ryzen AI parts, with ROCm 6.3 or newer and ROCm 7 for some), Intel GPUs, and several other accelerators.&lt;/li>
&lt;li>&lt;strong>Suits:&lt;/strong> a Linux box serving several clients at once. For one person chatting from a Windows desktop it is the wrong tool.&lt;/li>
&lt;/ul>
&lt;p>I have not measured vLLM on my RTX 5080, so there is no number for it here. The &lt;a href="https://techfuelhq.com/self-hosted/vllm-vs-ollama-2026/">vLLM vs Ollama&lt;/a> page works from the documentation for the same reason.&lt;/p>
&lt;h2 id="localai">LocalAI&lt;/h2>
&lt;p>LocalAI&amp;rsquo;s README describes it as running open models &amp;ldquo;for chat, images, speech and video on your own machines&amp;rdquo;, with an API in the OpenAI and Anthropic formats and more than 80 backends. It is MIT licensed, and the README says the name and logo are not covered by that licence.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Platforms and install:&lt;/strong> the README lists an install script for Linux and macOS on Apple Silicon, a container (Docker, podman), and a desktop app for macOS and Linux that the README says arrives with its next release. It does not list a native Windows installer.&lt;/li>
&lt;li>&lt;strong>Model formats and sources:&lt;/strong> models from its gallery, Hugging Face GGUF files, the Ollama registry (&lt;code>ollama://&lt;/code>) and OCI registries. Backends include llama.cpp, vLLM, MLX and whisper.cpp.&lt;/li>
&lt;li>&lt;strong>GPU:&lt;/strong> NVIDIA (CUDA 12 and 13), AMD (ROCm), Intel (oneAPI/SYCL), Apple Silicon, Vulkan, NVIDIA Jetson, or CPU only.&lt;/li>
&lt;li>&lt;strong>Suits:&lt;/strong> a homelab that wants one endpoint for text, speech and image jobs. The README also notes that some features it describes need a development build, so read it against the version you install.&lt;/li>
&lt;/ul>
&lt;h2 id="jan">Jan&lt;/h2>
&lt;p>Jan&amp;rsquo;s README calls it an open-source ChatGPT replacement that runs models locally, and the README&amp;rsquo;s licence section says Apache 2.0. The LICENSE file in the repository is an Apache 2.0 notice, though GitHub&amp;rsquo;s detector does not label it.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Platforms:&lt;/strong> Windows, macOS and Linux desktop builds. Its README lists GPU support for NVIDIA, AMD and Intel Arc on Windows and says acceleration is available on Linux.&lt;/li>
&lt;li>&lt;strong>Model formats:&lt;/strong> GGUF through its llama.cpp engine, which can also import a local GGUF file in place. MLX models on Apple Silicon, which Jan&amp;rsquo;s docs label experimental, with no embeddings and some newer architectures failing to load.&lt;/li>
&lt;li>&lt;strong>OpenAI-compatible API:&lt;/strong> yes, a local server at &lt;code>127.0.0.1:1337&lt;/code> by default, with an optional API key and a setting to listen on &lt;code>0.0.0.0&lt;/code>.&lt;/li>
&lt;li>&lt;strong>Also:&lt;/strong> MCP integration, and connections to hosted providers such as OpenAI and Anthropic.&lt;/li>
&lt;li>&lt;strong>Suits:&lt;/strong> a desktop chat app with the source open, that can also act as a local server.&lt;/li>
&lt;/ul>
&lt;h2 id="koboldcpp">KoboldCpp&lt;/h2>
&lt;p>KoboldCpp calls itself free and open-source software for running GGUF models on your own computer, built on llama.cpp. It is AGPL-3.0 licensed, with bundled components under their own licences.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Platforms:&lt;/strong> a single executable for Windows, Linux (x64) and macOS (Apple Silicon); Intel Macs need a source build.&lt;/li>
&lt;li>&lt;strong>Model formats:&lt;/strong> GGUF.&lt;/li>
&lt;li>&lt;strong>API:&lt;/strong> an OpenAI-compatible API at &lt;code>localhost:5001/v1&lt;/code>, KoboldAI&amp;rsquo;s own API, and endpoints compatible with Ollama.&lt;/li>
&lt;li>&lt;strong>GPU:&lt;/strong> &lt;code>--usecuda&lt;/code> for Nvidia only, &lt;code>--usevulkan&lt;/code> for AMD, Nvidia and Intel; a CPU-only mode as well.&lt;/li>
&lt;li>&lt;strong>Suits:&lt;/strong> chat, story writing and roleplay, which its bundled KoboldAI Lite web UI is built for. The README also lists image, video, speech and music generation.&lt;/li>
&lt;/ul>
&lt;p>The README warns that &lt;code>koboldcpp.com&lt;/code> is a fake site and that the only official downloads are the GitHub releases page and koboldcpp.net.&lt;/p>
&lt;h2 id="textgen-formerly-text-generation-webui">TextGen (formerly text-generation-webui)&lt;/h2>
&lt;p>text-generation-webui now lives at &lt;code>github.com/oobabooga/textgen&lt;/code>: the old repository URL answered with a permanent redirect when I requested it, and the README is headed &amp;ldquo;TextGen&amp;rdquo;. It is AGPL-3.0 licensed. The latest GitHub release I could see was v4.9, dated May 20, 2026, and the repository&amp;rsquo;s last push was August 17, 2026, while Ollama, llama.cpp, vLLM, LocalAI, Jan and KoboldCpp all had a push on 2026-11-17, so check it is keeping up with the models you want.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Platforms:&lt;/strong> portable builds for Linux, Windows and macOS with CUDA, Vulkan, ROCm and CPU-only options.&lt;/li>
&lt;li>&lt;strong>Model formats:&lt;/strong> GGUF through llama.cpp in the portable build. The full installation adds ExLlamaV3 and Transformers backends, which take multi-file Safetensors and EXL3 models.&lt;/li>
&lt;li>&lt;strong>OpenAI-compatible API:&lt;/strong> yes, OpenAI and Anthropic-compatible chat, completions and messages endpoints. On the manual install the README launches the server with &lt;code>--api&lt;/code>.&lt;/li>
&lt;li>&lt;strong>Suits:&lt;/strong> someone who wants a chat UI and options to train a LoRA or swap between several backends in one program.&lt;/li>
&lt;/ul>
&lt;h2 id="how-to-choose-and-what-to-do-first">How to choose, and what to do first&lt;/h2>
&lt;p>I would work through it in this order:&lt;/p>
&lt;ol>
&lt;li>Check Ollama&amp;rsquo;s context and parallelism settings and, if the cloud is the issue, &lt;code>OLLAMA_NO_CLOUD=1&lt;/code>. Those are one-line changes.&lt;/li>
&lt;li>If you want a GUI, install LM Studio or Jan next to Ollama and point it at a GGUF you already have. My LM Studio page ran both on ports 11434 and 1234 at once with two 3B models loaded.&lt;/li>
&lt;li>If you want the engine itself, run llama.cpp&amp;rsquo;s server. It loads GGUF files, either a local path or &lt;code>-hf&lt;/code> from Hugging Face. Ollama&amp;rsquo;s docs say where models are stored but, in what I read, not that llama.cpp can load them from there. My own comparison did it: &lt;code>ollama show &amp;lt;model&amp;gt; --modelfile&lt;/code> gave the path, and llama-server loaded the Llama 3.2 3B and Qwen 2.5 14B blobs from it, while the gpt-oss:20b blob was refused. That is one machine and three models, so try it on yours before you delete anything.&lt;/li>
&lt;li>If you serve many clients, run vLLM on Linux.&lt;/li>
&lt;/ol>
&lt;p>Before you swap anything, check what fits in your card with the &lt;a href="https://techfuelhq.com/tools/llm-vram-calculator/">LLM VRAM calculator&lt;/a> and sanity-check expected speed with the &lt;a href="https://techfuelhq.com/tools/llm-speed-calculator/">LLM speed calculator&lt;/a>; the &lt;a href="https://techfuelhq.com/articles/local-llm-by-gpu-vram-2026/">VRAM-tier guide&lt;/a> maps model sizes to cards. If you keep Ollama and run it in a container, the &lt;a href="https://techfuelhq.com/tutorials/ollama-docker-gpu-2026/">Ollama in Docker guide&lt;/a> covers binding it to loopback.&lt;/p></description></item><item><title>Proxmox Default Port: 8006, Plus the Other Ports Proxmox Documents</title><link>https://techfuelhq.com/homelab/proxmox-default-port-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/proxmox-default-port-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;p>The Proxmox VE web interface is on &lt;strong>TCP port 8006&lt;/strong>. Open &lt;code>https://your-host-or-ip:8006&lt;/code>, using the IP address you gave the installer, and log in as &lt;code>root&lt;/code> with the realm set to PAM. Proxmox&amp;rsquo;s own installation chapter gives exactly that form: the installer&amp;rsquo;s IP address plus port 8006, for example &lt;code>https://youripaddress:8006&lt;/code>.&lt;/p>
&lt;p>The other two Proxmox products with a web interface use different ports:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Product&lt;/th>
&lt;th scope="col">Web interface port&lt;/th>
&lt;th scope="col">URL form from its docs&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Product">Proxmox VE&lt;/td>
&lt;td data-label="Web interface port">TCP 8006&lt;/td>
&lt;td data-label="URL form from its docs">&lt;code>https://youripaddress:8006&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Product">Proxmox Backup Server&lt;/td>
&lt;td data-label="Web interface port">TCP 8007&lt;/td>
&lt;td data-label="URL form from its docs">&lt;code>https://youripaddress:8007&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Product">Proxmox Datacenter Manager&lt;/td>
&lt;td data-label="Web interface port">TCP 8443&lt;/td>
&lt;td data-label="URL form from its docs">&lt;code>https://youripaddress:8443&lt;/code>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>If you are following the install from scratch, &lt;a href="https://techfuelhq.com/articles/how-to-install-proxmox-ve-2026/">how to install Proxmox VE&lt;/a> and the &lt;a href="https://techfuelhq.com/articles/proxmox-mini-pc-setup/">mini PC setup walkthrough&lt;/a> cover the steps before that browser tab.&lt;/p>
&lt;h2 id="every-port-proxmox-ve-documents">Every port Proxmox VE documents&lt;/h2>
&lt;p>Proxmox VE&amp;rsquo;s firewall chapter has a section called &amp;ldquo;Ports used by Proxmox VE&amp;rdquo;. This is that list, with the other ports the manual names elsewhere added underneath.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Port&lt;/th>
&lt;th scope="col">Protocol&lt;/th>
&lt;th scope="col">What it is&lt;/th>
&lt;th scope="col">Where the docs say so&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Port">8006&lt;/td>
&lt;td data-label="Protocol">TCP&lt;/td>
&lt;td data-label="What it is">Web interface (HTTP/1.1 over TLS) and the API&lt;/td>
&lt;td data-label="Where the docs say so">Firewall chapter; pveproxy&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">5900-5999&lt;/td>
&lt;td data-label="Protocol">TCP&lt;/td>
&lt;td data-label="What it is">VNC web console (WebSocket)&lt;/td>
&lt;td data-label="Where the docs say so">Firewall chapter&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">3128&lt;/td>
&lt;td data-label="Protocol">TCP&lt;/td>
&lt;td data-label="What it is">SPICE proxy&lt;/td>
&lt;td data-label="Where the docs say so">Firewall chapter&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">22&lt;/td>
&lt;td data-label="Protocol">TCP&lt;/td>
&lt;td data-label="What it is">sshd, &amp;ldquo;used for cluster actions&amp;rdquo;&lt;/td>
&lt;td data-label="Where the docs say so">Firewall chapter; clustering requirements&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">111&lt;/td>
&lt;td data-label="Protocol">UDP&lt;/td>
&lt;td data-label="What it is">rpcbind&lt;/td>
&lt;td data-label="Where the docs say so">Firewall chapter&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">25&lt;/td>
&lt;td data-label="Protocol">TCP, outgoing&lt;/td>
&lt;td data-label="What it is">sendmail&lt;/td>
&lt;td data-label="Where the docs say so">Firewall chapter&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">5405-5412&lt;/td>
&lt;td data-label="Protocol">UDP&lt;/td>
&lt;td data-label="What it is">corosync cluster traffic&lt;/td>
&lt;td data-label="Where the docs say so">Firewall chapter; clustering requirements&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">60000-60050&lt;/td>
&lt;td data-label="Protocol">TCP&lt;/td>
&lt;td data-label="What it is">Live migration (VM memory and local-disk data)&lt;/td>
&lt;td data-label="Where the docs say so">Firewall chapter&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">5403&lt;/td>
&lt;td data-label="Protocol">TCP&lt;/td>
&lt;td data-label="What it is">Default port of the qnetd server, when you use an external QDevice vote&lt;/td>
&lt;td data-label="Where the docs say so">Clustering chapter&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">80&lt;/td>
&lt;td data-label="Protocol">TCP&lt;/td>
&lt;td data-label="What it is">Built-in web server for Let&amp;rsquo;s Encrypt http-01 certificate validation&lt;/td>
&lt;td data-label="Where the docs say so">System administration chapter&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">85 (127.0.0.1)&lt;/td>
&lt;td data-label="Protocol">TCP&lt;/td>
&lt;td data-label="What it is">pvedaemon, the privileged API daemon; local only&lt;/td>
&lt;td data-label="Where the docs say so">Service daemons chapter&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Three notes on that table:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>The cluster ports only matter between nodes.&lt;/strong> The clustering chapter&amp;rsquo;s requirements are UDP 5405-5412 for corosync and an SSH connection on TCP 22 between all nodes. The migration range is for moving guests: if you move guests between hosts, &lt;a href="https://techfuelhq.com/tutorials/proxmox-clustering-ha-2026/">Proxmox clustering and HA&lt;/a> and &lt;a href="https://techfuelhq.com/tutorials/proxmox-migrate-vm-without-cluster-2026/">moving a VM without a cluster&lt;/a> are the pages that use it.&lt;/li>
&lt;li>&lt;strong>Port 85 is not reachable from outside.&lt;/strong> The manual says pvedaemon &amp;ldquo;listens to a local address only, so you cannot access it from outside&amp;rdquo;. The web interface on 8006 is served by pveproxy, which forwards anything that needs more privileges to pvedaemon.&lt;/li>
&lt;li>&lt;strong>Port 80 is only for certificates.&lt;/strong> The http-01 plugin needs port 80 of the node reachable from the internet and no other listener on it. If you can&amp;rsquo;t expose port 80, the docs also describe a dns-01 plugin.&lt;/li>
&lt;/ul>
&lt;h2 id="proxmox-backup-server-and-datacenter-manager">Proxmox Backup Server and Datacenter Manager&lt;/h2>
&lt;p>Both products publish less than Proxmox VE does. I searched the documentation pages of each for port statements; this is everything I found.&lt;/p>
&lt;p>&lt;strong>Proxmox Backup Server (documentation 4.2.11-1)&lt;/strong>&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Port&lt;/th>
&lt;th scope="col">What it is&lt;/th>
&lt;th scope="col">Where the docs say so&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Port">TCP 8007&lt;/td>
&lt;td data-label="What it is">Web interface and API over HTTPS (the proxmox-backup-proxy daemon)&lt;/td>
&lt;td data-label="Where the docs say so">Installation; Graphical User Interface; Host System Administration&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">127.0.0.1:82&lt;/td>
&lt;td data-label="What it is">Management API of the proxmox-backup daemon, local only&lt;/td>
&lt;td data-label="Where the docs say so">Host System Administration&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">8007 (default)&lt;/td>
&lt;td data-label="What it is">The &lt;code>--port&lt;/code> option of the client tools, and the &lt;code>port&lt;/code> option when Proxmox VE adds a Backup Server as storage&lt;/td>
&lt;td data-label="Where the docs say so">Backup Client Usage; Proxmox VE administration guide&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">TCP 80&lt;/td>
&lt;td data-label="What it is">Built-in web server for ACME http-01 validation&lt;/td>
&lt;td data-label="Where the docs say so">Host System Administration&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The Backup Server docs have no firewall port list like the one in Proxmox VE. They do say that installing it directly on the hypervisor is not recommended: it is safer to use a separate physical server, so that if the hypervisor fails you can still reach the backups.&lt;/p>
&lt;p>&lt;strong>Proxmox Datacenter Manager (documentation 1.1.9)&lt;/strong>&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Port&lt;/th>
&lt;th scope="col">What it is&lt;/th>
&lt;th scope="col">Where the docs say so&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Port">TCP 8443&lt;/td>
&lt;td data-label="What it is">Web interface and API over HTTPS (the proxmox-datacenter-api daemon)&lt;/td>
&lt;td data-label="Where the docs say so">Installation; Web Interface; Host System Administration&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">8443 (default)&lt;/td>
&lt;td data-label="What it is">The &lt;code>--port&lt;/code> default of the command-line client&lt;/td>
&lt;td data-label="Where the docs say so">Command Syntax&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Port">TCP 80&lt;/td>
&lt;td data-label="What it is">Built-in web server for ACME http-01 validation&lt;/td>
&lt;td data-label="Where the docs say so">Host System Administration&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The privileged Datacenter Manager daemon uses a restricted UNIX socket rather than a port, so there is nothing to open there. One discrepancy: the introduction&amp;rsquo;s technology-stack paragraph says communication &amp;ldquo;occurs over TCP port 443 (HTTPS)&amp;rdquo;. Its installation page, web interface page, daemon description and client default all say 8443, so I&amp;rsquo;d treat 8443 as the answer and check with &lt;code>ss -tlnp&lt;/code> on your own install if the difference matters to you.&lt;/p>
&lt;h2 id="what-proxmox-says-about-changing-or-proxying-port-8006">What Proxmox says about changing or proxying port 8006&lt;/h2>
&lt;p>&lt;strong>Changing the port.&lt;/strong> I searched the administration guide and the pveproxy manual page for a setting that moves the web interface off 8006 and did not find one. What pveproxy does document, in &lt;code>/etc/default/pveproxy&lt;/code>:&lt;/p>
&lt;ul>
&lt;li>&lt;code>LISTEN_IP&lt;/code> binds pveproxy and spiceproxy to one address instead of the wildcard address. The docs say it can restrict the socket to an internal interface for less exposure, and that it is not recommended on clustered systems, because the nodes need access to pveproxy to communicate. Applying it takes a reboot or &lt;code>systemctl restart pveproxy.service spiceproxy.service&lt;/code>, and the docs warn a restart can interrupt long-running workers such as a console or shell.&lt;/li>
&lt;li>&lt;code>ALLOW_FROM&lt;/code>, &lt;code>DENY_FROM&lt;/code> and &lt;code>POLICY&lt;/code> set apache2-style access control lists, for example &lt;code>ALLOW_FROM=&amp;quot;10.0.0.1-10.0.0.5,192.168.0.0/22&amp;quot;&lt;/code>. The &lt;a href="https://techfuelhq.com/tools/subnet-cidr-calculator/">subnet calculator&lt;/a> will turn a range into a CIDR if you need one.&lt;/li>
&lt;li>&lt;code>PROXY_REAL_IP_HEADER&lt;/code> makes pveproxy log the client address from a header (for example &lt;code>X-Forwarded-For&lt;/code>) when a proxy sits in front of it.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Proxying it onto 443.&lt;/strong> The Proxmox VE wiki page &amp;ldquo;Web Interface Via Nginx Proxy&amp;rdquo; is the only Proxmox page I found that addresses it, and it is a wiki page rather than the administration guide. Its stated reason is that &amp;ldquo;sometimes there is a firewall restriction that blocks port 8006&amp;rdquo;, and it adds &amp;ldquo;we shouldn&amp;rsquo;t touch the port config in proxmox&amp;rdquo;, so nginx provides the interface on port 443 instead. The 443 server block from that page:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-nginx" data-lang="nginx">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">server&lt;/span> {
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">listen&lt;/span> &lt;span style="color:#ae81ff">443&lt;/span> &lt;span style="color:#e6db74">ssl&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">listen&lt;/span> &lt;span style="color:#e6db74">[::]:443&lt;/span> &lt;span style="color:#e6db74">ssl&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">server_name&lt;/span> &lt;span style="color:#e6db74">_&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">ssl_certificate&lt;/span> &lt;span style="color:#e6db74">/etc/pve/local/pve-ssl.pem&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">ssl_certificate_key&lt;/span> &lt;span style="color:#e6db74">/etc/pve/local/pve-ssl.key&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">proxy_redirect&lt;/span> &lt;span style="color:#66d9ef">off&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">location&lt;/span> &lt;span style="color:#e6db74">/&lt;/span> {
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">proxy_http_version&lt;/span> &lt;span style="color:#ae81ff">1&lt;/span>&lt;span style="color:#e6db74">.1&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">proxy_set_header&lt;/span> &lt;span style="color:#e6db74">Upgrade&lt;/span> $http_upgrade;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">proxy_set_header&lt;/span> &lt;span style="color:#e6db74">Connection&lt;/span> &lt;span style="color:#e6db74">&amp;#34;upgrade&amp;#34;&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">proxy_pass&lt;/span> &lt;span style="color:#e6db74">https://localhost:8006&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">proxy_buffering&lt;/span> &lt;span style="color:#66d9ef">off&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">client_max_body_size&lt;/span> &lt;span style="color:#ae81ff">0&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">proxy_connect_timeout&lt;/span> &lt;span style="color:#e6db74">3600s&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">proxy_read_timeout&lt;/span> &lt;span style="color:#e6db74">3600s&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">proxy_send_timeout&lt;/span> &lt;span style="color:#e6db74">3600s&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">send_timeout&lt;/span> &lt;span style="color:#e6db74">3600s&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> }
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>}
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The page also adds a systemd override so nginx starts only after &lt;code>pve-cluster.service&lt;/code>, because those certificates live under &lt;code>/etc/pve&lt;/code>. Two cautions from the page itself: it says it was tested from Proxmox 3.4 to 6.3, and it was last edited in July 2024. I have not tested it on a current release, so treat it as a starting point. If you would rather have a general reverse proxy than a hand-written nginx file, &lt;a href="https://techfuelhq.com/homelab/caddy-vs-nginx-proxy-manager-vs-traefik-2026/">Caddy, Nginx Proxy Manager and Traefik compared&lt;/a> covers the options. If the real reason you want 443 is reaching the interface from outside your house, my &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale remote access guide&lt;/a> covers that separately; I&amp;rsquo;m not drawing on Proxmox&amp;rsquo;s docs for it.&lt;/p>
&lt;h2 id="the-firewall-and-8006">The firewall and 8006&lt;/h2>
&lt;p>Proxmox VE&amp;rsquo;s firewall is &lt;strong>off by default&lt;/strong>. The chapter says it is completely disabled by default; you enable it cluster-wide with &lt;code>enable: 1&lt;/code> in the &lt;code>[OPTIONS]&lt;/code> section of &lt;code>/etc/pve/firewall/cluster.fw&lt;/code> (or from the web interface). The docs warn to open an SSH connection to a host before enabling it, so you still have access if something goes wrong.&lt;/p>
&lt;p>When it is on, traffic to all hosts is blocked by default, with exceptions for traffic coming from the local network to the web interface, SSH and other important services. The chapter&amp;rsquo;s default-rules list says that, even with the input policy on DROP or REJECT, TCP from management hosts is still allowed to 8006, 5900-5999, 3128, 22 and 60000-60050, along with UDP 5405-5412 in the cluster network. To administer a host from a different network, you need to write rules allowing those remote addresses to port 8006, or add them to the &lt;code>management&lt;/code> IP set, which the docs say is allowed to do the normal management tasks (web interface, VNC, SPICE, SSH) and applies to host firewalls only.&lt;/p>
&lt;h2 id="why-the-browser-warns-about-the-certificate">Why the browser warns about the certificate&lt;/h2>
&lt;p>Proxmox&amp;rsquo;s documentation explains the warning rather than leaving it to guesswork. Each Proxmox VE cluster creates its own self-signed certificate authority and signs a certificate for each node. By default the web interface uses the node certificate at &lt;code>/etc/pve/nodes/NODENAME/pve-ssl.pem&lt;/code>, &amp;ldquo;signed by the cluster CA and therefore not automatically trusted by browsers and operating systems&amp;rdquo;. Backup Server and Datacenter Manager each generate a self-signed certificate too.&lt;/p>
&lt;p>What the Proxmox VE docs give you for removing the warning:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Trust the cluster CA.&lt;/strong> Copy &lt;code>/etc/pve/pve-root-ca.pem&lt;/code> from any cluster node (for example with &lt;code>scp&lt;/code>) and import it into the operating system or browser trust store. The docs say there is no API or web interface endpoint to download it.&lt;/li>
&lt;li>&lt;strong>Upload a certificate&lt;/strong> from a commercial CA through the web interface; the key must not be password protected.&lt;/li>
&lt;li>&lt;strong>Use ACME (Let&amp;rsquo;s Encrypt)&lt;/strong>, which is built into the API and web interface. It validates with a built-in web server on port 80 or with a DNS plugin.&lt;/li>
&lt;/ol>
&lt;p>The docs warn not to replace or hand-edit the automatically generated node certificate files or the cluster CA files. Backup Server and Datacenter Manager offer the same three options for their own certificates, and Datacenter Manager&amp;rsquo;s remotes chapter adds one catch: it pins the fingerprint of a self-signed remote&amp;rsquo;s certificate, so if that remote renews its certificate, connections fail until you update the stored fingerprint.&lt;/p></description></item><item><title>Home Assistant Door Sensor: Zigbee, Z-Wave, Thread or Bluetooth? (2026)</title><link>https://techfuelhq.com/homelab/home-assistant-door-sensor-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/home-assistant-door-sensor-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;p>Pick the protocol your Home Assistant machine already has a radio for, then buy a sensor in that protocol. The radio and the software behind it are the commitment; the sensor is the easier part to swap later.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">You already run&lt;/th>
&lt;th scope="col">What Home Assistant needs&lt;/th>
&lt;th scope="col">A sensor to look at&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="You already run">A Zigbee coordinator (ZHA or Zigbee2MQTT)&lt;/td>
&lt;td data-label="What Home Assistant needs">Nothing more with ZHA; an MQTT broker with Zigbee2MQTT&lt;/td>
&lt;td data-label="A sensor to look at">Sonoff SNZB-04P&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="You already run">A Z-Wave adapter with the Z-Wave JS app&lt;/td>
&lt;td data-label="What Home Assistant needs">Nothing more&lt;/td>
&lt;td data-label="A sensor to look at">Aeotec Door/Window Sensor 7&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="You already run">A Thread border router and the Matter Server app&lt;/td>
&lt;td data-label="What Home Assistant needs">Nothing more&lt;/td>
&lt;td data-label="A sensor to look at">Aqara P2 or Eve Door &amp;amp; Window&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="You already run">A Bluetooth adapter or ESPHome proxy&lt;/td>
&lt;td data-label="What Home Assistant needs">Nothing more&lt;/td>
&lt;td data-label="A sensor to look at">Shelly BLU Door/Window ZB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="You already run">None of these&lt;/td>
&lt;td data-label="What Home Assistant needs">A coordinator first&lt;/td>
&lt;td data-label="A sensor to look at">See the &lt;a href="https://techfuelhq.com/homelab/home-assistant-connect-zbt-2-2026/">ZBT-2 guide&lt;/a>, then a Zigbee sensor&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>If you have no radio yet, Home Assistant&amp;rsquo;s ZHA page says the Home Assistant Connect ZBT-2 is the recommended coordinator for a first Zigbee network, and the &lt;a href="https://techfuelhq.com/homelab/home-assistant-connect-zbt-2-2026/">ZBT-2 page&lt;/a> covers what it can and cannot do. That makes a Zigbee sensor the lowest-friction start. I am not claiming Zigbee is the best protocol; Home Assistant&amp;rsquo;s documentation does not rank them.&lt;/p>
&lt;h2 id="what-each-protocol-needs-on-the-home-assistant-side">What each protocol needs on the Home Assistant side&lt;/h2>
&lt;p>&lt;strong>Zigbee.&lt;/strong> Home Assistant&amp;rsquo;s ZHA page describes the integration as a hardware-independent Zigbee gateway that works through a Zigbee coordinator. The other route is Zigbee2MQTT, whose getting-started page lists a Zigbee adapter, a host system and an MQTT broker (Mosquitto is the one it recommends); Home Assistant&amp;rsquo;s MQTT integration then connects to that broker. ZHA tells you to use a USB extension cable and a USB 2.0 port, and to keep the adapter away from USB 3.0 devices, which it calls known sources of interference. My &lt;a href="https://techfuelhq.com/tutorials/home-assistant-zigbee-zwave-2026/">Zigbee and Z-Wave tutorial&lt;/a> walks through the setup.&lt;/p>
&lt;p>&lt;strong>Z-Wave.&lt;/strong> Home Assistant&amp;rsquo;s Z-Wave JS page lists four parts: a Z-Wave adapter, a Z-Wave server (the Z-Wave JS app, which it notes was formerly called an add-on), the integration and the end devices. It supports 500, 700 and 800 series adapters and recommends an 800 series adapter with firmware 7.23.2 or newer if you are starting out. The adapter has a radio frequency region, and the page says it can talk to devices specified for that region, so match the sensor&amp;rsquo;s region to the adapter&amp;rsquo;s.&lt;/p>
&lt;p>&lt;strong>Thread and Matter.&lt;/strong> Home Assistant&amp;rsquo;s Matter page says the integration runs its own Matter controller as the Matter Server app, that running it on Home Assistant OS is the supported option, and that adding a device uses your phone&amp;rsquo;s Bluetooth connection during commissioning. For Thread devices it requires a Thread border router: a Nest Hub (2nd gen), Nest Wi-Fi Pro, HomePod mini, Apple TV 4K, or Home Assistant with the OpenThread Border Router app on a radio such as the Connect ZBT-2. The Thread page says Home Assistant can act as a border router using the Thread radio of Yellow, ZBT-1, ZBT-2 or another compatible radio. The ZBT-2 page, drawing on Nabu Casa&amp;rsquo;s documentation, says that one stick runs Zigbee or Thread but not both at once.&lt;/p>
&lt;p>&lt;strong>Bluetooth.&lt;/strong> Home Assistant&amp;rsquo;s Bluetooth integration supports Bluetooth Low Energy devices and not Bluetooth Classic. On Linux it needs D-Bus access and BlueZ 5.43 or newer (it recommends 5.63 or newer); Home Assistant OS 9.0 or later configures this for you. On a Container install, the docs say that without the &lt;code>NET_ADMIN&lt;/code> and &lt;code>NET_RAW&lt;/code> capabilities Bluetooth runs in a degraded mode with raw advertising data missing, &amp;ldquo;causing unreliable updates&amp;rdquo;. Range is extended with ESPHome Bluetooth proxies, which the ESPHome page says Home Assistant aggregates with any USB adapters you have. Bluetooth sensors that broadcast in the BTHome format are discovered by the BTHome integration once Bluetooth works.&lt;/p>
&lt;p>&lt;strong>Wi-Fi.&lt;/strong> There is no single Wi-Fi path; each brand has its own integration. The one example I read, the Shelly integration page, says first-generation Shelly devices push updates over a protocol called CoIoT and that setting the CoIoT peer to your Home Assistant address and port 5683 is &amp;ldquo;mandatory for battery operated devices&amp;rdquo;. I am not recommending a Wi-Fi contact sensor on this page, because I did not find a current manufacturer page and Home Assistant page pair for one that I could stand behind.&lt;/p>
&lt;p>If your Home Assistant box lives in a rack or a VM, the &lt;a href="https://techfuelhq.com/homelab/best-mini-pc-home-assistant-2026/">mini PC guide&lt;/a> and the &lt;a href="https://techfuelhq.com/tutorials/home-assistant-proxmox-2026/">Proxmox guide&lt;/a> cover where the radio can physically sit.&lt;/p>
&lt;h2 id="batteries-and-how-they-report">Batteries and how they report&lt;/h2>
&lt;p>ZHA&amp;rsquo;s documentation calls battery door sensors sleepy sensors that only report when triggered, which is why availability settings matter.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>ZHA&lt;/strong> has a global option, at Settings &amp;gt; Connectivity &amp;gt; Zigbee &amp;gt; Options, that marks battery-powered devices unavailable after a period with no activity. The default is 6 hours (21,600 seconds), and the docs say to raise it for sleepy sensors such as door sensors that only report when triggered.&lt;/li>
&lt;li>&lt;strong>Zigbee2MQTT&lt;/strong> has an availability feature that is off by default. When on, it expects battery-powered (&amp;ldquo;passive&amp;rdquo;) devices to check in every 25 hours by default and marks them offline if they do not.&lt;/li>
&lt;li>&lt;strong>Z-Wave:&lt;/strong> Aeotec&amp;rsquo;s guide says its sensor sends open, close and tamper changes as notification reports, and warns that if the cover is left open the sensor stays permanently awake.&lt;/li>
&lt;li>&lt;strong>Bluetooth&lt;/strong> sensors broadcast. Shelly&amp;rsquo;s page describes a regular mode that broadcasts on each open or close and a beacon mode that broadcasts every 30 seconds, and says battery life may be significantly reduced in beacon mode.&lt;/li>
&lt;/ul>
&lt;p>Each manufacturer&amp;rsquo;s battery-life figure is theirs, under their own conditions, and I give those conditions below. I did not measure any.&lt;/p>
&lt;h2 id="five-sensors-each-from-its-makers-pages">Five sensors, each from its maker&amp;rsquo;s pages&lt;/h2>
&lt;h3 id="sonoff-snzb-04p-zigbee">Sonoff SNZB-04P (Zigbee)&lt;/h3>
&lt;p>Sonoff describes it as a Zigbee 3.0 door/window contact sensor with tamper protection and a CR2477 (3 V) battery. Sonoff&amp;rsquo;s page says it works with Home Assistant through ZHA or Zigbee2MQTT and needs a coordinator dongle for that. Its claimed battery life is over 5 years, which Sonoff calls a theoretical value from internal laboratory testing at 25 C, connected to a Sonoff gateway, triggered 50 times a day. Installation gap is under 20 mm with the door closed, and Sonoff says it is for indoor use only, with an operating range of -10 to 60 C. Zigbee2MQTT&amp;rsquo;s page lists the exposed values as contact, battery_low, tamper, battery and voltage, and says the device supports OTA firmware updates.&lt;/p>
&lt;p>This is the one I would start with on a Zigbee network, because Sonoff itself names both ZHA and Zigbee2MQTT and Zigbee2MQTT has a device page for it.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=SONOFF&amp;#43;SNZB-04P&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/home-assistant-door-sensor-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DSONOFF%2BSNZB-04P" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/home-assistant-door-sensor-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;h3 id="shelly-blu-doorwindow-zb-bluetooth-and-zigbee">Shelly BLU Door/Window ZB (Bluetooth and Zigbee)&lt;/h3>
&lt;p>Shelly&amp;rsquo;s page describes Bluetooth 5 LE and Zigbee 3.0 connectivity on one sensor, &amp;ldquo;with support for simultaneous Zigbee + Bluetooth operation&amp;rdquo;, plus BTHome support, a reed switch, tilt-angle measurement, a light sensor and an encrypted mode. It uses an included CR2032 battery, and Shelly lists the battery life as 5 years with no test conditions on its documentation page. Bluetooth range is &amp;ldquo;up to 10 m / 33 ft indoors and 30 m / 100 ft outdoors&amp;rdquo;, which Shelly says depends on local conditions, and its listed ambient temperature range is -20 to 40 C. Pairing is by button presses: Shelly&amp;rsquo;s page says four quick presses put it into pairing mode and five quick presses activate Zigbee pairing. Zigbee2MQTT lists it as the Shelly SBDW-103C and exposes contact, handle_position, battery_low, battery, light_level and the dark and bright thresholds, with a note that Shelly devices should be updated over Wi-Fi or Bluetooth until they gain OTA over Zigbee.&lt;/p>
&lt;p>Two cautions. The earlier Shelly BLU Door/Window is listed by Shelly as discontinued, with this ZB model as the recommended successor, so do not buy the old one. Shelly&amp;rsquo;s US store lists the ZB model, so it is sold in the US. Home Assistant&amp;rsquo;s Shelly page says Shelly BLU series devices are not supported by the Shelly integration and should use the BTHome integration, which covers the Bluetooth side; the Zigbee side goes through ZHA or Zigbee2MQTT.&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Shelly&amp;#43;BLU&amp;#43;Door&amp;#43;Window&amp;#43;ZB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/home-assistant-door-sensor-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DShelly%2BBLU%2BDoor%2BWindow%2BZB" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/home-assistant-door-sensor-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;h3 id="aeotec-doorwindow-sensor-7-z-wave">Aeotec Door/Window Sensor 7 (Z-Wave)&lt;/h3>
&lt;p>Aeotec describes it as a Z-Wave Plus sensor with S2 security and SmartStart, magnetic detection only, a tamper switch, and two magnets in the box. It is IP20 and meant for dry indoor locations, with an operating range of -20 to 45 C. It does not act as a repeater. Aeotec&amp;rsquo;s battery life figure is 3 years assuming 5 open and 5 close events a day with wake-up reports disabled.&lt;/p>
&lt;p>The details that bite: Aeotec&amp;rsquo;s spec page lists the battery by model number. The ZWA011-A, -B and -C use a 1/2 AA ER14250 3.6 V cell, and the -02 revisions use &amp;ldquo;CR14250 or CR2 3.0V&amp;rdquo;; Aeotec&amp;rsquo;s guide says the wrong battery will stop the sensor powering on, so check the model number printed on yours. The frequency is regional as well, 904-916 MHz for the US and 868.4-869.8 MHz for the EU, so match it to your adapter. Aeotec also sells a Pro version, which I did not read up on.&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Aeotec&amp;#43;Door&amp;#43;Window&amp;#43;Sensor&amp;#43;7&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/home-assistant-door-sensor-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DAeotec%2BDoor%2BWindow%2BSensor%2B7" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/home-assistant-door-sensor-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;h3 id="aqara-door-and-window-sensor-p2-matter-over-thread">Aqara Door and Window Sensor P2 (Matter over Thread)&lt;/h3>
&lt;p>Aqara&amp;rsquo;s page says the P2 is Matter over Thread, uses a CR123A battery, and requires a Matter-compatible Thread border router. It lists Home Assistant Yellow among the 2-in-1 controller and border router devices it has tested. Aqara also says battery life depends on the border router and the Matter apps the sensor is connected to, and that an Aqara Hub M3 gives longer battery life in Aqara Home. The page lists tamper alarm, adjustable sensitivity and a programmable button among features coming in a future OTA update, and separately lists adjustable sensitivity and tamper alarm as Aqara Home app features with a Hub M3. I would not count on any of them in Home Assistant.&lt;/p>
&lt;p>In Home Assistant it is a Matter device: Matter Server app, a border router (the OpenThread Border Router app on a ZBT-2 qualifies per Home Assistant&amp;rsquo;s Thread page), and a phone with Bluetooth to commission it.&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Aqara&amp;#43;Door&amp;#43;and&amp;#43;Window&amp;#43;Sensor&amp;#43;P2&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/home-assistant-door-sensor-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DAqara%2BDoor%2Band%2BWindow%2BSensor%2BP2" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/home-assistant-door-sensor-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;h3 id="eve-door--window-matter-over-thread">Eve Door &amp;amp; Window (Matter over Thread)&lt;/h3>
&lt;p>Eve lists Thread as the wireless connection and a replaceable 1/2 AA ER14250 3.6 V battery, and says you need a hub with Matter controller and Thread border router functionality. Eve states there is no subscription, no registration and no Eve cloud. Some extra statistics in Eve&amp;rsquo;s own app require Apple Home, per Eve. In Home Assistant the path is the same as the Aqara P2: Matter Server app, Thread border router, phone commissioning. Eve does not publish a battery-life figure on the page I read.&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Eve&amp;#43;Door&amp;#43;and&amp;#43;Window&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/home-assistant-door-sensor-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DEve%2BDoor%2Band%2BWindow" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/homelab/home-assistant-door-sensor-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-17&lt;/small>
&lt;/a>
&lt;/span>
&lt;h2 id="garage-doors-and-naming-the-sensor-correctly">Garage doors, and naming the sensor correctly&lt;/h2>
&lt;p>Home Assistant&amp;rsquo;s binary sensor page lists Door, Window, Garage door and Opening as separate device classes, each Open when on and Closed when off, with its own triggers such as &amp;ldquo;Garage door opened&amp;rdquo;. If a sensor lands as the wrong type you can change the class under Settings &amp;gt; Devices &amp;amp; services &amp;gt; Entities, then Settings and Show as. That is the software side of a garage sensor. The hardware side is the temperature range and indoor-only ratings above; none of the five pages I read describes a garage-door install.&lt;/p>
&lt;h2 id="what-i-would-do">What I would do&lt;/h2>
&lt;p>On a network that already has a Zigbee coordinator, I would buy the Sonoff. On a Z-Wave network, the Aeotec, after reading the model number on the box. If I were building around Thread and Matter, I would buy whichever of the Aqara P2 or Eve is easier to get, since both are Thread sensors that go in through the same Matter integration. The Shelly is the one to look at if you have Bluetooth reach and want a single sensor that speaks both Bluetooth and Zigbee. Whichever you choose, the sensor is only the trigger: the &lt;a href="https://techfuelhq.com/tutorials/home-assistant-automations-guide-2026/">automations guide&lt;/a> shows what to do when the door opens.&lt;/p></description></item><item><title>Variable Refresh Rate On or Off? Windows, G-SYNC and FreeSync (2026)</title><link>https://techfuelhq.com/gaming/variable-refresh-rate-on-or-off-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gaming/variable-refresh-rate-on-or-off-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Variable refresh rate on or off&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Monitor and driver switch (G-SYNC or FreeSync): ON&lt;/strong> if your monitor supports it. That is the pair NVIDIA and AMD describe as removing tearing and stutter.&lt;/li>
&lt;li>&lt;strong>Windows "Variable refresh rate" toggle: your call.&lt;/strong> Microsoft describes it as covering DirectX 11 full-screen games that don't support VRR natively. In 2019 it said to try it and turn it off if a game misbehaves.&lt;/li>
&lt;li>&lt;strong>Where it lives:&lt;/strong> Settings > System > Display > Graphics > Advanced graphics settings > Variable refresh rate.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>I&amp;rsquo;ll start with the Windows toggle. By Microsoft&amp;rsquo;s own description it augments the G-SYNC or FreeSync setting rather than replacing it.&lt;/p>
&lt;h2 id="what-the-windows-toggle-does">What the Windows toggle does&lt;/h2>
&lt;p>Microsoft added it in Windows 10 version 1903. Its announcement says the setting enables VRR support for DirectX 11 full-screen games that did not support VRR natively, so those games can use VRR hardware you already own. It is not a replacement for G-SYNC or FreeSync. Microsoft says it only augments them and does not override settings you already made in the G-SYNC, FreeSync or Adaptive-Sync control panels.&lt;/p>
&lt;p>The setting stays hidden unless your system has all of these, per Microsoft:&lt;/p>
&lt;ul>
&lt;li>Windows version 1903 or later.&lt;/li>
&lt;li>A G-SYNC, FreeSync or Adaptive-Sync capable monitor.&lt;/li>
&lt;li>A GPU with WDDM 2.6 or newer drivers that support G-SYNC, FreeSync or Adaptive-Sync and this OS feature.&lt;/li>
&lt;/ul>
&lt;p>To find it in Windows 11, open Settings &amp;gt; System &amp;gt; Display &amp;gt; Graphics. Microsoft&amp;rsquo;s 2023 redesign post lists it under &lt;strong>Advanced graphics settings&lt;/strong>, next to hardware-accelerated GPU scheduling, and separate from the System-wide settings group at the top of the page. Microsoft&amp;rsquo;s 2021 post sent readers to Settings &amp;gt; System &amp;gt; Display &amp;gt; Graphics &amp;gt; Default graphics settings to find a section named Variable refresh rate, so older pages use that name. I did not open the Settings app, so I can&amp;rsquo;t tell you which label your build shows. Windows will also tell you whether it sees your display as VRR-capable: Settings &amp;gt; System &amp;gt; Display &amp;gt; Advanced display shows that in the display information panel.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s 2019 post says the feature is off by default and that you should try it, and that if you run into unexpected issues while gaming, you should turn it off and see if that fixes them. I didn&amp;rsquo;t find a later Microsoft page that states the current default, so check the toggle on your own PC rather than assuming.&lt;/p>
&lt;p>&lt;strong>Who should flip it.&lt;/strong> If your monitor has G-SYNC, FreeSync or Adaptive-Sync and you play DirectX 11 games in full screen that tear or stutter, turn it on and test; that is the case Microsoft describes. For other games I&amp;rsquo;d leave it alone unless you have a specific problem to solve. That is my judgment, not a Microsoft statement.&lt;/p>
&lt;h3 id="windowed-and-borderless-games-are-a-different-switch">Windowed and borderless games are a different switch&lt;/h3>
&lt;p>A DirectX 10 or 11 game in a window or borderless window is covered by &lt;strong>Optimizations for windowed games&lt;/strong>, on the same Graphics page. Microsoft&amp;rsquo;s support page says it moves compatible games from the older blt-model presentation to flip-model, which reduces frame latency and enables Auto HDR and VRR on supported displays. Its 2022 announcement adds a catch: with v-sync off, a new frame can be ready before the last one is shown, and at high frame rates that may cause tearing. Matching the game&amp;rsquo;s frame rate to the monitor&amp;rsquo;s refresh rate or turning on in-game v-sync are the fixes it names, and it says tearing is still possible with a VRR monitor if you exceed the monitor&amp;rsquo;s refresh rate. My &lt;a href="https://techfuelhq.com/gaming/vsync-on-or-off-2026/">VSync on or off&lt;/a> page covers the cap-plus-V-Sync recipe, and the &lt;a href="https://techfuelhq.com/articles/fix-screen-tearing-2026/">screen tearing guide&lt;/a> walks the whole chain. The same Graphics page also holds Auto HDR, which has its own answer in &lt;a href="https://techfuelhq.com/gaming/hdr-on-or-off-2026/">HDR on or off&lt;/a>.&lt;/p>
&lt;h2 id="the-driver-switch-g-sync">The driver switch: G-SYNC&lt;/h2>
&lt;p>NVIDIA describes G-SYNC as matching the monitor&amp;rsquo;s refresh rate to the GPU frame rate to eliminate tearing and minimize stutter and input lag. It requires a G-SYNC or G-SYNC Compatible display. NVIDIA&amp;rsquo;s monitor page describes G-SYNC Compatible as a display that doesn&amp;rsquo;t use NVIDIA&amp;rsquo;s own processor but has been validated by NVIDIA for a basic VRR experience. The classic Control Panel help says G-SYNC Compatible displays need Windows 10 or later and a Pascal-class GPU or newer.&lt;/p>
&lt;p>The classic Control Panel steps still document how it works. Under Display, open &lt;strong>Set up G-SYNC&lt;/strong>, tick &lt;strong>Enable G-SYNC/G-SYNC Compatible&lt;/strong>, then choose between &lt;strong>Full screen mode&lt;/strong> and &lt;strong>Windowed and full screen mode&lt;/strong>. NVIDIA says to pick full screen only if G-SYNC gives you difficulty with windowed applications. It also says the display must be connected, enabled and set as the primary display, and that &lt;strong>Monitor Technology&lt;/strong> must be set to G-SYNC/G-SYNC Compatible on the Manage 3D Settings page.&lt;/p>
&lt;p>NVIDIA has since retired the classic Control Panel for Game Ready and Studio Drivers. Its May 26, 2026 driver announcement says existing installs stay put unless you do a clean install, that you can still get the Control Panel from the Microsoft Store, and that display options now live in the NVIDIA app&amp;rsquo;s System tab. G-SYNC controls were added to the NVIDIA app in October 2024, per NVIDIA&amp;rsquo;s own post. I couldn&amp;rsquo;t open the app without a GUI today, so I&amp;rsquo;m not giving you a menu path I didn&amp;rsquo;t read. My &lt;a href="https://techfuelhq.com/gaming/vsync-on-or-off-2026/">VSync page&lt;/a> records where the Monitor Technology row sat in the NVIDIA app on my bench machine in September.&lt;/p>
&lt;h2 id="the-driver-switch-freesync">The driver switch: FreeSync&lt;/h2>
&lt;p>AMD says AMD Software should enable FreeSync automatically on systems with compatible Radeon graphics and a certified display. To see or change it, open AMD Software, search for Display, and open Display Settings. Under Global Display, the FreeSync status and tier appear below Display Options, FreeSync is on globally by default, and you can turn it off on that screen. For one game, go to Gaming &amp;gt; Games, open that game&amp;rsquo;s profile and set FreeSync to AMD Optimized (the default), On or Off.&lt;/p>
&lt;p>AMD also lists the monitor side. Enable FreeSync in the display&amp;rsquo;s own settings, and note that some display presets or custom settings can disable FreeSync support, in which case it will not be available in AMD Software. For frame rates that exceed the refresh rate, AMD&amp;rsquo;s FreeSync page suggests V-Sync or a frame-rate cap. Its FAQ also says that other GPUs that support DisplayPort Adaptive-Sync, such as NVIDIA&amp;rsquo;s GeForce 10 series and newer, are expected to work with AMD FreeSync, and tells you to check with the GPU maker.&lt;/p>
&lt;h2 id="the-monitor-switch">The monitor switch&lt;/h2>
&lt;p>AMD says to enable FreeSync in the display&amp;rsquo;s own settings, and that some presets and custom settings can disable it. The vendor pages I read don&amp;rsquo;t say where that switch sits on any given monitor, so use the monitor&amp;rsquo;s manual. On my AORUS FO48U the Gaming menu has an AMD FreeSync Premium switch, as the OSD screenshots in my &lt;a href="https://techfuelhq.com/articles/aorus-fo48u-review/">FO48U review&lt;/a> show. I run it from an RTX 5080 at 3840 x 2160 and 120 Hz, which the dxdiag report on this machine confirmed today.&lt;/p>
&lt;p>HDMI and DisplayPort limits can also decide which refresh rates you can reach at 4K. The &lt;a href="https://techfuelhq.com/tools/displayport-hdmi-bandwidth-calculator/">DisplayPort and HDMI bandwidth calculator&lt;/a> checks a resolution and refresh rate against each link.&lt;/p>
&lt;h2 id="how-the-three-fit-together">How the three fit together&lt;/h2>
&lt;p>Think of it as a chain. The monitor has to offer VRR, the GPU driver has to use it, and Windows adds one more layer for older games.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Layer&lt;/th>
&lt;th scope="col">Switch&lt;/th>
&lt;th scope="col">What the source says it does&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Layer">Monitor&lt;/td>
&lt;td data-label="Switch">FreeSync, Adaptive-Sync or G-SYNC Compatible option in its menu&lt;/td>
&lt;td data-label="What the source says it does">AMD says to enable FreeSync in the display settings; some presets can disable it.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Layer">GPU driver&lt;/td>
&lt;td data-label="Switch">NVIDIA: Enable G-SYNC/G-SYNC Compatible. AMD: FreeSync in Display Settings or per-game profile&lt;/td>
&lt;td data-label="What the source says it does">Matches the monitor&amp;rsquo;s refresh rate to the GPU frame rate to remove tearing.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Layer">Windows&lt;/td>
&lt;td data-label="Switch">Variable refresh rate (Advanced graphics settings)&lt;/td>
&lt;td data-label="What the source says it does">Adds VRR to DirectX 11 full-screen games that don&amp;rsquo;t support it natively; doesn&amp;rsquo;t override the driver settings.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>To compare VRR on and off in a game, change one layer at a time. The Windows toggle and the driver switch are separate, so switching both at once tells you nothing about which one mattered.&lt;/p>
&lt;p>One more name to separate: &lt;strong>Dynamic Refresh Rate&lt;/strong> is a different Windows 11 feature, found under Settings &amp;gt; System &amp;gt; Display &amp;gt; Advanced display. Microsoft&amp;rsquo;s 2021 preview post said it was available only on laptops; its current refresh-rate page doesn&amp;rsquo;t say that, and says DRR requires a display that supports VRR and a refresh rate of at least 120 Hz. Both say DRR should not affect games designed for VRR but can limit the maximum refresh rate of other games, and that the best mitigation is to disable DRR.&lt;/p>
&lt;h2 id="when-id-turn-vrr-off">When I&amp;rsquo;d turn VRR off&lt;/h2>
&lt;p>Off is a diagnostic step, not a default. Turn the Windows toggle off if a game starts misbehaving after you enabled it, because that is what Microsoft says to do. Turn the driver switch off to see whether a stutter or flicker follows it, and set FreeSync to Off in a single game&amp;rsquo;s profile if only that game is the problem. If tearing comes back with VRR off, the cap and V-Sync pages linked above are where to go next.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/os-variable-refresh-rate/" rel="noopener">Microsoft DirectX Developer Blog, OS Variable Refresh Rate (2019)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/navigating-the-redesigned-graphics-settings-page/" rel="noopener">Microsoft DirectX Developer Blog, Navigating the Redesigned Graphics Settings page (2023)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/dynamic-refresh-rate/" rel="noopener">Microsoft DirectX Developer Blog, Dynamic refresh rate (2021)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/updates-in-graphics-and-gaming/" rel="noopener">Microsoft DirectX Developer Blog, Updates in Graphics and Gaming (2022)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/optimizations-for-windowed-games-in-windows-11-3f006843-2c7e-4ed0-9a5e-f9389e535952" rel="noopener">Microsoft Support, Optimizations for windowed games in Windows 11&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/hardware/display-graphics/change-the-refresh-rate-on-your-monitor-in-windows" rel="noopener">Microsoft Support, Change the refresh rate on your monitor in Windows&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.nvidia.com/content/Control-Panel-Help/vLatest/en-us/mergedProjects/Display/Variable_Refresh_Rate.htm" rel="noopener">NVIDIA Control Panel Help, NVIDIA G-SYNC&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.nvidia.com/content/Control-Panel-Help/vLatest/en-us/mergedProjects/Display/To_use_variable_refresh_rates.htm" rel="noopener">NVIDIA Control Panel Help, To set up G-SYNC&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.nvidia.com/content/Control-Panel-Help/vLatest/en-us/mergedProjects/nv3d/Manage_3D_Settings_%28reference%29.htm" rel="noopener">NVIDIA Control Panel Help, Manage 3D Settings (reference)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.nvidia.com/en-us/geforce/news/007-first-light-geforce-game-ready-driver/" rel="noopener">NVIDIA, 007 First Light GeForce Game Ready Driver Released (Control Panel retirement notice)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.nvidia.com/en-us/geforce/news/nvidia-app-beta-update-g-sync-controls-rtx-hdr-multi-monitor/" rel="noopener">NVIDIA, NVIDIA App Beta Adds G-SYNC Controls (October 1, 2024)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.nvidia.com/en-us/geforce/products/g-sync-monitors/" rel="noopener">NVIDIA, G-SYNC monitors&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.amd.com/en/resources/support-articles/faqs/DH3-013.html" rel="noopener">AMD Support DH3-013, How to Enable AMD FreeSync with AMD Software: Adrenalin Edition&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.amd.com/en/products/graphics/technologies/freesync.html" rel="noopener">AMD, FreeSync technology&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>Steam Store Not Loading: Outage or Your PC? Fixes in Order (2026)</title><link>https://techfuelhq.com/gaming/steam-store-not-loading-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gaming/steam-store-not-loading-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Steam store not loading&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>First:&lt;/strong> open store.steampowered.com in a normal browser, then on a phone using mobile data. Failing everywhere points away from your PC.&lt;/li>
&lt;li>&lt;strong>Fails only in the Steam client:&lt;/strong> restart Steam, make sure it isn't in Offline Mode, then optionally try Delete Web Browser Data (not a Valve-documented fix for the store).&lt;/li>
&lt;li>&lt;strong>Still failing:&lt;/strong> restart the modem and router, try a wired connection and another network, then test VPN, proxy, firewall and security software.&lt;/li>
&lt;li>&lt;strong>Last resort:&lt;/strong> run the Steam installer over the same folder. Valve warns that uninstalling Steam any other way deletes game and userdata content.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>I couldn&amp;rsquo;t find a Steam Support article about the store not loading. What Valve does have is a set of network, firewall and interference articles, and those are the ground this page is built on. Where a step comes from Valve I say so. Where it comes from Microsoft, I say that. Where it&amp;rsquo;s my own test, I say that too.&lt;/p>
&lt;h2 id="outage-or-your-pc-three-quick-tests">Outage or your PC: three quick tests&lt;/h2>
&lt;p>Valve&amp;rsquo;s network article opens by telling you to check server status so you can rule out system-wide downtime, and says that if you hit timeout errors when opening Steam sites, there is very likely a system-wide issue and Steam won&amp;rsquo;t be reachable until it&amp;rsquo;s resolved. The status link in that article now lands on the Steam Charts page, which lists player counts. Valve doesn&amp;rsquo;t call those counts an outage indicator, so I wouldn&amp;rsquo;t read one into them.&lt;/p>
&lt;p>That leaves tests you can run yourself:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Open store.steampowered.com in a normal browser.&lt;/strong> Valve&amp;rsquo;s sign-in help page says the Steam client accesses your account differently than a web browser does. That page is about signing in, not the store, so treat this as my test rather than a Valve diagnosis. If the store loads in the browser but not the client, start at Fix 1.&lt;/li>
&lt;li>&lt;strong>Try a second device on a different network&lt;/strong>, such as a phone on mobile data. Valve&amp;rsquo;s troubleshooting article recommends testing on an entirely different network, preferably from a different internet provider. It also notes that some providers, &amp;ldquo;especially cellphone networks,&amp;rdquo; cache or compress data in ways that can cause Steam issues, so a failure on a hotspot proves less than a success does.&lt;/li>
&lt;li>&lt;strong>Note the time.&lt;/strong> Valve says that if Steam has trouble only during certain hours, for example 5pm to 11pm, your ISP may be blocking or shaping the connection. Test at another time of day and contact the ISP if it follows the clock.&lt;/li>
&lt;/ol>
&lt;p>If the store fails in the browser on every device and network, stop. Valve&amp;rsquo;s help wizard tells people who can&amp;rsquo;t sign in that Steam may be undergoing maintenance, or that there&amp;rsquo;s a problem with the local network or ISP, and that waiting a few hours and trying again may be the answer.&lt;/p>
&lt;h2 id="the-fixes-least-disruptive-first">The fixes, least disruptive first&lt;/h2>
&lt;h3 id="1-restart-steam-then-check-offline-mode">1. Restart Steam, then check Offline Mode&lt;/h3>
&lt;p>Valve&amp;rsquo;s first basic step is to restart Steam as well as the computer, because a restart releases locks on files and other resources. Its advanced list adds running Windows&amp;rsquo; Check for Updates, since it wants the operating system and drivers current.&lt;/p>
&lt;p>Then look at the Steam menu. Valve&amp;rsquo;s Offline Mode article says any client feature that requires a connection is unavailable in Offline Mode, and the menu entry that switches it off reads &amp;ldquo;Go Online&amp;hellip;&amp;rdquo; in my client&amp;rsquo;s strings. If you see that entry, use it.&lt;/p>
&lt;p>&lt;strong>Rules out:&lt;/strong> a stale session and a client left offline.&lt;/p>
&lt;h3 id="2-delete-web-browser-data">2. Delete Web Browser Data&lt;/h3>
&lt;p>Valve has no support article for this button, so everything here comes from the client itself. On my install the button is labelled Delete Web Browser Data. Its confirmation reads &amp;ldquo;Delete all Steam browser cached files, cookies, and history?&amp;rdquo; The client&amp;rsquo;s interface code places it on the In Game settings page, beside &amp;ldquo;Web browser home page,&amp;rdquo; and the same label appears in a second, Internet-settings code path whose confirmation reads &amp;ldquo;Delete all browser cached files, cookies, and history?&amp;rdquo; Both run the same clear-all-browsing-data call. Many older guides send you to a Web Browser tab. The client&amp;rsquo;s strings file contains a page title &amp;ldquo;Web Browser,&amp;rdquo; but I found no code that uses it, and I didn&amp;rsquo;t open the window, so look for the label.&lt;/p>
&lt;p>The confirmation says it deletes cached files, cookies and history for the Steam browser, so treat it as a test, not a documented fix. Because it sits with the in-game overlay browser settings, I can&amp;rsquo;t confirm from what I read that it clears the same data the store pane uses. It isn&amp;rsquo;t Valve&amp;rsquo;s documented fix for the store, and I can&amp;rsquo;t tell you why it helps when it does, because nothing I read says.&lt;/p>
&lt;p>&lt;strong>Rules out:&lt;/strong> bad cached web data inside the client.&lt;/p>
&lt;h3 id="3-clear-the-download-cache">3. Clear the download cache&lt;/h3>
&lt;p>Valve&amp;rsquo;s article says clearing it &amp;ldquo;can solve problems with games that won&amp;rsquo;t download or start,&amp;rdquo; and doesn&amp;rsquo;t mention the store. I include it because it&amp;rsquo;s cheap. It doesn&amp;rsquo;t affect installed games, but you have to log in to Steam again afterward. Go to Steam, Settings, Downloads, then Clear Download Cache, and confirm.&lt;/p>
&lt;p>&lt;strong>Rules out:&lt;/strong> that cache. Expect nothing more than that.&lt;/p>
&lt;h3 id="4-if-the-pane-is-blank-rather-than-erroring-gpu-acceleration">4. If the pane is blank rather than erroring: GPU acceleration&lt;/h3>
&lt;p>Valve&amp;rsquo;s article on the &amp;ldquo;Steamwebhelper is not responding&amp;rdquo; dialog says some video drivers can have trouble rendering Steam content with GPU acceleration on. It points to Steam, Settings, Interface, where the checkbox reads &amp;ldquo;Enable GPU accelerated rendering in web views (requires restart)&amp;rdquo; in my client&amp;rsquo;s strings. Turn it off, restart Steam, and test. If that helps, Valve suggests updating your graphics drivers, and my &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/">GPU driver guide&lt;/a> covers a clean install. Valve says leaving it off permanently affects UI performance.&lt;/p>
&lt;p>Valve describes this for the not-responding dialog, not for a store that won&amp;rsquo;t load. I&amp;rsquo;m offering it for a blank store pane because it&amp;rsquo;s the rendering step Valve documents.&lt;/p>
&lt;p>&lt;strong>Rules out:&lt;/strong> GPU-accelerated rendering in the client&amp;rsquo;s web views.&lt;/p>
&lt;h3 id="5-network-router-wired-connection-dns">5. Network: router, wired connection, DNS&lt;/h3>
&lt;p>These are Valve&amp;rsquo;s, in its words:&lt;/p>
&lt;ul>
&lt;li>Reboot the modem, router or combined unit before anything else. Valve says network hardware can get into a slow or broken state after running for a long time.&lt;/li>
&lt;li>If modem and router are separate, close Steam, plug the PC straight into the modem, and test. If Steam connects, Valve says that indicates a router configuration or compatibility issue.&lt;/li>
&lt;li>Test over a wired connection. Valve says wireless and powerline connections can fail intermittently from interference.&lt;/li>
&lt;li>If your router has stateful inspection, dynamic packet filtering, QoS or UPnP turned on, Valve says to try disabling them. It doesn&amp;rsquo;t say why. Note each setting before you change it, because other devices share that router.&lt;/li>
&lt;/ul>
&lt;p>Two DNS steps come after, and neither Valve nor Microsoft ties DNS to the Steam store. They&amp;rsquo;re my additions, cheap and reversible.&lt;/p>
&lt;p>Microsoft documents &lt;code>ipconfig /flushdns&lt;/code> as flushing and resetting the DNS client resolver cache, and says it can be used during DNS troubleshooting. Run it in a Command Prompt, then reload the store.&lt;/p>
&lt;p>To test your current DNS server, Microsoft&amp;rsquo;s steps are Settings, Network &amp;amp; internet, then Wi-Fi, Manage known networks (or Ethernet), the connection, Edit next to IP assignment, Manual, IPv4, and the Preferred DNS and Alternate DNS boxes. Cloudflare documents 1.1.1.1 and 1.0.0.1, and Google documents 8.8.8.8 and 8.8.4.4. Microsoft notes that Manual lets you set IP settings as well as DNS, and the same Manual screen has IP address, Subnet mask and Gateway boxes, so write down what&amp;rsquo;s there first and re-enter those values with the DNS change. When you&amp;rsquo;re done, set it back to Automatic (DHCP), which Microsoft recommends.&lt;/p>
&lt;p>&lt;strong>Rules out:&lt;/strong> your router, your wireless link, and your current DNS server.&lt;/p>
&lt;h3 id="6-proxy-and-vpn">6. Proxy and VPN&lt;/h3>
&lt;p>Valve&amp;rsquo;s interference article says VPN software can prevent the Steam client from reaching the Steam network, and its client troubleshooting article lists proxies among software that modifies network activity. Disconnect any VPN, either in its own app or through Settings, Network &amp;amp; internet, VPN, which is Microsoft&amp;rsquo;s path.&lt;/p>
&lt;p>For the proxy, Microsoft&amp;rsquo;s path is Settings, Network &amp;amp; internet, Proxy. On my machine I read ProxyEnable as 0 and the WinHTTP proxy as direct, so this is a check, not a diagnosis. If you&amp;rsquo;re on a work or school network, Valve says many university and business networks and proxies block the ports Steam needs, and that those ports can&amp;rsquo;t be remapped. Its list for logging in includes TCP 80 and 443 and TCP and UDP 27015 to 27050. Its proxy section says the proxy should allow steampowered.com, steamcommunity.com, steamgames.com, steamusercontent.com, steamcontent.com, steamstatic.com and akamaihd.net. That is for the network administrator, not for you to fix at home.&lt;/p>
&lt;p>&lt;strong>Rules out:&lt;/strong> a tunnel or proxy sitting between Steam and the internet.&lt;/p>
&lt;h3 id="7-security-software-and-the-firewall">7. Security software and the firewall&lt;/h3>
&lt;p>Valve says anti-virus can affect disk and network operations, anti-spyware can break some Steam web features if your web traffic is being aggressively monitored, and firewalls can stop Steam talking to its servers. Its test is to exit the program, disable it temporarily, and restart Steam.&lt;/p>
&lt;p>For the Windows firewall, Valve&amp;rsquo;s steps (the article was last updated in 2021) are to close Steam, remove the Steam executables from the firewall&amp;rsquo;s permissions (steam.exe, steaminstall.exe, hl.exe, hl2.exe and steamTmp.exe), start Steam, and let the firewall prompt you again. It then says to give permission for all TCP and UDP ports when prompted, and restart the PC. Microsoft&amp;rsquo;s path to the allowed-apps list is Windows Security, Firewall &amp;amp; network protection, Allow an app through firewall, Change settings.&lt;/p>
&lt;p>To test with the firewall off, Valve says to exit Steam, disable the firewall temporarily, restart Steam and test, and re-enable the firewall. It adds that it doesn&amp;rsquo;t recommend leaving it disabled, and Microsoft warns that turning it off can leave your device more open to unauthorized access. Re-enable it whatever the result.&lt;/p>
&lt;p>&lt;strong>Rules out:&lt;/strong> security software and your firewall rules.&lt;/p>
&lt;h3 id="8-reinstall-steam-over-the-same-folder">8. Reinstall Steam over the same folder&lt;/h3>
&lt;p>This is Valve&amp;rsquo;s second basic step, and it&amp;rsquo;s the one that can lose data. Run the installer from Steam&amp;rsquo;s site into the folder Steam already uses. Valve says that may fix client and service file problems and preserves installed games, and it warns that uninstalling Steam any other way deletes all game and userdata content. The full version, and what to do if Steam won&amp;rsquo;t open at all, is on my &lt;a href="https://techfuelhq.com/gaming/steam-not-opening-2026/">Steam not opening&lt;/a> page.&lt;/p>
&lt;h2 id="when-to-stop-and-contact-steam">When to stop and contact Steam&lt;/h2>
&lt;p>Steam Support is Valve&amp;rsquo;s channel for what these articles don&amp;rsquo;t fix. Stop and file a ticket at help.steampowered.com if the store fails on every device and network after a few hours, which points away from your PC, or if it still fails inside the client after Fix 8. Give them the time of each failure, which of the three outage tests failed, and the steps you&amp;rsquo;ve already run.&lt;/p>
&lt;p>If you want a place to keep that record, the &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">Diagnostic Workbench&lt;/a> does it in your browser.&lt;/p>
&lt;h2 id="steam-deck">Steam Deck&lt;/h2>
&lt;p>Valve&amp;rsquo;s Deck guide says to change network under Steam, Settings, Internet. It has nothing about the store specifically. Steps 1, 5 and the different-network test above are the ones that apply, and I haven&amp;rsquo;t tested any of them on a Deck.&lt;/p>
&lt;h2 id="if-the-store-loads-but-downloads-crawl-or-games-wont-start">If the store loads but downloads crawl, or games won&amp;rsquo;t start&lt;/h2>
&lt;p>That&amp;rsquo;s a different failure. For slow downloads, see &lt;a href="https://techfuelhq.com/gaming/steam-slow-download-speed-2026/">Steam slow download speed&lt;/a>. For a game that bounces between Play and Running, see &lt;a href="https://techfuelhq.com/gaming/steam-games-not-launching-2026/">Steam games not launching&lt;/a>.&lt;/p>
&lt;h2 id="what-i-checked-on-my-own-machine">What I checked on my own machine&lt;/h2>
&lt;p>All read-only, on 2026-11-17, with Steam not running. Windows 11 build 26200.9974, NVIDIA driver 621.24. &lt;code>steam.exe&lt;/code> reads file version 11.23.65.88, written 2026-11-12. The labels I quote came from the client&amp;rsquo;s own strings file and interface code. No proxy is set. Valve&amp;rsquo;s status link redirected to the Charts page. I did not launch Steam, open its Settings window or reproduce a store failure, so this page tells you what Valve and Microsoft document and where I found no documentation.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/669A-2F68-D1D1-A5EC" rel="noopener">Steam Support, Troubleshooting Network Connectivity&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/1F39-DCB4-FF28-5748" rel="noopener">Steam Support, Programs Which May Interfere with Steam&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/46D2-B5B1-F0B9-B867" rel="noopener">Steam Support, Using a Router with Steam&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/66C8-4FF1-8470-B666" rel="noopener">Steam Support, Using a Firewall with Steam&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/2EA8-4D75-DA21-31EB" rel="noopener">Steam Support, Required Ports for Steam&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/29A6-F529-F956-6292" rel="noopener">Steam Support, Steam Client Troubleshooting&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/6C3E-9504-CC20-AF49" rel="noopener">Steam Support, Steamwebhelper is not responding&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/6AD7-820D-8BE5-E51F" rel="noopener">Steam Support, Clear download cache&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/0E18-319B-E34B-B2C8" rel="noopener">Steam Support, Offline Mode&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/wizard/HelpWithSteamIssue/?issueid=706" rel="noopener">Steam Support, I can&amp;rsquo;t sign in to the Steam Client&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/69E3-14AF-9764-4C28" rel="noopener">Steam Support, Steam Deck Basic Use &amp;amp; Troubleshooting Guide&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/71D3-35C2-AD96-AA3A" rel="noopener">Steam Support, Limited User Accounts&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://store.steampowered.com/charts/" rel="noopener">Steam Charts&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/ipconfig" rel="noopener">Microsoft Learn, ipconfig&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/experience/connectivity-networking/essential-network-settings-and-tasks-in-windows" rel="noopener">Microsoft Support, Essential network settings and tasks in Windows&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/experience/connectivity-networking/use-a-proxy-server-in-windows" rel="noopener">Microsoft Support, Use a proxy server in Windows&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/experience/connectivity-networking/connect-to-a-vpn-in-windows" rel="noopener">Microsoft Support, Connect to a VPN in Windows&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/security/firewall/risks-of-allowing-apps-through-windows-firewall" rel="noopener">Microsoft Support, Risks of allowing apps through Windows Firewall&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/security/windows-security/firewall-and-network-protection-in-the-windows-security-app" rel="noopener">Microsoft Support, Firewall and network protection in the Windows Security app&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://developers.cloudflare.com/1.1.1.1/ip-addresses/" rel="noopener">Cloudflare 1.1.1.1 docs, IP addresses&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://developers.google.com/speed/public-dns/docs/using" rel="noopener">Google Public DNS, Get started&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>Steam Overlay Not Working: Fixes in Order (2026)</title><link>https://techfuelhq.com/gaming/steam-overlay-not-working-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gaming/steam-overlay-not-working-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;p>By &lt;a href="https://techfuelhq.com/author/lk-wood-iv/">LK Wood IV&lt;/a> · Published 2026-11-17 · ~7 min read · St. Louis County, MO&lt;/p>
&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Steam overlay not working&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Two switches:&lt;/strong> &lt;strong>Steam &amp;gt; Settings &amp;gt; In-game &amp;gt; Enable the Steam Overlay while in-game&lt;/strong>, then &lt;strong>Properties &amp;gt; General&lt;/strong> on the game itself.&lt;/li>
&lt;li>&lt;strong>The key:&lt;/strong> Valve's default is &lt;strong>Shift + Tab&lt;/strong>. If you changed it, the new one lives in the same In-game tab.&lt;/li>
&lt;li>&lt;strong>Launch from Steam.&lt;/strong> For a non-Steam game, add it to your Steam library first and turn off any other launcher's overlay.&lt;/li>
&lt;li>&lt;strong>Still nothing:&lt;/strong> restart, close other overlay and monitoring software, verify the game's files, then look at firewall and antivirus.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>This is Valve&amp;rsquo;s own guidance arranged from least to most disruptive, with what each step rules out. The Valve pages I read don&amp;rsquo;t say which cause is most common, so I won&amp;rsquo;t either.&lt;/p>
&lt;p>First, which problem is yours?&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">What you see&lt;/th>
&lt;th scope="col">Start at&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="What you see">Shift+Tab does nothing in a Steam game&lt;/td>
&lt;td data-label="Start at">Step 1&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">Works in some games, not in a game you added yourself&lt;/td>
&lt;td data-label="Start at">Step 3&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">Opens, then freezes or closes&lt;/td>
&lt;td data-label="Start at">&lt;a href="#the-overlay-opens-but-freezes-or-closes">Overlay opens but freezes&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">The game itself won&amp;rsquo;t start&lt;/td>
&lt;td data-label="Start at">&lt;a href="https://techfuelhq.com/gaming/steam-games-not-launching-2026/">Steam games not launching&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">Steam won&amp;rsquo;t open at all&lt;/td>
&lt;td data-label="Start at">&lt;a href="https://techfuelhq.com/gaming/steam-not-opening-2026/">Steam not opening&lt;/a>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="step-1-check-the-setting-and-the-key">Step 1. Check the setting and the key&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> the overlay being switched off, and a shortcut you&amp;rsquo;ve forgotten you changed.&lt;/p>
&lt;p>Valve describes the overlay as the in-game interface for Steam Community features, opened with Shift+Tab in any game where it&amp;rsquo;s supported and enabled. Its article says to confirm two things before anything else: that the overlay is enabled, and that the keybinding is correct.&lt;/p>
&lt;ol>
&lt;li>Open &lt;strong>Steam &amp;gt; Settings &amp;gt; In-game&lt;/strong> and turn on &lt;strong>Enable the Steam Overlay while in-game&lt;/strong>. The shortcut is on the same tab.&lt;/li>
&lt;li>Find the game in your Library, open &lt;strong>Properties&lt;/strong>, and on the &lt;strong>General&lt;/strong> tab check &lt;strong>Enable the Steam Overlay while in-game&lt;/strong>.&lt;/li>
&lt;/ol>
&lt;p>Valve&amp;rsquo;s article lists the global switch and the per-game one separately, so check both.&lt;/p>
&lt;p>If you were about to leave the overlay off on purpose, know what rides on it. Valve says some games need it for in-game purchases, party and matchmaking invites, trading and Market features, and F12 screenshots. A game that uses it for invites won&amp;rsquo;t send them when it&amp;rsquo;s off.&lt;/p>
&lt;h2 id="step-2-start-the-game-from-steam-and-give-it-a-moment">Step 2. Start the game from Steam, and give it a moment&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> a game that was started some other way, so the overlay never had a chance to attach.&lt;/p>
&lt;p>Valve&amp;rsquo;s Steamworks documentation says the overlay hooks into any game launched from Steam. For a game that meets its requirements and still shows no overlay, it says to make sure the game is being launched through the Steam client. That documentation is written for developers, but it tells you what Valve describes as the supported route. A game you start some other way isn&amp;rsquo;t covered by that sentence.&lt;/p>
&lt;p>The same page notes, in its description of a function developers call, that the overlay process can take a few seconds to start and hook the game process. Valve doesn&amp;rsquo;t give players advice based on that. My suggestion, not Valve&amp;rsquo;s, is to wait a few seconds after the game window appears before testing Shift+Tab.&lt;/p>
&lt;p>The same documentation also lists what the overlay supports: DirectX 7 through 12, OpenGL, Metal and Vulkan. It says the overlay won&amp;rsquo;t be active in software-rasterized games, and it says that for a game running inside a web browser the overlay can&amp;rsquo;t work as it stands, because it needs a game that renders frames consistently and browsers don&amp;rsquo;t support that model. It describes a developer-side workaround, not a player setting.&lt;/p>
&lt;h3 id="a-check-i-can-show-you-from-my-own-machine">A check I can show you from my own machine&lt;/h3>
&lt;p>Steam keeps an overlay log. On my bench PC it&amp;rsquo;s &lt;code>gameoverlay_renderer.txt&lt;/code> in the &lt;code>logs&lt;/code> folder under the Steam install (mine is &lt;code>C:\Program Files (x86)\Steam&lt;/code>). The entry I read names the process the overlay attached to and the line &amp;ldquo;Game is using dxgi (dx10/dx11), preparing to hook.&amp;rdquo; If you launch a game from Steam and that file then has an entry naming the game&amp;rsquo;s executable, the entry is a record that the overlay renderer module was loaded in that process, going by the fields it prints. I haven&amp;rsquo;t seen what a missing entry looks like and I found no Valve page that documents this log, so I can&amp;rsquo;t tell you what absence means. Treat it as one more piece of evidence, not a diagnosis.&lt;/p>
&lt;h2 id="step-3-non-steam-games">Step 3. Non-Steam games&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> a game that isn&amp;rsquo;t in your Steam library, which Valve says Steam may have trouble applying the overlay to.&lt;/p>
&lt;p>Valve&amp;rsquo;s Steam Controller support page, in its overlay troubleshooting, says Steam may have issues applying the overlay to a non-Steam or retail game that hasn&amp;rsquo;t been added to your Steam library, particularly when the game has its own launcher. So:&lt;/p>
&lt;ol>
&lt;li>Add the game to your Steam library and start it from Steam. I&amp;rsquo;m not giving you a menu path for the add step because I didn&amp;rsquo;t find a Valve page that spells one out; use the add-a-game control in the Steam client.&lt;/li>
&lt;li>If the game goes through another launcher, turn that launcher&amp;rsquo;s overlay off. The same Valve page says launchers such as Uplay and Origin can have their own overlays that take priority over Steam&amp;rsquo;s, and its steps are: launch the game from Steam, find the launcher&amp;rsquo;s settings, and disable its overlay. Those two launcher names are Valve&amp;rsquo;s own examples. I would check any other launcher&amp;rsquo;s overlay setting the same way.&lt;/li>
&lt;/ol>
&lt;p>Valve doesn&amp;rsquo;t promise the overlay works in every non-Steam game. Its wording is that Steam &amp;ldquo;may have issues&amp;rdquo;, and that is all the page says.&lt;/p>
&lt;h2 id="step-4-restart-steam-then-the-computer">Step 4. Restart Steam, then the computer&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> stuck state in the client or the system.&lt;/p>
&lt;p>Valve&amp;rsquo;s first basic step for the overlay is to restart both Steam and the computer, and it gives a reason: restarting flushes system states and caches, resets other programs, and releases locks on files and other resources. Exit Steam from the Steam menu, then restart Windows and try the game again.&lt;/p>
&lt;h2 id="step-5-close-other-overlay-and-monitoring-software">Step 5. Close other overlay and monitoring software&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> another program interfering with Steam&amp;rsquo;s overlay.&lt;/p>
&lt;p>Valve says any software that modifies or monitors system, disk or network activity can cause issues with the overlay. Its examples are antivirus, ad-blockers, web-optimizers, firewalls, system cleaners, recording software, proxies and performance boosters. Its separate &lt;a href="https://help.steampowered.com/en/faqs/view/1F39-DCB4-FF28-5748" rel="noopener">Programs Which May Interfere with Steam&lt;/a> article says problems from such software may be resolved by exiting or disabling it and then restarting Steam, and that some programs need a reboot after being shut down.&lt;/p>
&lt;p>Close them one at a time and test after each, so you know which one it was. Valve also warns that many applications launch at startup and may not appear in the Windows taskbar while still running, so an empty taskbar is not proof that nothing is running.&lt;/p>
&lt;p>Valve&amp;rsquo;s Steam Controller page has its own list of programs that conflicted with controller functionality, including Razer Synapse, XInput emulators, screen capture software such as Fraps, MSI Afterburner and ASUS AI Suite. That list was written for controller behavior, not for the overlay, so treat it as a place to look rather than a verdict.&lt;/p>
&lt;h2 id="step-6-verify-the-games-files">Step 6. Verify the game&amp;rsquo;s files&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> a damaged game file that touches how the game uses the overlay.&lt;/p>
&lt;p>Valve says files can become corrupted, and that some of them may be tied to how the game uses the overlay. In your Library, right-click the game, choose &lt;strong>Properties&lt;/strong>, open &lt;strong>Installed Files&lt;/strong>, and click &lt;strong>Verify integrity of game files&lt;/strong>. Valve says it can take several minutes.&lt;/p>
&lt;p>Two warnings from Valve&amp;rsquo;s article: don&amp;rsquo;t run it while doing other system-intensive work such as defragmenting or virus scanning, and don&amp;rsquo;t run it for several games at the same time. It also says one or more files failing to verify is normal for most games and can be ignored.&lt;/p>
&lt;h2 id="step-7-firewall-and-antivirus">Step 7. Firewall and antivirus&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> security software blocking Steam&amp;rsquo;s communication with the game.&lt;/p>
&lt;p>Valve puts these under advanced troubleshooting and recommends getting help from an IT specialist for them. It says firewalls may prevent Steam from communicating with the game that needs it, and that antivirus can affect disk and network operations. It suggests temporarily disabling each for testing and adding Steam exceptions, with the example of excluding Steam library folders from live monitoring.&lt;/p>
&lt;p>My own preference is the exception over leaving protection switched off. That part is judgment, not Valve&amp;rsquo;s instruction. The temporary disable is Valve&amp;rsquo;s wording for a test.&lt;/p>
&lt;h2 id="step-8-reinstall-steam-over-the-existing-install">Step 8. Reinstall Steam over the existing install&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> damaged Steam client files, including the ones the overlay needs.&lt;/p>
&lt;p>Valve says to download the installer and reinstall to the same location Steam is already in, and that this ensures all the files the overlay needs are in a good state without affecting installed games.&lt;/p>
&lt;p>&lt;strong>Warning:&lt;/strong> Valve states that uninstalling Steam deletes all game content. Don&amp;rsquo;t uninstall first. Run the installer over the existing folder. My &lt;a href="https://techfuelhq.com/gaming/steam-not-opening-2026/">Steam not opening guide&lt;/a> covers that reinstall in more detail.&lt;/p>
&lt;h2 id="the-overlay-opens-but-freezes-or-closes">The overlay opens but freezes or closes&lt;/h2>
&lt;p>Valve describes the overlay as a supplemental component that is closed automatically if system resources come under heavy load. Its advice: update major drivers, limit the programs running during play, and update the operating system. If you suspect the graphics driver, my &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/">GPU driver crash guide&lt;/a> walks that through. Valve also says that if the system is at or below a game&amp;rsquo;s required or recommended specs, the overlay may struggle.&lt;/p>
&lt;h2 id="when-to-stop-and-contact-valve">When to stop and contact Valve&lt;/h2>
&lt;p>If you&amp;rsquo;ve been through the eight steps and the overlay still won&amp;rsquo;t open, take it to Steam Support at help.steampowered.com. If the failure is also showing up as a file error during updates, that&amp;rsquo;s a different path: see &lt;a href="https://techfuelhq.com/gaming/steam-missing-file-privileges-fix-2026/">Steam missing file privileges&lt;/a> or &lt;a href="https://techfuelhq.com/gaming/steam-content-file-locked-fix-2026/">Steam content file locked&lt;/a>. The &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">diagnostic workbench&lt;/a> can help you keep a record of what you tried.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/3978-072C-18DF-FBF9" rel="noopener">Steam Support: Steam Community Overlay&lt;/a>, read 2026-11-17.&lt;/li>
&lt;li>&lt;a href="https://partner.steamgames.com/doc/features/overlay" rel="noopener">Steamworks Documentation: Steam Overlay&lt;/a>, read 2026-11-17.&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/wizard/HelpWithGameIssue/?appid=353370&amp;amp;issueid=362&amp;amp;nodeid=30" rel="noopener">Steam Support: Steam Controller (2015), Configurations&lt;/a>, read 2026-11-17. Valve&amp;rsquo;s page about controller configurations; I use only its overlay-related lines.&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/1F39-DCB4-FF28-5748" rel="noopener">Steam Support: Programs Which May Interfere with Steam&lt;/a>, read 2026-11-17.&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/0C48-FCBD-DA71-93EB" rel="noopener">Steam Support: Verify Integrity of Game Files&lt;/a>, read 2026-11-17.&lt;/li>
&lt;/ul></description></item><item><title>Steam Missing File Privileges: Fixes in Order (2026)</title><link>https://techfuelhq.com/gaming/steam-missing-file-privileges-fix-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gaming/steam-missing-file-privileges-fix-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;p>By &lt;a href="https://techfuelhq.com/author/lk-wood-iv/">LK Wood IV&lt;/a> · Published 2026-11-17 · ~8 min read · St. Louis County, MO&lt;/p>
&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Steam missing file privileges&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>First:&lt;/strong> restart Steam and the PC, then &lt;strong>Steam &amp;gt; Settings &amp;gt; Storage &amp;gt; ... &amp;gt; Repair Folder&lt;/strong> on the drive that holds the game.&lt;/li>
&lt;li>&lt;strong>Next:&lt;/strong> &lt;strong>Steam &amp;gt; Settings &amp;gt; Downloads &amp;gt; Clear Download Cache&lt;/strong>. Valve says it doesn't affect installed games, but you'll sign in again.&lt;/li>
&lt;li>&lt;strong>Then:&lt;/strong> check security software and Windows Security's folder protection.&lt;/li>
&lt;li>&lt;strong>Last:&lt;/strong> moving games or reinstalling Steam. Read the warning box before either one.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>I couldn&amp;rsquo;t find a Valve support page for this exact message, and I&amp;rsquo;m not going to invent one. What it does have is the general install and update error article, and that article names the permission requirement and the fix. I&amp;rsquo;ve built the order around it.&lt;/p>
&lt;h2 id="what-the-error-means">What the error means&lt;/h2>
&lt;p>Valve&amp;rsquo;s &lt;a href="https://help.steampowered.com/en/faqs/view/21F5-8D5D-0141-7A5E" rel="noopener">Update &amp;amp; Installation Issues&lt;/a> article covers messages that begin &amp;ldquo;An error occurred while updating&amp;rdquo; or &amp;ldquo;An error occurred while installing&amp;rdquo; a game. It says the error appears when Steam can&amp;rsquo;t complete the installation, and that the specific reason is shown in parentheses at the end of the message. If your message ends with &amp;ldquo;(missing file privileges)&amp;rdquo;, that is the reason Steam is reporting. Valve doesn&amp;rsquo;t define it on that page or on any page I could find.&lt;/p>
&lt;p>Here&amp;rsquo;s what Valve does say, which is the closest thing to a definition:&lt;/p>
&lt;ul>
&lt;li>Steam library folders contain your installed games on disk.&lt;/li>
&lt;li>Those folders need to be writable by all users to update properly.&lt;/li>
&lt;li>Sometimes those user permissions break and need to be refreshed, and the listed fix is &lt;strong>Repair Folder&lt;/strong>.&lt;/li>
&lt;/ul>
&lt;p>Valve doesn&amp;rsquo;t say that this is what &amp;ldquo;missing file privileges&amp;rdquo; means. It&amp;rsquo;s the nearest documented permission requirement, and the repair is the documented way to refresh it. Which file, which account, and what broke are all things Valve&amp;rsquo;s article leaves out, and I can&amp;rsquo;t tell you from here either.&lt;/p>
&lt;p>If the parentheses say something else, for example &amp;ldquo;content file locked&amp;rdquo;, you have a different error. &lt;a href="https://techfuelhq.com/gaming/steam-content-file-locked-fix-2026/">Steam content file locked&lt;/a> handles that one, so I won&amp;rsquo;t repeat it here.&lt;/p>
&lt;h3 id="what-healthy-looks-like-on-my-machine">What healthy looks like on my machine&lt;/h3>
&lt;p>On my bench PC, &lt;code>icacls &amp;quot;C:\Program Files (x86)\Steam\steamapps&amp;quot;&lt;/code> lists the Users group with full access, inherited from the parent folder. Microsoft&amp;rsquo;s icacls reference defines &lt;code>F&lt;/code> as full access and &lt;code>(I)&lt;/code> as inherited from the parent container. That matches Valve&amp;rsquo;s statement that library folders need to be writable by all users. It&amp;rsquo;s one machine with one library, not a survey, and the command only reads permissions. I didn&amp;rsquo;t change any.&lt;/p>
&lt;h2 id="before-you-start-what-touches-your-game-files">Before you start: what touches your game files&lt;/h2>
&lt;p>Some steps below delete, replace or move files. Here&amp;rsquo;s what Valve says each does to installed games.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Step&lt;/th>
&lt;th scope="col">What Valve says it does to installed games&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Step">Restart, Repair Folder&lt;/td>
&lt;td data-label="What Valve says it does to installed games">Restart releases locks. Repair Folder is Valve&amp;rsquo;s listed fix for library folder user permissions that need refreshing. Valve doesn&amp;rsquo;t list anything else it changes.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Step">Clear Download Cache&lt;/td>
&lt;td data-label="What Valve says it does to installed games">Doesn&amp;rsquo;t affect currently installed games. You&amp;rsquo;ll need to sign in again.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Step">Verify integrity of game files&lt;/td>
&lt;td data-label="What Valve says it does to installed games">Checks installed files and fixes them if necessary.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Step">New library folder, moving a game&lt;/td>
&lt;td data-label="What Valve says it does to installed games">Moving relocates a game&amp;rsquo;s files.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Step">Reinstall Steam over the same folder&lt;/td>
&lt;td data-label="What Valve says it does to installed games">Preserves installed games.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Step">Uninstall Steam&lt;/td>
&lt;td data-label="What Valve says it does to installed games">Deletes all game content.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="step-1-restart-steam-and-the-pc">Step 1. Restart Steam and the PC&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> a stuck state or a lock left over from an earlier session.&lt;/p>
&lt;p>Valve&amp;rsquo;s article says to restart both Steam and the computer, because restarting flushes system states and caches, resets other programs, and releases locks on files and other resources. Do it before changing anything else.&lt;/p>
&lt;h2 id="step-2-repair-the-library-folder">Step 2. Repair the library folder&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> broken user permissions on the library. It is the only permission-specific fix in Valve&amp;rsquo;s list.&lt;/p>
&lt;p>Open &lt;strong>Steam &amp;gt; Settings &amp;gt; Storage&lt;/strong>, then the &lt;strong>&amp;hellip;&lt;/strong> menu, then &lt;strong>Repair Folder&lt;/strong>. That is Valve&amp;rsquo;s path as written. If Storage lists more than one drive, I would run it on the drive that holds the game; Valve&amp;rsquo;s article doesn&amp;rsquo;t spell that part out. Let it finish and retry the install or update.&lt;/p>
&lt;p>If you want to look before you repair, the icacls command above shows the folder&amp;rsquo;s permissions without changing them. Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/icacls" rel="noopener">icacls reference&lt;/a> says the same tool can also modify permissions. I&amp;rsquo;d leave that to Repair Folder.&lt;/p>
&lt;h2 id="step-3-clear-the-download-cache">Step 3. Clear the download cache&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> the client&amp;rsquo;s locally cached configuration data, which Valve says the client flushes and fetches again from Steam&amp;rsquo;s servers when you clear it.&lt;/p>
&lt;p>Valve&amp;rsquo;s &lt;a href="https://help.steampowered.com/en/faqs/view/6AD7-820D-8BE5-E51F" rel="noopener">Clear download cache&lt;/a> article says to open &lt;strong>Steam &amp;gt; Settings&lt;/strong>, go to &lt;strong>Downloads&lt;/strong>, click &lt;strong>Clear Download Cache&lt;/strong> at the bottom, and confirm. It says this won&amp;rsquo;t affect your installed games, but you&amp;rsquo;ll need to sign in to Steam again, so have your login ready before you start.&lt;/p>
&lt;h2 id="step-4-run-steam-as-administrator-once-as-a-test">Step 4. Run Steam as administrator once, as a test&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> the problem depending on your normal account&amp;rsquo;s rights.&lt;/p>
&lt;p>Valve&amp;rsquo;s article doesn&amp;rsquo;t list this step. I include it because Microsoft documents how to do it and because the error&amp;rsquo;s wording is about permissions. Treat it as a test, not a fix. No source I read says what running Steam elevated changes on disk, so do it once, then close Steam and open it normally.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows/powertoys/administrator" rel="noopener">PowerToys administrator page&lt;/a> says Windows applications run in user mode by default, and that the simplest way to run one in administrative mode is to right-click it and select &lt;strong>Run as administrator&lt;/strong>. If your account isn&amp;rsquo;t an administrator, Windows asks for the administrator username and password. Close Steam first, start it this way, and retry the update once.&lt;/p>
&lt;p>What the result tells you is my reading, not Valve&amp;rsquo;s: if it only works elevated, the library folder&amp;rsquo;s permissions are the place to look, and Step 2 is the documented repair. Close Steam afterwards and open it normally.&lt;/p>
&lt;h2 id="step-5-check-windows-securitys-folder-protection">Step 5. Check Windows Security&amp;rsquo;s folder protection&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> Windows blocking Steam from changing files in a protected folder.&lt;/p>
&lt;p>This applies only if &lt;strong>Controlled folder access&lt;/strong> is on. Microsoft says it is off by default. When it&amp;rsquo;s on, it stops untrusted apps from modifying or deleting files in protected folders. Microsoft&amp;rsquo;s Learn page lists the default protected folders as the user&amp;rsquo;s Documents, Favorites, Music, Pictures and Videos folders plus the Public Documents, Music, Pictures and Videos folders, and says you can add more folders. Its Support page also names Desktop. Program Files isn&amp;rsquo;t on either list, so a Steam library there isn&amp;rsquo;t covered by default. A library inside a folder you added yourself is the clear case to check, since Microsoft says subfolders of an added folder are protected too.&lt;/p>
&lt;p>To check: open Windows Security, go to &lt;strong>Virus &amp;amp; threat protection &amp;gt; Manage ransomware protection&lt;/strong>. Microsoft&amp;rsquo;s support page says Controlled folder access shows a notification when it blocks an app, and that you can allow the app by selecting the message and choosing &lt;strong>Add an allowed app&lt;/strong>, or by using &lt;strong>Allow an app through Controlled folder access&lt;/strong>. It also cautions that any app you add can reach the files in the protected folders, so only add Steam if the block is actually from it.&lt;/p>
&lt;p>Microsoft says Defender automatically trusts most apps based on prevalence and reputation. It takes a minute to look, and if the setting is off you can move on.&lt;/p>
&lt;h2 id="step-6-antivirus-and-firewall">Step 6. Antivirus and firewall&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> security software interfering with Steam&amp;rsquo;s disk operations.&lt;/p>
&lt;p>Valve says antivirus software hooks deep into the system and can affect disk and network operations, and that it may be necessary to add exceptions for Steam, for example by excluding Steam library folders from live monitoring. Valve&amp;rsquo;s &lt;a href="https://help.steampowered.com/en/faqs/view/1F39-DCB4-FF28-5748" rel="noopener">Programs Which May Interfere with Steam&lt;/a> article repeats the point and also covers anti-spyware, firewalls and other categories. Valve&amp;rsquo;s wording for testing is to temporarily disable the software. I&amp;rsquo;d rather add the exclusion than leave protection off, but that&amp;rsquo;s my preference, not Valve&amp;rsquo;s.&lt;/p>
&lt;h2 id="step-7-verify-the-games-files">Step 7. Verify the game&amp;rsquo;s files&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> a damaged file in the game&amp;rsquo;s own install.&lt;/p>
&lt;p>In your Library, right-click the game, choose &lt;strong>Properties&lt;/strong>, open &lt;strong>Installed Files&lt;/strong>, and click &lt;strong>Verify integrity of game files&lt;/strong>. Valve says it can take several minutes.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Warning, from Valve:&lt;/strong> don&amp;rsquo;t run verification while defragmenting your drive or scanning for viruses, and don&amp;rsquo;t run it for more than one game at a time. One or more files failing to verify is normal for most games, Valve says, and can be ignored.&lt;/p>&lt;/blockquote>
&lt;p>Valve&amp;rsquo;s article doesn&amp;rsquo;t cover a stall at 0%. If it&amp;rsquo;s not moving after a long wait, I&amp;rsquo;d stop and go to Step 8 rather than starting it over.&lt;/p>
&lt;h2 id="step-8-check-the-drive-and-memory">Step 8. Check the drive and memory&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> a failing drive or bad memory as the underlying cause.&lt;/p>
&lt;p>Valve&amp;rsquo;s advanced list says storage devices can be affected by file corruption, especially older ones or ones under heavy load. For Windows it gives &lt;strong>This PC &amp;gt; right-click the drive &amp;gt; Properties &amp;gt; Tools &amp;gt; Error checking&lt;/strong>. It lists the Windows Memory Diagnostic as the memory check (run &lt;code>mdsched&lt;/code> from Start). It also says overclocking can cause memory and file corruption and should be disabled, usually in the BIOS. Valve recommends working with a local IT specialist for these advanced steps.&lt;/p>
&lt;p>If you want to read the drive&amp;rsquo;s own health numbers first, my &lt;a href="https://techfuelhq.com/articles/ssd-health-check-2026/">SSD health check&lt;/a> does that without installing anything.&lt;/p>
&lt;h2 id="step-9-test-with-a-second-library-folder">Step 9. Test with a second library folder&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> the drive or folder you&amp;rsquo;ve been using.&lt;/p>
&lt;p>Valve suggests testing by installing on another hard drive: &lt;strong>Steam &amp;gt; Settings &amp;gt; Storage &amp;gt; +&lt;/strong> creates a new library folder on a different drive. Install a small game there as a test.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Warning: moving files.&lt;/strong> Valve&amp;rsquo;s article says you can move already installed games into a new library folder. A move relocates the game&amp;rsquo;s files. Valve doesn&amp;rsquo;t say what happens to a move that fails partway, so I&amp;rsquo;d test with a fresh install first and move only after that works. If you&amp;rsquo;ve added anything of your own to a game&amp;rsquo;s folder, such as mods or custom configs, copy it somewhere else first. That precaution is mine.&lt;/p>&lt;/blockquote>
&lt;h2 id="step-10-reinstall-steam-over-the-same-folder">Step 10. Reinstall Steam over the same folder&lt;/h2>
&lt;p>&lt;strong>Rules out:&lt;/strong> damaged Steam client or service files.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Warning: don&amp;rsquo;t uninstall first.&lt;/strong> Valve says uninstalling Steam deletes all game content. Its instruction is to download the installer and reinstall to the same location where Steam is already installed, which it says preserves installed games.&lt;/p>&lt;/blockquote>
&lt;p>My &lt;a href="https://techfuelhq.com/gaming/steam-not-opening-2026/">Steam not opening guide&lt;/a> walks through that reinstall in detail.&lt;/p>
&lt;h2 id="when-to-stop-and-contact-steam-support">When to stop and contact Steam Support&lt;/h2>
&lt;p>If you&amp;rsquo;ve been through Step 10 and the message returns, contact Steam Support at help.steampowered.com. Tell them the game, the library path, and which steps you&amp;rsquo;ve done. If the problem is slow downloads rather than a permission error, &lt;a href="https://techfuelhq.com/gaming/steam-slow-download-speed-2026/">Steam slow download speed&lt;/a> is a better place to start. If a game installs but won&amp;rsquo;t start, see &lt;a href="https://techfuelhq.com/gaming/steam-games-not-launching-2026/">Steam games not launching&lt;/a>. The &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">diagnostic workbench&lt;/a> can keep a record of what you tried.&lt;/p>
&lt;h2 id="finding-steam-in-program-files">Finding Steam in Program Files&lt;/h2>
&lt;p>If you can&amp;rsquo;t find Steam where you expect it, look in &lt;code>Program Files (x86)&lt;/code>. On my PC the install is &lt;code>C:\Program Files (x86)\Steam&lt;/code>, which is what the registry reports under &lt;code>HKCU\Software\Valve\Steam&lt;/code> as &lt;code>SteamPath&lt;/code> (the value is stored in lowercase with forward slashes: &lt;code>c:/program files (x86)/steam&lt;/code>). My &lt;code>steamapps\libraryfolders.vdf&lt;/code> lists that same folder as the only library. If you added a library on another drive, your games live there instead, and &lt;strong>Steam &amp;gt; Settings &amp;gt; Storage&lt;/strong> is where Valve&amp;rsquo;s article has you add a library folder.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/21F5-8D5D-0141-7A5E" rel="noopener">Steam Support: Update &amp;amp; Installation Issues&lt;/a>, read 2026-11-17.&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/6AD7-820D-8BE5-E51F" rel="noopener">Steam Support: Clear download cache&lt;/a>, read 2026-11-17.&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/0C48-FCBD-DA71-93EB" rel="noopener">Steam Support: Verify Integrity of Game Files&lt;/a>, read 2026-11-17.&lt;/li>
&lt;li>&lt;a href="https://help.steampowered.com/en/faqs/view/1F39-DCB4-FF28-5748" rel="noopener">Steam Support: Programs Which May Interfere with Steam&lt;/a>, read 2026-11-17.&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/defender-endpoint/controlled-folder-access-overview" rel="noopener">Microsoft Learn: Controlled folder access overview&lt;/a>, read 2026-11-17.&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/security/threat-malware-protection/virus-and-threat-protection-in-the-windows-security-app" rel="noopener">Microsoft Support: Virus and Threat Protection in the Windows Security App&lt;/a>, read 2026-11-17.&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows/powertoys/administrator" rel="noopener">Microsoft Learn: Run PowerToys in Administrator Mode&lt;/a>, read 2026-11-17. Used only for its explanation of Run as administrator.&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/icacls" rel="noopener">Microsoft Learn: icacls&lt;/a>, read 2026-11-17.&lt;/li>
&lt;/ul></description></item><item><title>Optimizations for Windowed Games: On or Off in Windows 11? (2026)</title><link>https://techfuelhq.com/gaming/optimizations-for-windowed-games-on-or-off-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gaming/optimizations-for-windowed-games-on-or-off-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;p>Have it on. Microsoft&amp;rsquo;s support page says Optimizations for windowed games &amp;ldquo;improves gaming performance for DirectX 10 and DirectX 11 games running in windowed and borderless windowed modes&amp;rdquo; by moving compatible games from the legacy blt presentation model to the newer flip model. Microsoft credits that with lower frame latency and with unlocking Auto HDR and variable refresh rate (VRR) on supported displays.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s pages do not say whether the switch is on by default, so check yours. If one game tears and Microsoft&amp;rsquo;s two first fixes don&amp;rsquo;t cure it, turn the setting off for that game, not for the PC. The switch is at Settings &amp;gt; System &amp;gt; Display &amp;gt; Graphics, and a per-app override sits further down the same page. Both paths are below.&lt;/p>
&lt;p>This page is about the Windows 11 switch. A different setting with a nearly identical name, the Compatibility tab&amp;rsquo;s checkbox for exclusive-fullscreen games, has its own page: &lt;a href="https://techfuelhq.com/gaming/disable-fullscreen-optimizations-2026/">Disable fullscreen optimizations&lt;/a> explains that one and how the two differ.&lt;/p>
&lt;h2 id="on-or-off-by-situation">On or off, by situation&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Situation&lt;/th>
&lt;th scope="col">Setting&lt;/th>
&lt;th scope="col">What Microsoft says&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Situation">A DX10 or DX11 game in windowed or borderless windowed mode&lt;/td>
&lt;td data-label="Setting">&lt;strong>On&lt;/strong>&lt;/td>
&lt;td data-label="What Microsoft says">This is the case the setting is written for.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Situation">A DX12 game&lt;/td>
&lt;td data-label="Setting">Nothing to set&lt;/td>
&lt;td data-label="What Microsoft says">&amp;ldquo;You don&amp;rsquo;t need to worry about DX12 games as they already take advantage of the new presentation mode.&amp;rdquo;&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Situation">A game running in true Fullscreen&lt;/td>
&lt;td data-label="Setting">Not this setting&lt;/td>
&lt;td data-label="What Microsoft says">&amp;ldquo;When you&amp;rsquo;re running in Fullscreen, a similar optimization already exists.&amp;rdquo; See &lt;a href="https://techfuelhq.com/gaming/disable-fullscreen-optimizations-2026/">Disable fullscreen optimizations&lt;/a>.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Situation">You use Auto HDR&lt;/td>
&lt;td data-label="Setting">&lt;strong>On&lt;/strong>&lt;/td>
&lt;td data-label="What Microsoft says">Turning on Auto HDR turns this on automatically, and you must turn Auto HDR off before you can turn this off.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Situation">A windowed game tears with V-Sync off at high frame rates&lt;/td>
&lt;td data-label="Setting">Fix the tearing first; if that fails, &lt;strong>off for that game&lt;/strong>&lt;/td>
&lt;td data-label="What Microsoft says">Match the game&amp;rsquo;s frame rate to the monitor&amp;rsquo;s refresh rate or turn on the game&amp;rsquo;s V-Sync. If neither works, opt out (2022 announcement).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Situation">A VRR monitor&lt;/td>
&lt;td data-label="Setting">&lt;strong>On&lt;/strong>&lt;/td>
&lt;td data-label="What Microsoft says">Flip model works with VRR, but &amp;ldquo;tearing is still possible if you exceed the refresh rate of the monitor.&amp;rdquo;&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Situation">One game crashes or misbehaves in windowed mode&lt;/td>
&lt;td data-label="Setting">Testing it &lt;strong>off for that game&lt;/strong> is my judgment&lt;/td>
&lt;td data-label="What Microsoft says">Microsoft does not list crashes as a reason to opt out. Its 2022 post says it disables the feature by default for apps with known issues.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>I run a 7800X3D and an RTX 5080 into a 4K 120 Hz OLED with variable refresh rate. On that setup I&amp;rsquo;d have it on and set the game&amp;rsquo;s frame rate to match the refresh rate rather than opt out, which is the first fix Microsoft names for tearing. The V-Sync guide covers that in &lt;a href="https://techfuelhq.com/gaming/vsync-on-or-off-2026/">VSync on or off&lt;/a>.&lt;/p>
&lt;h2 id="what-it-changes">What it changes&lt;/h2>
&lt;p>Presentation is how a game&amp;rsquo;s finished frames reach the screen. Microsoft&amp;rsquo;s February 2022 announcement, written when the setting was still limited to Windows Insider build 22545, defines the setting as one that &amp;ldquo;affects presentation modes used in Windowed and Borderless Windowed DX10/DX11 games,&amp;rdquo; and says that more technically it moves apps &amp;ldquo;from the legacy blt-model presentation to modern flip-model.&amp;rdquo;&lt;/p>
&lt;p>Microsoft&amp;rsquo;s developer guidance on flip model says flip-model presents can make windowed mode &amp;ldquo;effectively equivalent or better when compared to the classic &amp;lsquo;fullscreen exclusive&amp;rsquo; mode,&amp;rdquo; and that depending on window and buffer configuration the system can skip desktop composition entirely and send application frames to the screen &amp;ldquo;in the same way that exclusive fullscreen does.&amp;rdquo; Microsoft calls those paths DirectFlip and Independent Flip. It does not say which one any given game lands on, but it points to PresentMon as the tool that shows which was used.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s 2019 fullscreen post describes what windowed play has cost. When a game runs in a borderless window, the Desktop Window Manager controls the display, and &amp;ldquo;this control has historically resulted in a slight performance overhead vs FSE.&amp;rdquo;&lt;/p>
&lt;h2 id="who-should-turn-it-off-and-when">Who should turn it off, and when&lt;/h2>
&lt;p>Microsoft gives one reason to opt out, and I&amp;rsquo;m adding none.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Tearing.&lt;/strong> With V-Sync off, a new frame can be ready before the previous one is shown. Microsoft says that at high frame rates this &amp;ldquo;may lead to screen tearing when this feature is turned on.&amp;rdquo; Its fixes, in the order it lists them, are to configure the game&amp;rsquo;s frame rate to match the monitor&amp;rsquo;s refresh rate, to turn on V-Sync in the game, and, if neither works, to opt out of the feature. It also suggests a VRR monitor, with the warning that tearing is still possible above its refresh rate.&lt;/li>
&lt;li>&lt;strong>A game Microsoft has already flagged.&lt;/strong> This is not a reason from Microsoft to opt out, but it is related. Its 2022 post says it disables the feature by default for apps with known issues, and that you may see a warning message if you uncheck the option (that post&amp;rsquo;s per-app box was worded &amp;ldquo;Don&amp;rsquo;t use Optimizations for windowed games&amp;rdquo;), which &amp;ldquo;means that the app may crash or there is an issue with how the feature interacts with the title.&amp;rdquo; Microsoft does not say what the warning looks like in today&amp;rsquo;s Settings.&lt;/li>
&lt;/ul>
&lt;p>One thing is not a reason: Auto HDR. You cannot turn this setting off while Auto HDR is on. If you want Auto HDR off for one game, Microsoft&amp;rsquo;s per-app page has its own Don&amp;rsquo;t use Auto HDR checkbox.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s support page does not state the default for the system-wide switch, so check the state on your own PC rather than assuming. Its 2023 redesign post adds that Microsoft has &amp;ldquo;disabled or enabled settings by default for some specific apps,&amp;rdquo; so not every app will match the system-wide state.&lt;/p>
&lt;h2 id="where-the-switch-is">Where the switch is&lt;/h2>
&lt;p>&lt;strong>System-wide.&lt;/strong> Microsoft&amp;rsquo;s support page, written for Windows 11, gives these steps: Start, Settings, System, Display, Graphics, then under Default settings turn on the switch beside Optimizations for windowed games, and restart your game. Microsoft&amp;rsquo;s 2023 redesign of the page (first shipped to Insiders in build 25281) folded the old Default graphics settings page into the Graphics page as a group called System-wide settings at the top. Microsoft&amp;rsquo;s own pages use both names, so look for the switch under whichever heading your build shows. I did not open the Settings app on the bench machine for this page, so I can&amp;rsquo;t tell you which one my build shows.&lt;/p>
&lt;p>&lt;strong>Per app.&lt;/strong> In Settings &amp;gt; System &amp;gt; Display &amp;gt; Graphics, under Custom options for apps, select the game, then Options. The window offers GPU preference (if you have more than one GPU), the Auto HDR checkbox and the Optimizations for windowed games switch. Turn the last one off, select Save, and restart the game. If the game isn&amp;rsquo;t listed, Microsoft&amp;rsquo;s redesign post says to add it with the Add desktop app or Add Windows Store app button.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s 2023 post says the per-app preference overrides the system-wide one, and gives this example: &amp;ldquo;even if you disable System-wide settings for a feature, you can enable it for a specific application.&amp;rdquo; It also says the settings apply only to eligible games, and a Reset button returns an app to the defaults.&lt;/p>
&lt;h2 id="what-windows-stores-on-this-machine">What Windows stores on this machine&lt;/h2>
&lt;p>I read the registry key where Windows keeps per-user graphics preferences on the bench machine, read-only, on 2026-11-17. &lt;code>HKCU\Software\Microsoft\DirectX\UserGpuPreferences&lt;/code> holds a &lt;code>DirectXUserGlobalSettings&lt;/code> string reading &lt;code>AutoHDREnable=0;SwapEffectUpgradeEnable=1;&lt;/code>, followed by per-program strings named by executable path. Most are &lt;code>GpuPreference=&lt;/code> entries for utility and wallpaper apps, four game executables carry &lt;code>AppStatus=&lt;/code> values (0 on three, 1 on one), and four game executables carry an &lt;code>AutoHDREnable=2097;&lt;/code> string.&lt;/p>
&lt;p>The names look related to the Auto HDR and presentation features Microsoft describes, but none of the Microsoft pages I read documents those strings, and I changed nothing to see which switch moves which value. So I won&amp;rsquo;t give you a registry edit. Use the Settings page, which is what Microsoft documents.&lt;/p>
&lt;h2 id="how-to-check-whether-it-helped">How to check whether it helped&lt;/h2>
&lt;p>Microsoft says to restart the game after changing the setting, so do that first. Microsoft&amp;rsquo;s flip-model guidance names PresentMon for seeing which presentation path a game used, which is a better test than a feeling. Change one switch at a time. If the stutter you were chasing stays, &lt;a href="https://techfuelhq.com/gaming/hardware-accelerated-gpu-scheduling-on-or-off-2026/">HAGS&lt;/a> and &lt;a href="https://techfuelhq.com/gaming/game-mode-on-or-off-2026/">Game Mode&lt;/a> are separate Windows switches with their own pages, and &lt;a href="https://techfuelhq.com/articles/pc-stuttering-in-games-2026/">why a PC stutters in games&lt;/a> covers telling stutter from low FPS. The &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">diagnostic workbench&lt;/a> keeps a log of what you changed.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s claims here are about latency, and I have not measured latency; I have no latency hardware. I also looked for a controlled on/off test of this setting from a named publisher and didn&amp;rsquo;t find one, so I can&amp;rsquo;t give you a number. If you use frame generation, &lt;a href="https://techfuelhq.com/articles/frame-generation-explained-2026/">frame generation explained&lt;/a> is a separate topic. If a game&amp;rsquo;s DX11 and DX12 modes behave differently, &lt;a href="https://techfuelhq.com/gaming/dx12-vs-dx11-fps-2026/">DX12 vs DX11&lt;/a> covers why.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/hardware/display-graphics/optimizations-for-windowed-games-in-windows-11" rel="noopener">Microsoft Support, Optimizations for windowed games in Windows 11&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/updates-in-graphics-and-gaming/" rel="noopener">Microsoft DirectX Developer Blog, Updates in Graphics and Gaming, February 16, 2022&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/navigating-the-redesigned-graphics-settings-page/" rel="noopener">Microsoft DirectX Developer Blog, Navigating the redesigned graphics settings page, January 19, 2023&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/dxgi-flip-model/" rel="noopener">Microsoft DirectX Developer Blog, For best performance, use DXGI flip model, April 9, 2018&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows/win32/direct3ddxgi/for-best-performance--use-dxgi-flip-model" rel="noopener">Microsoft Learn, For best performance, use DXGI flip model&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/demystifying-full-screen-optimizations/" rel="noopener">Microsoft DirectX Developer Blog, Demystifying Fullscreen Optimizations, December 17, 2019&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>NVIDIA Reflex Low Latency: On, On + Boost, or Off?</title><link>https://techfuelhq.com/gaming/nvidia-reflex-on-or-off-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gaming/nvidia-reflex-on-or-off-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · NVIDIA Reflex Low Latency&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Reflex Low Latency: On,&lt;/strong> in every game that has the option. NVIDIA's own latency guide says to turn it on whenever the game offers it.&lt;/li>
&lt;li>&lt;strong>On + Boost&lt;/strong> only if lowest latency matters more to you than power draw. NVIDIA calls the benefit very modest.&lt;/li>
&lt;li>&lt;strong>Off&lt;/strong> is for comparing. The NVIDIA pages I read describe no cost for plain On beyond a developer checklist limit of 4 percent FPS impact.&lt;/li>
&lt;li>&lt;strong>Driver Low Latency Mode:&lt;/strong> leave it alone in games with Reflex. NVIDIA says Reflex overrides the driver's Ultra mode when both are enabled.&lt;/li>
&lt;li>&lt;strong>Where it lives:&lt;/strong> in the game's own settings menu. I found no Reflex Low Latency entry in the NVIDIA app's driver-settings strings.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>I run an RTX 5080, and on the bench machine &lt;code>nvidia-smi&lt;/code> reports driver 621.24 today. That is the card behind this page, but every claim below comes from NVIDIA&amp;rsquo;s own documentation, not from a latency test of mine. I did not launch a game for this page, so the in-game labels are as NVIDIA&amp;rsquo;s pages describe them.&lt;/p>
&lt;h2 id="what-the-three-settings-are">What the three settings are&lt;/h2>
&lt;p>Reflex Low Latency is a mode a game developer builds into the game. NVIDIA&amp;rsquo;s launch article says it lines the game engine&amp;rsquo;s work up so it finishes just in time for rendering, which empties the GPU&amp;rsquo;s render queue and eases the back pressure that queue puts on the CPU. The switch is in the game&amp;rsquo;s own settings: NVIDIA&amp;rsquo;s latency guide tells you to find it in the game&amp;rsquo;s options menu.&lt;/p>
&lt;p>The game offers up to three positions: Off, On and On + Boost. Boost is the part that needs a decision, and it is covered next. For compatibility, NVIDIA says the Reflex Low Latency mode supports GeForce GTX 900 series and newer, and NVIDIA keeps a list of supported games on its Reflex page.&lt;/p>
&lt;p>NVIDIA&amp;rsquo;s developer guide for integrating Reflex also states that the mode&amp;rsquo;s default state should be On, and lists Off, On and On + Boost as the three modes a game has to support. It adds that Reflex On should not cost more than 4 percent of FPS. That is a developer&amp;rsquo;s pass/fail checklist item, not a measurement of any game, so I would not read it as a promise.&lt;/p>
&lt;h2 id="on-or-on--boost">On or On + Boost&lt;/h2>
&lt;p>NVIDIA&amp;rsquo;s description of Boost is consistent across its pages. Boost overrides the GPU&amp;rsquo;s power-saving features so clocks stay high when the game is CPU-bound, and NVIDIA says that can reduce latency slightly when the GPU is significantly underutilized and the CPU submits the final rendering work in a large batch. It also says the higher clocks can consume significantly more power, and that if you do not want that trade you can use Reflex On without Boost. Its Reflex launch article calls the Boost benefit very modest, though it can help squeeze every last millisecond out of the pipeline.&lt;/p>
&lt;p>Two more NVIDIA statements bear on the choice:&lt;/p>
&lt;ul>
&lt;li>For Counter-Strike 2, NVIDIA says Enabled + Boost can reduce latency further at the cost of extra power usage and a slightly lower frame rate, and recommends it only for players who put lowest latency ahead of highest frame rate.&lt;/li>
&lt;li>In the same Counter-Strike 2 article, NVIDIA also says Reflex is most effective when the system is GPU-bound or the GPU is under high utilization, because that is when the CPU can run ahead and build up the render queue.&lt;/li>
&lt;/ul>
&lt;p>My call follows from those lines. Start with On. Move to On + Boost only if you play a latency-sensitive game, want every last bit, and accept the extra power. NVIDIA&amp;rsquo;s pages give no reason to prefer On + Boost for general play. I have not measured the difference on my own system, so I will not tell you how many milliseconds it is worth.&lt;/p>
&lt;p>Off is for A/B testing or for ruling Reflex out when you are chasing a problem in one specific game. NVIDIA&amp;rsquo;s pages describe no downside to plain On beyond that developer checklist figure.&lt;/p>
&lt;h2 id="reflex-versus-the-drivers-low-latency-mode">Reflex versus the driver&amp;rsquo;s Low Latency Mode&lt;/h2>
&lt;p>They are different switches. Low Latency Mode is a driver setting with three values. NVIDIA&amp;rsquo;s Control Panel Help describes Off (default) as prioritizing render throughput by letting games queue frames, On as limiting queued frames to one, and Ultra as fully minimizing queued frames. When NVIDIA introduced the mode in August 2019, it said On limits the queue to one frame, Ultra submits the frame just in time for the GPU, and in DirectX 12 and Vulkan games the game decides when to queue the frame. I found no newer NVIDIA statement that changes that DirectX 12 and Vulkan point, so check it before you rely on the driver mode there.&lt;/p>
&lt;p>For which one wins, NVIDIA is direct:&lt;/p>
&lt;ul>
&lt;li>If the game supports Reflex, NVIDIA recommends the Reflex mode over the driver&amp;rsquo;s Ultra mode.&lt;/li>
&lt;li>If Reflex is not available, NVIDIA&amp;rsquo;s guide names the driver&amp;rsquo;s Ultra mode as your next best option.&lt;/li>
&lt;li>NVIDIA says Reflex operates independently of the driver&amp;rsquo;s Ultra mode, and that if both are enabled, Reflex overrides Ultra Low Latency functionality. The guide says nothing about the driver&amp;rsquo;s On setting.&lt;/li>
&lt;/ul>
&lt;p>NVIDIA&amp;rsquo;s reason for the ranking is that Reflex is built into the game, so it can control the back pressure the CPU gets from the render queue and later pipeline stages. The driver&amp;rsquo;s mode can often reduce the render queue, NVIDIA says, but it cannot remove that back pressure on the game and CPU side.&lt;/p>
&lt;p>&lt;strong>Where Low Latency Mode lives now.&lt;/strong> NVIDIA&amp;rsquo;s retirement notice for the classic Control Panel says the NVIDIA app&amp;rsquo;s Graphics &amp;gt; Program Settings replaces Manage 3D Settings. The app on this machine, NVIDIA App 11.0.9.585, ships a Low Latency Mode entry with Off, On and Ultra in its bundled UI strings. One detail from those strings: the entry carries an error message that says to disable Smooth Motion to configure the feature. The full list of driver settings, with what I would change, is on the &lt;a href="https://techfuelhq.com/gaming/nvidia-control-panel-best-settings-2026/">NVIDIA Control Panel best settings&lt;/a> page.&lt;/p>
&lt;h2 id="does-reflex-cap-your-fps">Does Reflex cap your FPS?&lt;/h2>
&lt;p>Not as a fixed number. NVIDIA&amp;rsquo;s launch article compares Reflex Low Latency to a good in-game frame limiter that stalls the game in the right places, and then says that unlike a limiter locked to one frame rate, Reflex lets your frame rate run faster than a limit would, which it likens to a dynamic limiter.&lt;/p>
&lt;p>Two details sit on top of that. The Reflex SDK has a separate frame rate limiter sub-feature that a game can expose, and NVIDIA&amp;rsquo;s developer guide says the sub-features are distinct with no cross-dependencies. And with G-SYNC and V-Sync together, NVIDIA&amp;rsquo;s guide says Reflex automatically caps the frame rate below the refresh rate. The next section covers that case.&lt;/p>
&lt;h2 id="g-sync-and-v-sync">G-SYNC and V-Sync&lt;/h2>
&lt;p>NVIDIA&amp;rsquo;s latency guide says V-Sync causes back pressure that reverberates through the system, and that it recommends V-Sync off if you will tolerate tearing. For G-SYNC owners who do not want to tear, it says to keep V-Sync on while using Reflex or the driver&amp;rsquo;s Ultra mode, which automatically caps the frame rate below the refresh rate. It states that this gives slightly higher latency than uncapped frame rates with Reflex on.&lt;/p>
&lt;p>The guide also says driver V-Sync only works for fullscreen applications and that Microsoft hybrid laptops do not support the driver setting. If you play in windowed mode or on one of those laptops, it says to use the in-game V-Sync for G-SYNC plus V-Sync plus Reflex. That guide dates from 2020, so treat the windowed-mode statement as NVIDIA&amp;rsquo;s 2020 position. For the current driver setup and the full table of V-Sync choices by monitor type, see my &lt;a href="https://techfuelhq.com/gaming/vsync-on-or-off-2026/">V-Sync on or off&lt;/a> page and the &lt;a href="https://techfuelhq.com/articles/fix-screen-tearing-2026/">screen tearing guide&lt;/a>.&lt;/p>
&lt;p>One result from NVIDIA&amp;rsquo;s Streamline guide matters if you do not have a VRR monitor. That guide is developer documentation on GitHub, the copy I read carries no date, and it gives no reason for any row of its table, so I am reporting the rows and nothing more. Its table of supported configurations lists V-Sync on, VRR off and frame generation off as a case with no latency reduction from Reflex. With V-Sync on, the table lists a reduction when VRR is on or when frame generation is on. It lists a GPU-bound game as a reduction regardless, and a CPU-bound game as no reduction. NVIDIA&amp;rsquo;s Boost description, covered above, is aimed at CPU-bound cases, and I did not find NVIDIA reconciling the two statements.&lt;/p>
&lt;h2 id="frame-generation">Frame generation&lt;/h2>
&lt;p>NVIDIA ties the two together. Its DLSS 3 announcement describes DLSS 3 as combining Super Resolution, Frame Generation and Reflex, and its Streamline developer guide says a game that integrates DLSS Frame Generation has to integrate Reflex through Streamline too. The pages I read do not say whether the in-game Reflex setting can still be changed once frame generation is on, so check your game&amp;rsquo;s menu rather than assume.&lt;/p>
&lt;p>NVIDIA says its DLSS 4.5 Multi Frame Generation combines with Reflex so generated frames have minimal impact on responsiveness. NVIDIA gives no measurement with that statement, so I treat it as a design claim. The &lt;a href="https://techfuelhq.com/articles/frame-generation-explained-2026/">frame generation guide&lt;/a> covers how the generation modes differ.&lt;/p>
&lt;p>One NVIDIA instruction changes the sync advice above. NVIDIA&amp;rsquo;s March 2026 notes say the NVIDIA app&amp;rsquo;s Dynamic Multi Frame Generation mode is not compatible with frame rate limiters or V-Sync. If you use that mode, do not apply the G-SYNC plus V-Sync plus cap recipe on top of it.&lt;/p>
&lt;h2 id="fortnite-counter-strike-2-and-valorant">Fortnite, Counter-Strike 2 and Valorant&lt;/h2>
&lt;p>NVIDIA documents the setting for all three, but in old articles: Fortnite is September 2020, Valorant&amp;rsquo;s steps are from a March 2022 guide written around the GeForce Experience overlay, and Counter-Strike 2 is September 2023. I did not launch any of the games, so confirm the label in your current build.&lt;/p>
&lt;h3 id="fortnite">Fortnite&lt;/h3>
&lt;p>NVIDIA&amp;rsquo;s Fortnite article, dated September 17, 2020, tells you to scroll down the Video Settings menu to NVIDIA Reflex Low Latency and select On. On GeForce RTX GPUs it also offers On + Boost, which NVIDIA says overrides GPU power saving to deliver higher performance and lower latency. If you want to watch latency while you play, the same article says to enable Latency Markers in Video Settings and then Latency Debug Stats in the Game UI menu. NVIDIA&amp;rsquo;s April 2021 article says Fortnite got a Boost optimization for CPU-bound scenes where the render submission thread is the limit, and that Valorant&amp;rsquo;s was still to come as of that article.&lt;/p>
&lt;h3 id="counter-strike-2">Counter-Strike 2&lt;/h3>
&lt;p>NVIDIA&amp;rsquo;s Counter-Strike 2 article, dated September 27, 2023, says to open the game, go to Settings, then Video, then Advanced Video, and set NVIDIA Reflex Low Latency to Enabled. It also lists Enabled + Boost, with the power and frame rate trade described above. NVIDIA says it worked with Valve on the integration.&lt;/p>
&lt;h3 id="valorant">Valorant&lt;/h3>
&lt;p>NVIDIA&amp;rsquo;s Reflex Analyzer guide, dated March 7, 2022, says to click the cog at the top right of the main menu, go to settings, and enable NVIDIA Reflex under the General tab; it names no On or Boost choice. NVIDIA&amp;rsquo;s April 2021 article says each Reflex game has On and Boost Mode, and it is writing about Fortnite and Valorant. My advice is the same as above: On first, Boost only if latency outranks power.&lt;/p>
&lt;h2 id="reflex-frame-warp">Reflex Frame Warp&lt;/h2>
&lt;p>NVIDIA&amp;rsquo;s developer page says Reflex consists of two technologies, Reflex Low Latency mode and Reflex Frame Warp. The same page tells developers to sign up to be notified when Frame Warp is available for general integration. Everything on this page is about Low Latency.&lt;/p>
&lt;p>If a game has no Reflex entry, there is nothing to switch. The next step is the driver&amp;rsquo;s Low Latency Mode for that game, covered above, and the setting list on the &lt;a href="https://techfuelhq.com/gaming/nvidia-control-panel-best-settings-2026/">Control Panel page&lt;/a>. If frame pacing rather than latency is the complaint, start with the &lt;a href="https://techfuelhq.com/articles/pc-stuttering-in-games-2026/">stuttering guide&lt;/a>, and make sure the driver you are running is the one you meant to install, as in &lt;a href="https://techfuelhq.com/articles/game-ready-vs-studio-driver-2026/">Game Ready vs Studio&lt;/a>.&lt;/p></description></item><item><title>NVIDIA Control Panel Best Settings for Gaming (2026)</title><link>https://techfuelhq.com/gaming/nvidia-control-panel-best-settings-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gaming/nvidia-control-panel-best-settings-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · NVIDIA Control Panel best settings&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Change:&lt;/strong> G-SYNC on if your monitor supports it, a frame rate cap per game, Low Latency Mode per game for titles without Reflex, and Vertical sync to suit your monitor type.&lt;/li>
&lt;li>&lt;strong>Leave on default or Application-controlled:&lt;/strong> antialiasing, anisotropic filtering, texture filtering, threaded optimization, CUDA Memory Fallback, Resizable BAR, Shader Cache Size.&lt;/li>
&lt;li>&lt;strong>Where it lives:&lt;/strong> NVIDIA says the app's Graphics > Program Settings replaces Manage 3D Settings, and display options are in the app's System tab. The classic Control Panel is retired for GeForce.&lt;/li>
&lt;li>&lt;strong>No frame rate promises:&lt;/strong> I list only what NVIDIA documents each setting as doing.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>Nearly every &amp;ldquo;best settings&amp;rdquo; list for this panel is a list of defaults with a few opinions in it. This one separates NVIDIA&amp;rsquo;s own description of each setting from my call, and my call is usually &amp;ldquo;leave it&amp;rdquo;. I run an RTX 5080 on driver 621.24 and NVIDIA App 11.0.9.585, read from the bench machine today. I did not open the app or the panel for this page, so everything below is NVIDIA&amp;rsquo;s documentation plus the settings text that ships inside the app.&lt;/p>
&lt;h2 id="where-the-settings-live-now">Where the settings live now&lt;/h2>
&lt;p>NVIDIA&amp;rsquo;s May 2026 driver announcement says the classic NVIDIA Control Panel is retiring for Game Ready and Studio drivers. Existing installs stay on your system unless you do a clean installation, you can still download it from the Microsoft Store, and NVIDIA says it will not add features, fixes or other changes. RTX PRO users keep it until NVIDIA migrates the professional features.&lt;/p>
&lt;p>For GeForce cards, NVIDIA says the app&amp;rsquo;s Graphics &amp;gt; Program Settings replaces the Control Panel&amp;rsquo;s 3D Settings &amp;gt; Manage 3D Settings screen, and that all other settings, display options included, are in the app&amp;rsquo;s System tab. The app&amp;rsquo;s own text also has Global Settings and Program Settings labels, a &amp;ldquo;Show Legacy Settings&amp;rdquo; toggle, and a &amp;ldquo;Go to Legacy Control Panel&amp;rdquo; link. I did not open the app, so I cannot tell you which entries the legacy toggle reveals.&lt;/p>
&lt;p>One more first-hand note: the app strings on this machine carry a name for most Manage 3D Settings entries, and I found none for these entries that the Help reference lists: Ambient Occlusion, Buffer-flipping mode, CUDA - Double precision, Deep color for 3D applications, Multi-display/mixed-GPU acceleration, Preferred refresh rate, Preferred graphics processor, Antialiasing line gamma, Unified back/depth buffer and SILK Smoothness. A missing string does not prove a setting is gone, so I list them as Help-only and leave them alone.&lt;/p>
&lt;h2 id="the-four-i-would-change">The four I would change&lt;/h2>
&lt;p>These are my calls, each with NVIDIA&amp;rsquo;s description under it.&lt;/p>
&lt;h3 id="1-monitor-technology-g-sync-if-your-monitor-has-it">1. Monitor Technology: G-SYNC, if your monitor has it&lt;/h3>
&lt;p>NVIDIA&amp;rsquo;s Help describes G-SYNC as eliminating screen tearing while minimizing input lag and stutter, ULMB as a motion blur option you pick instead of G-SYNC, and Fixed Refresh Rate as no variability. The app&amp;rsquo;s text says G-SYNC and G-SYNC Compatible suit demanding games with highly variable frame rates, and ULMB suits games with consistently high frame rates. The app&amp;rsquo;s text carries it in two places: a Monitor Technology entry in the driver settings list, and G-SYNC options in the System tab&amp;rsquo;s display strings. The display strings offer G-SYNC for fullscreen only, or for fullscreen and windowed, and say windowed G-SYNC extends compatibility to applications rendered through the desktop compositor, and needs the application profiled by NVIDIA or set manually on the Graphics page. If you play borderless windowed games, that is the choice to look at.&lt;/p>
&lt;h3 id="2-max-frame-rate-per-game">2. Max Frame Rate, per game&lt;/h3>
&lt;p>NVIDIA&amp;rsquo;s Help says it sets the maximum frame rate the GPU will render, helps with battery life, and can reduce system latency in certain scenarios; the range in the Help is 20 to 1000 fps and the default is Off. The app&amp;rsquo;s text says people often use it to limit the frame rate slightly below a G-SYNC display&amp;rsquo;s refresh rate. I set it per game under Program Settings, not globally. The number to use, and why it interacts with V-Sync, is on my &lt;a href="https://techfuelhq.com/gaming/vsync-on-or-off-2026/">V-Sync on or off&lt;/a> page. There is also a Background Application Max Frame Rate, 20 to 200 in the Help, which NVIDIA says reduces power draw or fan noise while a game sits in the background.&lt;/p>
&lt;h3 id="3-low-latency-mode-per-game-only-where-there-is-no-reflex">3. Low Latency Mode, per game, only where there is no Reflex&lt;/h3>
&lt;p>NVIDIA&amp;rsquo;s Help lists Off (default), On and Ultra: Off prioritizes render throughput by letting games queue frames, On limits queued frames to one, and Ultra fully minimizes them. The app&amp;rsquo;s text adds that Ultra also minimizes V-Sync latency when V-Sync and G-SYNC are both on. NVIDIA&amp;rsquo;s own latency guide says to use Reflex when the game has it, Ultra when it does not, and that Reflex overrides Ultra if both are on. The 2019 launch post says the mode covers DirectX 9 and 11 games, and that in DirectX 12 and Vulkan games the game decides when to queue frames. All of that is on &lt;a href="https://techfuelhq.com/gaming/nvidia-reflex-on-or-off-2026/">the Reflex page&lt;/a>; I leave the global value alone and set it per game.&lt;/p>
&lt;h3 id="4-vertical-sync-by-monitor-type">4. Vertical sync, by monitor type&lt;/h3>
&lt;p>NVIDIA&amp;rsquo;s app text describes Off as very low latency with tearing, On as tear-free at the cost of possible latency and stutter below the refresh rate, and Fast as close to Off in latency without tearing. Which one is right depends on whether you have a variable refresh rate monitor, so I left the decision table to the &lt;a href="https://techfuelhq.com/gaming/vsync-on-or-off-2026/">V-Sync page&lt;/a> and the &lt;a href="https://techfuelhq.com/articles/fix-screen-tearing-2026/">screen tearing guide&lt;/a>.&lt;/p>
&lt;h2 id="settings-with-a-documented-reason-to-leave-them">Settings with a documented reason to leave them&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Setting&lt;/th>
&lt;th scope="col">What NVIDIA says it does&lt;/th>
&lt;th scope="col">My call&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Setting">Power Management Mode&lt;/td>
&lt;td data-label="What NVIDIA says it does">Adaptive lets the driver pick a performance state from GPU usage and saves power; Prefer maximum performance holds the maximum state regardless of usage, which can raise power consumption. NVIDIA&amp;rsquo;s Reflex article says it works like Reflex&amp;rsquo;s Low Latency Boost, which it aims at CPU-bound cases for anyone who wants every last bit of latency regardless of power.&lt;/td>
&lt;td data-label="My call">Leave. Set it per game only if you accept the power.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Shader Cache Size&lt;/td>
&lt;td data-label="What NVIDIA says it does">Caps the disk space the driver uses for compiled shaders. The app also has Automatic Shader Compilation (Beta), which NVIDIA says rebuilds DirectX 12 shaders while the system is idle, with Low, Medium and High utilization.&lt;/td>
&lt;td data-label="My call">Leave on Driver Default; the &lt;a href="https://techfuelhq.com/gaming/shader-cache-size-nvidia-2026/">shader cache guide&lt;/a> has the reasoning.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Texture filtering - Quality&lt;/td>
&lt;td data-label="What NVIDIA says it does">Quality is the default for GeForce cards; High quality turns off all texture filtering optimization.&lt;/td>
&lt;td data-label="My call">Leave.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Texture filtering - trilinear, anisotropic sample, negative LOD bias&lt;/td>
&lt;td data-label="What NVIDIA says it does">The app&amp;rsquo;s text says On gives higher performance with minimal loss in image quality for the first two, and Off is for best quality or if you see shimmering. Clamp is for better image quality with anisotropic filtering.&lt;/td>
&lt;td data-label="My call">Leave.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Anisotropic filtering, Antialiasing mode and setting&lt;/td>
&lt;td data-label="What NVIDIA says it does">NVIDIA says Application-controlled is the preferred value for programs with built-in controls.&lt;/td>
&lt;td data-label="My call">Leave on Application-controlled.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Antialiasing - transparency, gamma correction, MFAA&lt;/td>
&lt;td data-label="What NVIDIA says it does">The Help says Multisampling transparency provides superior performance and Supersampling superior quality, and that gamma correction is for OpenGL programs.&lt;/td>
&lt;td data-label="My call">Leave.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Antialiasing - FXAA&lt;/td>
&lt;td data-label="What NVIDIA says it does">A post-process filter that NVIDIA says can be used on any program; enabling it globally may affect all programs rendered on the GPU, including video players and the Windows desktop.&lt;/td>
&lt;td data-label="My call">Leave Off globally.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Threaded optimization&lt;/td>
&lt;td data-label="What NVIDIA says it does">Lets applications use multiple CPUs. The app&amp;rsquo;s text says most newer applications should benefit from Auto or On, and most older ones should have it off.&lt;/td>
&lt;td data-label="My call">Leave on Auto.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">CUDA Memory Fallback&lt;/td>
&lt;td data-label="What NVIDIA says it does">Lets GPU allocations spill into system memory. The app&amp;rsquo;s text says Prefer no fallback returns out-of-memory errors instead and may cause crashes or TDRs.&lt;/td>
&lt;td data-label="My call">Leave on Driver Default.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Resizable BAR&lt;/td>
&lt;td data-label="What NVIDIA says it does">Auto is NVIDIA&amp;rsquo;s recommended behavior.&lt;/td>
&lt;td data-label="My call">Leave on Auto; see &lt;a href="https://techfuelhq.com/gaming/resizable-bar-on-or-off-2026/">Resizable BAR on or off&lt;/a>.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Image Scaling&lt;/td>
&lt;td data-label="What NVIDIA says it does">Off by default. NVIDIA describes On as GPU upscaling and sharpening that increases frame rates, with a Sharpen slider of 0 to 100%.&lt;/td>
&lt;td data-label="My call">Leave Off; decide per game.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Triple buffering, OpenGL entries, Vulkan/OpenGL present method, OpenGL GDI Compatibility&lt;/td>
&lt;td data-label="What NVIDIA says it does">Triple buffering applies to OpenGL applications only, per NVIDIA. For the present method and GDI entries, the app&amp;rsquo;s text says to set Auto for the driver-recommended behavior.&lt;/td>
&lt;td data-label="My call">Leave.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Dynamic Boost, BatteryBoost, WhisperMode, Panel self-refresh&lt;/td>
&lt;td data-label="What NVIDIA says it does">Power features. The Help lists Dynamic Boost as On by default; NVIDIA&amp;rsquo;s text for the others is about battery life and fan noise on laptops.&lt;/td>
&lt;td data-label="My call">Leave.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Setting">Stereo, SLI and Multi View, VR, PhysX&lt;/td>
&lt;td data-label="What NVIDIA says it does">NVIDIA&amp;rsquo;s app text labels PhysX processor Auto (Recommended). The others are for stereo displays, multi-GPU or headsets.&lt;/td>
&lt;td data-label="My call">Leave.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The Help-only SILK Smoothness entry says Low is the default and that High or Ultra can add lag, so NVIDIA says it may not suit first-person shooters or competitive play. I found no string for it in the app here, so I cannot tell you where it appears.&lt;/p>
&lt;h2 id="new-app-only-settings">New app-only settings&lt;/h2>
&lt;p>The app also carries settings the Help reference does not: DLSS Override for Super Resolution, Frame Generation and model presets, Smooth Motion, RTX HDR and RTX Dynamic Vibrance. NVIDIA&amp;rsquo;s text says Smooth Motion infers an extra frame between two rendered frames for games that do not support DLSS and should not be combined with the Frame Generation override. For the Dynamic mode, NVIDIA&amp;rsquo;s March 2026 notes say it is not compatible with frame rate limiters or V-Sync, so do not stack a cap on it. The &lt;a href="https://techfuelhq.com/articles/frame-generation-explained-2026/">frame generation guide&lt;/a> explains the modes.&lt;/p>
&lt;h2 id="color-settings">Color settings&lt;/h2>
&lt;p>In the app these are on the System tab&amp;rsquo;s display page. Its text describes Output color format as the color space that looks best on your TV, and gives wrong saturation or blacks that are not pure black as the reason to change it. It says YCbCr 4:2:2 or 4:2:0, where the display supports them, can reach higher refresh rates than RGB or YCbCr 4:4:4. For dynamic range it says Limited (16 to 235) is commonly used by televisions and Full (0 to 255) may allow more detail in dark and white areas of some content. It does not say which a PC monitor needs, so I would leave it on the default and change it only to fix a symptom NVIDIA lists. If you are chasing a refresh rate your cable cannot carry, check the &lt;a href="https://techfuelhq.com/tools/displayport-hdmi-bandwidth-calculator/">DisplayPort and HDMI bandwidth calculator&lt;/a> before dropping the color format.&lt;/p>
&lt;h2 id="altz">Alt+Z&lt;/h2>
&lt;p>Alt+Z belongs to the app, not the panel. NVIDIA&amp;rsquo;s retirement notice lists it for recording gameplay and capturing screenshots, with Alt+R for in-game stats. If it does nothing, NVIDIA&amp;rsquo;s support article (last updated December 2024) gives three steps: check the overlay is enabled in the app&amp;rsquo;s settings, install the Windows Media Feature Pack if you have a Windows N edition and then reboot and reinstall the app, and update the driver, for which NVIDIA recommends 565.90 or higher. Whether your build matches that is covered in &lt;a href="https://techfuelhq.com/articles/game-ready-vs-studio-driver-2026/">Game Ready vs Studio drivers&lt;/a>.&lt;/p></description></item><item><title>Motion Blur On or Off? What It Does and What Fixes the Real Blur (2026)</title><link>https://techfuelhq.com/gaming/motion-blur-on-or-off-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gaming/motion-blur-on-or-off-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Motion blur on or off&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>My pick: off.&lt;/strong> That is judgment, not a measurement. Epic's and Unity's documentation define the effect and give you strength controls; neither says which way to set it.&lt;/li>
&lt;li>&lt;strong>Keep it on if you like the look,&lt;/strong> and keep it low. It is a style setting. It is not what fixes blur on your screen.&lt;/li>
&lt;li>&lt;strong>There is a second blur, and it is on the display,&lt;/strong> not in the game: Blur Busters calls it sample-and-hold blur, and it exists even on a 0 ms pixel-response panel.&lt;/li>
&lt;li>&lt;strong>To reduce that blur:&lt;/strong> raise frame rate and refresh rate together, or use the monitor's strobing or black frame insertion mode if it has one and you can tolerate the trade-offs.&lt;/li>
&lt;li>&lt;strong>Where it lives:&lt;/strong> the game's own graphics menu. I found no Windows or NVIDIA driver setting for it in the documentation I read.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>There are two different blurs in this question, and the two are easy to mix up. One is an effect a game&amp;rsquo;s renderer draws into the picture. The other happens between your screen and your eyes whether the game draws any blur or not. This page covers both, with the definitions taken from the engine documentation and from Blur Busters, the site that has spent years on the display side. I have a &lt;a href="https://techfuelhq.com/articles/aorus-fo48u-review/">4K OLED&lt;/a> on an RTX 5080 on this bench; I did not run any game for this page, so there is no &amp;ldquo;I tested it&amp;rdquo; anywhere below.&lt;/p>
&lt;h2 id="what-the-in-game-setting-is">What the in-game setting is&lt;/h2>
&lt;p>Unity&amp;rsquo;s documentation describes its Motion Blur effect as simulating the blur that occurs in an image when a real-world camera films objects moving faster than the camera&amp;rsquo;s exposure time, usually from rapidly moving objects or a long exposure. Epic puts it in photography terms too: motion blur is the result of an object moving before the image has been captured, and how fast the object moves determines how much blur there is.&lt;/p>
&lt;p>Two flavors show up in the documentation:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Camera motion blur.&lt;/strong> Unity&amp;rsquo;s Motion Blur override has a Mode with two options. Camera Only uses only the motion of the camera to blur the picture, does not use motion vectors, and Unity says it performs better than the other mode. Camera and Objects adds the motion of the objects in the scene, and per Unity the object motion vectors overwrite the camera motion vectors.&lt;/li>
&lt;li>&lt;strong>Per-object motion blur.&lt;/strong> Epic says Unreal&amp;rsquo;s motion blur uses a full-screen velocity map, and objects are blurred based on their contribution to that map. One of its controls, Per Object Size, sets the minimum projected screen radius an object needs to be drawn in the velocity pass, as a percentage of screen width; smaller radii cause more draw calls.&lt;/li>
&lt;/ul>
&lt;p>The strength controls are what you see in a game&amp;rsquo;s slider, if it has one. Unity&amp;rsquo;s are Intensity (0 to 1; higher values give a stronger blur and, depending on Clamp, can cost performance), Quality (lower presets perform better but risk visual artifacts) and Clamp, the maximum length the velocity from camera rotation can have, with a default of 0.05 and a range of 0 to 0.2. Epic&amp;rsquo;s are Amount (0 is off) and Max, the maximum distortion as a percentage of screen width (0 is off).&lt;/p>
&lt;p>One Epic detail explains why the same slider can feel different at different frame rates. Its Target FPS setting makes the motion blur independent of the actual frame rate: relative to the specified target, shorter frames mean shorter shutter times and less blur, and lower FPS means more blur. A value of 0 makes it depend on the measured frame rate. Whether a particular game sets that value, I can&amp;rsquo;t tell you from documentation.&lt;/p>
&lt;h2 id="why-people-turn-it-off-and-why-people-turn-it-on">Why people turn it off, and why people turn it on&lt;/h2>
&lt;p>I&amp;rsquo;ll be plain about the limits here. Nothing I read from Epic or Unity says motion blur is meant to hide low frame rate, to help or hurt aiming, or to cause discomfort. I&amp;rsquo;m not going to repeat claims like those as fact.&lt;/p>
&lt;p>What the sources do support is the display side, and that is where the frame-rate part of this question lives.&lt;/p>
&lt;p>&lt;strong>Sample-and-hold.&lt;/strong> Blur Busters says your eyes are always moving when you track a moving object on a screen, and that sample-and-hold means each frame is held statically until the next refresh. Your eyes are in a different position at the start of a refresh than at the end, so the frame is smeared across your retinas. It calls this blur from persistence, separate from pixel transition speed (GtG): even a 0 ms GtG panel can show a lot of motion blur this way, and it says plainly that most LCDs and OLEDs are sample-and-hold. A 60 Hz refresh, it notes, is displayed for a whole 1/60th of a second.&lt;/p>
&lt;p>Blur Busters&amp;rsquo; one rule for fixing it: the only way to reduce sample-and-hold blur is to shorten the time a frame is displayed, with extra refreshes (higher Hz) or black periods between refreshes (flicker). A guest article by William Sokol Erhard that Blur Busters published in May 2025 puts a number on the first route: doubling the frame rate will halve display motion blur and quadrupling it eliminates 75 percent, assuming enough refresh rate and instant pixel response (GtG of 0).&lt;/p>
&lt;p>That is the &amp;ldquo;low frame rate&amp;rdquo; connection I can actually source: that 2025 piece ties frame rate directly to the amount of display blur. Whether a game&amp;rsquo;s drawn blur makes a 60 fps game look smoother to you is something I haven&amp;rsquo;t found a source for, and I won&amp;rsquo;t pretend otherwise. Try it in the game and judge it with your own eyes. If it looks better to you, that is a fine reason to leave it on.&lt;/p>
&lt;p>&lt;strong>OLED does not escape it.&lt;/strong> Blur Busters&amp;rsquo; OLED page makes the point that OLED&amp;rsquo;s near-instant pixel response does not shorten persistence. Their examples are older handheld and phone OLEDs, so I read it as a statement about the mechanism, and the same page says some OLEDs use strobing to lower persistence and not all do.&lt;/p>
&lt;h2 id="display-side-blur-reduction">Display-side blur reduction&lt;/h2>
&lt;p>This is the part of the question the in-game slider can&amp;rsquo;t touch. Blur Busters&amp;rsquo; motion blur reduction FAQ describes backlight strobing, sold under names like ULMB, LightBoost, DyAc and ELMB, as flashing a backlight synchronized to the refresh rate. The backlight is off while the LCD pixels are changing and flashes only on fully refreshed frames; the flash can be shorter than the pixel transition. NVIDIA&amp;rsquo;s own words for ULMB in its driver help are &amp;ldquo;Ultra Low Motion Blur&amp;rdquo; for people who prefer to improve motion blur instead of using G-SYNC, and NVIDIA app&amp;rsquo;s text describes it as backlight pulsing at a fixed refresh rate to minimize blur, best for games with consistently high FPS.&lt;/p>
&lt;p>The trade-offs, all from Blur Busters:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Quality varies by monitor.&lt;/strong> It says blur reduction sometimes looks very good, with CRT-style motion clarity, and sometimes very bad, with double images (strobe crosstalk), poor colors, dimness, microstutter or flicker.&lt;/li>
&lt;li>&lt;strong>Frame rate must match.&lt;/strong> Frame rates lower than the strobe rate produce multiple-image artifacts: 30 fps at 60 Hz is a double image, 60 fps at 120 Hz is a double image and 30 fps at 120 Hz is four. Its advice is to match frame rate, refresh rate and strobe rate.&lt;/li>
&lt;li>&lt;strong>Brightness versus clarity.&lt;/strong> Some backlights have an adjustable pulse width, and the shorter the flash, the clearer the motion and the dimmer the picture.&lt;/li>
&lt;li>&lt;strong>Input lag.&lt;/strong> It says blur reduction modes by several vendors may add input lag.&lt;/li>
&lt;li>&lt;strong>Flicker.&lt;/strong> Erhard&amp;rsquo;s 2025 guest article puts the flicker fusion threshold for most people at roughly 90 to 120 Hz, and says strobing below it can cause significant discomfort and fatigue. NVIDIA&amp;rsquo;s app text for G-SYNC Pulsar, its variable-frequency strobing feature, says it runs at 90 to 360 Hz by default, that the minimum can be set between 75 and 120 Hz based on personal flicker tolerance, and that some users might perceive flickering below 90.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Black frame insertion (BFI).&lt;/strong> Same idea at the signal level: individual refresh cycles are blacked out. Erhard&amp;rsquo;s article lists BFI, ULMB, ELMB, DyAc, OLED Motion and G-Sync Pulsar as names for the family, and says modern TVs like LG OLEDs and OLED gaming monitors often offer BFI with limited controls, a moderate amount of added latency, and often a single mode at half the maximum refresh rate with a 50 percent duty cycle. Duty cycle there means the fraction of each refresh the image is visible; the lower it is, the lower the brightness and the lower the motion blur. Which of your monitor&amp;rsquo;s modes are which is a question for your monitor&amp;rsquo;s manual.&lt;/p>
&lt;p>On my own screen, the one thing I can tell you comes from my &lt;a href="https://techfuelhq.com/articles/aorus-fo48u-review/">AORUS FO48U review&lt;/a>: it has a feature called Aim Stabilizer that is supposed to reduce motion blur, and I wrote there that enabling FreeSync disables most of the monitor&amp;rsquo;s gamer features. Blur Busters&amp;rsquo; FAQ lists Aim Stabilizer, by AORUS/Gigabyte, among the monitor brand names for blur reduction. I have no measurement of it. That interaction between adaptive sync and strobing is also in the sources: Erhard&amp;rsquo;s article says some strobing implementations offer configurable refresh rates but not with variable refresh rates (NVIDIA markets G-SYNC Pulsar as variable-frequency strobing, so check what your monitor supports).&lt;/p>
&lt;h2 id="what-id-do">What I&amp;rsquo;d do&lt;/h2>
&lt;ol>
&lt;li>&lt;strong>Pick the in-game setting by taste, starting at off.&lt;/strong> It&amp;rsquo;s drawn into the image by the game; the documentation gives you strength controls and nothing more.&lt;/li>
&lt;li>&lt;strong>If your complaint is that moving objects smear on your screen,&lt;/strong> that&amp;rsquo;s the display&amp;rsquo;s persistence. Raise frame rate and refresh rate together; the &lt;a href="https://techfuelhq.com/gaming/vsync-on-or-off-2026/">VSync&lt;/a> and &lt;a href="https://techfuelhq.com/articles/frame-generation-explained-2026/">frame generation&lt;/a> pages cover the sync and frame-rate settings. If frames are inconsistent rather than low, the &lt;a href="https://techfuelhq.com/articles/pc-stuttering-in-games-2026/">stuttering guide&lt;/a> is the place to start. The &lt;a href="https://techfuelhq.com/tools/fps-calculator/">FPS calculator&lt;/a> helps with the budget.&lt;/li>
&lt;li>&lt;strong>Then look at your monitor&amp;rsquo;s strobing or BFI mode,&lt;/strong> and treat it as a trade: brightness, flicker, crosstalk and latency in return for clarity.&lt;/li>
&lt;li>&lt;strong>Softness that isn&amp;rsquo;t motion&lt;/strong> (a static image that looks smeared) is an anti-aliasing question, covered in the &lt;a href="https://techfuelhq.com/gaming/anti-aliasing-on-or-off-2026/">anti-aliasing guide&lt;/a>.&lt;/li>
&lt;/ol></description></item><item><title>HDR On or Off in Windows? HDR, Auto HDR and the Calibration App (2026)</title><link>https://techfuelhq.com/gaming/hdr-on-or-off-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gaming/hdr-on-or-off-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · HDR on or off&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Windows HDR: ON&lt;/strong> if your display supports HDR10 and you play or watch HDR content. If the desktop looks too bright or too dark, use the SDR content brightness slider.&lt;/li>
&lt;li>&lt;strong>Auto HDR: your call, per game.&lt;/strong> It only touches older SDR-only games. Turn it off for any game where the result looks wrong.&lt;/li>
&lt;li>&lt;strong>Paths:&lt;/strong> Settings > System > Display > pick your display > HDR. Auto HDR sits inside the expanded HDR section.&lt;/li>
&lt;li>&lt;strong>Then run the Windows HDR Calibration app&lt;/strong>, a Microsoft Store download that Microsoft says to consider even on certified displays.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>I&amp;rsquo;m answering this for a display that already supports HDR. My bench monitor is an AORUS FO48U on an RTX 5080, and Windows reports HDR on for it right now, as the read-only check below shows. If you&amp;rsquo;re not sure your display qualifies, start with the next section.&lt;/p>
&lt;h2 id="does-your-display-support-hdr">Does your display support HDR?&lt;/h2>
&lt;p>Microsoft&amp;rsquo;s requirement for an external display is that it supports HDR10 and connects over DisplayPort 1.4, HDMI 2.0 or higher, USB-C or Thunderbolt. It recommends displays certified for HDR (AMD FreeSync Premium Pro, Dolby Vision, NVIDIA G-SYNC Ultimate or VESA DisplayHDR) and, within DisplayHDR, the DisplayHDR 500 tier or higher. If Settings &amp;gt; System &amp;gt; Display &amp;gt; Advanced display shows &amp;ldquo;Not found&amp;rdquo; next to HDR certification, Microsoft says that can mean the display has no certification or that its maker hasn&amp;rsquo;t published one.&lt;/p>
&lt;p>The quick check is on the HDR settings page. Under Display capabilities, Windows shows whether the display supports HDR video streaming, games, apps and more. For the long version, Microsoft&amp;rsquo;s steps are to run dxdiag, save the information to a text file and read the Advanced Color line: AdvancedColorSupported means the driver and display support HDR10, and AdvancedColorEnabled means HDR is on. My report read both, with Active Color Mode set to HDR.&lt;/p>
&lt;h2 id="windows-hdr-on-or-off">Windows HDR: on or off&lt;/h2>
&lt;p>&lt;strong>On, if you use HDR content.&lt;/strong> Microsoft&amp;rsquo;s description of HDR is brighter highlights, deeper shadows and a wider range of colors than SDR, with details visible in bright and dark areas at the same time. Games, movies and creative work are the examples it gives.&lt;/p>
&lt;p>&lt;strong>The path (Windows 11):&lt;/strong> Settings &amp;gt; System &amp;gt; Display. If you have more than one display, choose the HDR-capable one at the top, then turn on &lt;strong>HDR&lt;/strong>. Windows 10 builds label it differently; Microsoft&amp;rsquo;s page for them says to enable the Use HDR toggle under Windows HD Color.&lt;/p>
&lt;p>&lt;strong>Off, or at least a second look, in these cases:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>&lt;strong>A laptop on battery.&lt;/strong> Microsoft says playing HDR on battery can reduce battery life, so the PC maker may have turned HDR off by default on battery, and HDR turns back on when you plug in. There is a checkbox, &amp;ldquo;Turn off HDR when my PC is running on battery&amp;rdquo;, in the expanded HDR section if you want to change it.&lt;/li>
&lt;li>&lt;strong>Duplicate mode.&lt;/strong> When you connect an external display to a laptop, Windows duplicates the desktop by default, and Microsoft says HDR isn&amp;rsquo;t supported in that configuration. Choose Extend these displays.&lt;/li>
&lt;li>&lt;strong>A display that handles HDR badly.&lt;/strong> Microsoft says some HDR-capable displays don&amp;rsquo;t reproduce sRGB colors correctly when HDR is on, and tells shoppers to look for certified displays and reviews that discuss color accuracy. If yours is one of those, I&amp;rsquo;d decide by looking at it, not by the spec sheet.&lt;/li>
&lt;li>&lt;strong>Dolby Vision monitors.&lt;/strong> Windows chooses Dolby Vision automatically when a monitor offers it. Microsoft notes that some monitors limit peak brightness in that mode, and that clearing &lt;strong>Use Dolby Vision mode&lt;/strong> under Settings &amp;gt; System &amp;gt; Display &amp;gt; HDR enables a non-certified HDR10 mode that may be brighter. Microsoft&amp;rsquo;s longer note says some monitors limit maximum brightness to around 450 nits in both modes, and that a monitor&amp;rsquo;s own menu may have an option to unlock higher levels.&lt;/li>
&lt;/ul>
&lt;p>If your connection is HDMI and the display also supports HDR over DisplayPort, Microsoft says to use DisplayPort when color looks wrong. The &lt;a href="https://techfuelhq.com/tools/displayport-hdmi-bandwidth-calculator/">DisplayPort and HDMI bandwidth calculator&lt;/a> shows what a given resolution and refresh rate needs. If you&amp;rsquo;re running a TV as a monitor, my &lt;a href="https://techfuelhq.com/articles/oled-tv-as-pc-monitor-2026/">OLED TV as PC monitor&lt;/a> page covers that setup.&lt;/p>
&lt;h2 id="sdr-content-brightness-what-microsoft-says">SDR content brightness: what Microsoft says&lt;/h2>
&lt;p>With HDR on, a display interprets SDR and HDR signals differently, and Microsoft says the results vary by make and model. Its guidance is specific.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>SDR looks too bright or too dark.&lt;/strong> Microsoft says to open Settings &amp;gt; System &amp;gt; Display, pick the HDR display, open HDR, and drag the &lt;strong>SDR content brightness&lt;/strong> slider. On an external HDR display this changes SDR brightness relative to HDR content.&lt;/li>
&lt;li>&lt;strong>Stay near the default.&lt;/strong> Microsoft says the default setting, or one close to it, should work well for most times. Setting it higher can improve contrast between the brightest and darkest parts but reduces detail in dark areas.&lt;/li>
&lt;li>&lt;strong>Some desktop apps look darker than others.&lt;/strong> Microsoft says this can happen with apps that don&amp;rsquo;t work with the slider. For an external HDR display, its fix is to lower the slider so all SDR content sits at a similar level, then raise the brightness with the display&amp;rsquo;s own menu. If a change doesn&amp;rsquo;t take effect in an app, restart the app.&lt;/li>
&lt;li>&lt;strong>Laptops are different.&lt;/strong> On a built-in HDR display, a separate brightness setting controls SDR content and the slider is labeled HDR content brightness, which sets HDR relative to SDR.&lt;/li>
&lt;/ul>
&lt;p>Microsoft&amp;rsquo;s fix for a too-bright or too-dark desktop is that slider. It doesn&amp;rsquo;t tell you to switch HDR off for that.&lt;/p>
&lt;h2 id="auto-hdr-on-or-off">Auto HDR: on or off&lt;/h2>
&lt;p>Auto HDR is a separate switch from Windows HDR. Microsoft&amp;rsquo;s description is that it automatically raises the color range and brightness of older SDR-only games to HDR on an HDR-capable display. Microsoft&amp;rsquo;s 2023 Graphics page post says it covers existing DirectX 10 through DirectX 12 games; the 2021 preview post said DirectX 11 and DirectX 12. Microsoft&amp;rsquo;s 2021 preview post also says native HDR is the best-quality experience for games that have it, with Auto HDR a vastly improved experience over regular SDR for games that don&amp;rsquo;t.&lt;/p>
&lt;p>&lt;strong>System-wide path:&lt;/strong> Settings &amp;gt; System &amp;gt; Display, pick your HDR display, turn on HDR, expand the HDR toggle section, and turn on &lt;strong>Auto HDR&lt;/strong>.&lt;/p>
&lt;p>&lt;strong>Per game:&lt;/strong> Settings &amp;gt; System &amp;gt; Display &amp;gt; Graphics. Microsoft&amp;rsquo;s 2023 redesign gives each app in the custom settings list its own Auto HDR toggle, and a per-app setting overrides the system-wide one. Microsoft&amp;rsquo;s support page words the same thing as a &lt;strong>Don&amp;rsquo;t use Auto HDR&lt;/strong> checkbox under the app&amp;rsquo;s Options. The 2023 post adds that these settings only apply to eligible games.&lt;/p>
&lt;p>&lt;strong>In the game:&lt;/strong> Microsoft&amp;rsquo;s April 2022 post describes Xbox Game Bar (Win+G) &amp;gt; Settings &amp;gt; Gaming features, with a &lt;strong>Use Auto HDR with supported games&lt;/strong> checkbox and an &lt;strong>Adjust HDR Intensity&lt;/strong> button. Relaunch the game after a change. The intensity slider applies to Auto HDR games, not games with native HDR, and Microsoft says its minimum is the equivalent of Auto HDR off. That post is from 2022, and I found no newer Microsoft page that repeats these menu names, so I&amp;rsquo;m quoting them as Microsoft wrote them then; Game Bar&amp;rsquo;s labels may have changed since.&lt;/p>
&lt;p>&lt;strong>Default state.&lt;/strong> I found no current Microsoft page that states whether Auto HDR is on by default. Microsoft&amp;rsquo;s 2021 Insider preview post said a PC whose monitor was already configured for HDR would automatically get Auto HDR, and that was a preview-era statement.&lt;/p>
&lt;p>&lt;strong>Who it&amp;rsquo;s for.&lt;/strong> If you play older SDR-only DirectX games on an HDR display you already run in HDR, try it on and judge each game. Microsoft&amp;rsquo;s 2022 post says the intensity slider is for games with extremely bright or dim colors. If you don&amp;rsquo;t like the result in a game, turn Auto HDR off for that game. You don&amp;rsquo;t need to turn Windows HDR off to get rid of Auto HDR, because there is a system-wide switch and a per-game one. The recommendation is my judgment, not a Microsoft statement.&lt;/p>
&lt;p>&lt;strong>The windowed-game link.&lt;/strong> Microsoft&amp;rsquo;s support page says turning on Auto HDR automatically turns on Optimizations for windowed games, and that you have to turn Auto HDR off before you can turn that one off. Microsoft says that setting changes presentation in DirectX 10 and 11 windowed games, lowering frame latency, and its 2022 post says it can cause tearing at high frame rates with v-sync off. The &lt;a href="https://techfuelhq.com/gaming/variable-refresh-rate-on-or-off-2026/">variable refresh rate page&lt;/a> and the &lt;a href="https://techfuelhq.com/gaming/vsync-on-or-off-2026/">V-Sync page&lt;/a> cover that side.&lt;/p>
&lt;p>&lt;strong>FPS.&lt;/strong> The only Microsoft statement on cost I found is from the 2021 Auto HDR preview: it takes some GPU compute power, but Microsoft didn&amp;rsquo;t expect a significant effect on your gaming experience. That is a preview-era statement and I haven&amp;rsquo;t measured it on the bench.&lt;/p>
&lt;p>&lt;strong>NVIDIA&amp;rsquo;s version.&lt;/strong> NVIDIA&amp;rsquo;s RTX HDR is a different feature. NVIDIA&amp;rsquo;s October 2024 post describes it as a filter opened in games with Alt+Z &amp;gt; Game Filter that brings HDR to SDR games on DX12, DX11, DX9 and Vulkan, and it points to NVIDIA&amp;rsquo;s support knowledge base for requirements. I haven&amp;rsquo;t tested it, so this page doesn&amp;rsquo;t compare it with Auto HDR.&lt;/p>
&lt;h2 id="the-windows-hdr-calibration-app">The Windows HDR Calibration app&lt;/h2>
&lt;p>Microsoft says HDR-certified displays typically work well out of the box without calibration, and that you should still consider using the app. It is a download from the Microsoft Store. It has three test patterns recommended by the HDR Gaming Interest Group (HGIG), which find the darkest visible details, the brightest visible details and the display&amp;rsquo;s maximum brightness. It also has a color saturation slider that applies to both HDR and SDR content when HDR is on.&lt;/p>
&lt;p>&lt;strong>Requirements, per Microsoft:&lt;/strong> Windows 11, an HDR-capable display with HDR turned on, the app running full screen, a WDDM 2.7 or later driver, and a newer GPU (AMD RX 400 series or later or Ryzen with Radeon Graphics, Intel 11th Gen integrated or DG1 and later, or NVIDIA GTX 10 series and later) for color saturation to work.&lt;/p>
&lt;p>&lt;strong>Steps:&lt;/strong> install it, then Start &amp;gt; All apps &amp;gt; Windows HDR Calibration. With several displays, put its window on the HDR one. Drag each of the three sliders until the test pattern is no longer visible. Saturation defaults to less saturated on the left; Microsoft warns that pushing it too far makes HDR look unnatural and over-saturated.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s notes also say to use the app in the lighting you normally use, to turn off display post-processing effects if the app doesn&amp;rsquo;t work as expected, and to re-run it whenever you add or replace a display. The app saves a color profile. To delete one, open Color Management in Control Panel, go to the All Profiles tab, select the profile and choose Remove.&lt;/p>
&lt;p>On my machine, the app is installed (version 1.1.2.0), and C:\Windows\System32\spool\drivers\color holds fifteen files named &amp;ldquo;HDR Calibrated Profile&amp;rdquo; with dates from June and July 2026.&lt;/p>
&lt;h2 id="what-i-read-on-the-bench">What I read on the bench&lt;/h2>
&lt;p>All of this was read-only. dxdiag&amp;rsquo;s Display section listed 3840 x 2160 at 120 Hz on the RTX 5080, HDR Supported, and Advanced Color supported and enabled in HDR mode. The AORUS FO48U is the monitor; my &lt;a href="https://techfuelhq.com/articles/aorus-fo48u-review/">FO48U review&lt;/a> has the OSD screenshots and the picture-mode settings. I didn&amp;rsquo;t open Settings, so the page doesn&amp;rsquo;t say how my Auto HDR toggle is set, and I didn&amp;rsquo;t compare HDR against SDR or measure FPS.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/help/4040547" rel="noopener">Microsoft Support, What is HDR (high dynamic range) in Windows and how does it work?&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/hdr-settings-in-windows-2d767185-38ec-7fdc-6f97-bbc6c5ef24e6" rel="noopener">Microsoft Support, HDR settings in Windows&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/use-auto-hdr-for-better-gaming-in-windows-0cce8402-3de5-4512-a742-e027ca7aa79c" rel="noopener">Microsoft Support, Use Auto HDR for better gaming in Windows&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/calibrate-your-hdr-display-using-the-windows-hdr-calibration-app-f30f4809-3369-43e4-9b02-9eabebd23f19" rel="noopener">Microsoft Support, Calibrate your HDR display using the Windows HDR Calibration app&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/optimizations-for-windowed-games-in-windows-11-3f006843-2c7e-4ed0-9a5e-f9389e535952" rel="noopener">Microsoft Support, Optimizations for windowed games in Windows 11&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/auto-hdr-preview-for-pc-available-today/" rel="noopener">Microsoft DirectX Developer Blog, Auto HDR Preview for PC Available Today (2021)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/exciting-additions-to-your-auto-hdr-experience-on-pc/" rel="noopener">Microsoft DirectX Developer Blog, Exciting additions to your Auto HDR experience on PC (2022)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/navigating-the-redesigned-graphics-settings-page/" rel="noopener">Microsoft DirectX Developer Blog, Navigating the Redesigned Graphics Settings page (2023)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.nvidia.com/en-us/geforce/news/nvidia-app-beta-update-g-sync-controls-rtx-hdr-multi-monitor/" rel="noopener">NVIDIA, NVIDIA App Beta Adds G-SYNC Controls, RTX HDR Multi-Monitor Support &amp;amp; More (October 1, 2024)&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>Disable Fullscreen Optimizations: When It Helps, How to Do It (2026)</title><link>https://techfuelhq.com/gaming/disable-fullscreen-optimizations-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gaming/disable-fullscreen-optimizations-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;p>Leave it on unless one game gives you a problem, then turn it off for that game only. Microsoft says its data shows almost all users get the same performance with Fullscreen Optimizations as with exclusive fullscreen, and the checkbox is Microsoft&amp;rsquo;s own troubleshooting step for &amp;ldquo;performance regression or input lag.&amp;rdquo;&lt;/p>
&lt;p>To set it, right-click the game&amp;rsquo;s .exe file, choose Properties, open the Compatibility tab, check Disable fullscreen optimizations, and select Apply.&lt;/p>
&lt;p>If you came looking for the Windows 11 switch under Settings &amp;gt; System &amp;gt; Display &amp;gt; Graphics, that is a different setting with a nearly identical name. It is covered in &lt;a href="https://techfuelhq.com/gaming/optimizations-for-windowed-games-on-or-off-2026/">Optimizations for windowed games: on or off&lt;/a>, and the section below says how they differ.&lt;/p>
&lt;h2 id="what-the-checkbox-does">What the checkbox does&lt;/h2>
&lt;p>Microsoft&amp;rsquo;s DirectX team explained the feature in December 2019. Fullscreen Optimizations &amp;ldquo;takes full screen exclusive games and runs them instead in a highly optimized borderless windowed format that takes up the entire screen.&amp;rdquo; The game believes it is in Fullscreen Exclusive (FSE), while Windows runs it in a borderless window behind the scenes.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s reason is the Desktop Window Manager, the DWM. A borderless window normally hands control of the display to the DWM, which Microsoft says &amp;ldquo;has historically resulted in a slight performance overhead vs FSE.&amp;rdquo; So Microsoft changed the DWM to recognize a borderless full screen game with no other apps on the screen, and in that case it &amp;ldquo;gives control of the display and almost all the CPU/GPU power to the game.&amp;rdquo;&lt;/p>
&lt;p>When something like the Game Bar overlay appears, the DWM takes control back and, Microsoft says, &amp;ldquo;a slight performance overhead is incurred so that the overlay can be composited on top of the game in a safe and stable way.&amp;rdquo;&lt;/p>
&lt;p>What you get, per Microsoft: faster Alt-Tab, multiple-monitor setups and overlays. What it claims on performance is parity, from its own data: &amp;ldquo;almost all users who use Fullscreen Optimizations have equal performance to Full Screen Exclusive,&amp;rdquo; and telemetry that shows performance &amp;ldquo;on average, as good or better than FSE.&amp;rdquo; Microsoft&amp;rsquo;s troubleshooting steps use the checkbox to disable the feature for one game.&lt;/p>
&lt;h2 id="when-disabling-it-helps">When disabling it helps&lt;/h2>
&lt;p>These are the cases a vendor documents. I found no others from a vendor, and I found no named publisher&amp;rsquo;s on/off measurement.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Performance regression or input lag.&lt;/strong> Microsoft&amp;rsquo;s troubleshooting section names these and gives the checkbox as the step. It also asks players to report problems that disabling resolves, through the Feedback Hub.&lt;/li>
&lt;li>&lt;strong>Flicker or black screens when you Alt-Tab.&lt;/strong> In VALORANT&amp;rsquo;s Alt + Tab troubleshooting, Riot lists the checkbox among its steps, saying it &amp;ldquo;stops Windows from forcing its own fullscreen management on VALORANT, which can cause flickers or black screens when alt-tabbing.&amp;rdquo;&lt;/li>
&lt;li>&lt;strong>Lag in League of Legends.&lt;/strong> Riot&amp;rsquo;s support page calls the feature part of the Windows 10 Anniversary Update, says it is on by default, and says &amp;ldquo;Sometimes it makes things worse.&amp;rdquo; It also warns that for League&amp;rsquo;s own executable &amp;ldquo;you&amp;rsquo;ll have to do this after every patch release.&amp;rdquo;&lt;/li>
&lt;/ul>
&lt;p>What it costs: Microsoft lists faster Alt-Tab, multiple monitors and overlays as the benefits of the feature. Its post doesn&amp;rsquo;t say what you lose or what the game gets instead when you disable it for one executable.&lt;/p>
&lt;p>Change only this checkbox when you test. If the problem is stutter, &lt;a href="https://techfuelhq.com/articles/pc-stuttering-in-games-2026/">why a PC stutters in games&lt;/a> separates frame-pacing problems from low FPS. Other Windows switches that people try in the same sitting have their own pages: &lt;a href="https://techfuelhq.com/gaming/game-mode-on-or-off-2026/">Game Mode&lt;/a>, &lt;a href="https://techfuelhq.com/gaming/hardware-accelerated-gpu-scheduling-on-or-off-2026/">hardware-accelerated GPU scheduling&lt;/a>, and the sync question on the &lt;a href="https://techfuelhq.com/gaming/vsync-on-or-off-2026/">VSync page&lt;/a>. Test one at a time.&lt;/p>
&lt;h2 id="how-to-disable-fullscreen-optimizations">How to disable fullscreen optimizations&lt;/h2>
&lt;p>Microsoft&amp;rsquo;s steps, from the 2019 post:&lt;/p>
&lt;ol>
&lt;li>Right-click the executable file (.exe) and select Properties.&lt;/li>
&lt;li>Select the Compatibility tab.&lt;/li>
&lt;li>Under Settings, select Disable fullscreen optimizations.&lt;/li>
&lt;li>Click Apply.&lt;/li>
&lt;/ol>
&lt;p>Riot&amp;rsquo;s VALORANT page (dated May 24, 2026) gives the same four clicks and ends with OK, and says you can do it on the game&amp;rsquo;s shortcut as well. The setting belongs to the executable you pick. For League, Riot&amp;rsquo;s page says to pick League of Legends.exe in the game&amp;rsquo;s Game folder, and that the setting has to be redone after a patch. I did not test whether other games&amp;rsquo; patches reset it.&lt;/p>
&lt;p>Microsoft wrote its steps while Windows 10 was current, and I found no Microsoft page that repeats them for Windows 11. Riot&amp;rsquo;s VALORANT page, updated in May 2026, gives the same clicks, but it doesn&amp;rsquo;t name a Windows version, and I did not open a Properties dialog on the bench machine, so I can&amp;rsquo;t confirm the label on my own build.&lt;/p>
&lt;h3 id="how-to-tell-whether-it-is-on">How to tell whether it is on&lt;/h3>
&lt;p>Microsoft&amp;rsquo;s check is the Xbox Game Bar. Press Win+G in the game. Microsoft says that if the Game Bar pops up as an overlay, Fullscreen Optimizations is in use, and that in true exclusive fullscreen the display brightness may flicker instead. It says the same check works with other system UI such as the volume indicator.&lt;/p>
&lt;h2 id="how-it-differs-from-optimizations-for-windowed-games">How it differs from Optimizations for windowed games&lt;/h2>
&lt;p>The two settings sound alike and are not the same.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">Disable fullscreen optimizations&lt;/th>
&lt;th scope="col">Optimizations for windowed games&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">Where&lt;/td>
&lt;td data-label="Disable fullscreen optimizations">Right-click the .exe &amp;gt; Properties &amp;gt; Compatibility&lt;/td>
&lt;td data-label="Optimizations for windowed games">Settings &amp;gt; System &amp;gt; Display &amp;gt; Graphics&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Scope&lt;/td>
&lt;td data-label="Disable fullscreen optimizations">One executable&lt;/td>
&lt;td data-label="Optimizations for windowed games">System-wide, with a per-app override&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Applies to&lt;/td>
&lt;td data-label="Disable fullscreen optimizations">Games that request exclusive fullscreen&lt;/td>
&lt;td data-label="Optimizations for windowed games">DirectX 10 and 11 games in Windowed or Borderless Windowed mode&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Introduced&lt;/td>
&lt;td data-label="Disable fullscreen optimizations">Windows 10; Microsoft explained it in 2019&lt;/td>
&lt;td data-label="Optimizations for windowed games">Windows 11; Microsoft announced it in February 2022&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">What it does&lt;/td>
&lt;td data-label="Disable fullscreen optimizations">Runs an FSE game in a borderless window so Windows can keep overlays and fast Alt-Tab&lt;/td>
&lt;td data-label="Optimizations for windowed games">Moves a windowed game from blt to flip-model presentation, which Microsoft says lowers latency&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Microsoft draws the line itself. Its 2022 announcement says the windowed setting applies to Windowed and Borderless Windowed games &amp;ldquo;because when you&amp;rsquo;re running in Fullscreen, a similar optimization already exists.&amp;rdquo; Microsoft&amp;rsquo;s post links that phrase to its 2019 fullscreen-optimizations post, which is the feature this page covers.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s pages don&amp;rsquo;t say how the two interact for a game set to Fullscreen, so test one at a time and change the one that matches the mode you are in. If a game is set to Borderless Windowed and tears, start with &lt;a href="https://techfuelhq.com/gaming/optimizations-for-windowed-games-on-or-off-2026/">the windowed-games page&lt;/a>.&lt;/p>
&lt;h2 id="per-game-what-the-publishers-say">Per game: what the publishers say&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>VALORANT:&lt;/strong> Riot&amp;rsquo;s Alt + Tab troubleshooting page, as above. Riot lists the checkbox as a step for Alt + Tab problems, and does not describe it as a way to raise FPS.&lt;/li>
&lt;li>&lt;strong>League of Legends:&lt;/strong> Riot&amp;rsquo;s support page, as above.&lt;/li>
&lt;li>&lt;strong>CS2 and Destiny 2:&lt;/strong> I searched for Valve, Steam and Bungie support pages and found none that recommends the checkbox. What you find for those games is community posts, which I don&amp;rsquo;t treat as sources. Test the game yourself.&lt;/li>
&lt;/ul>
&lt;h2 id="what-i-could-and-couldnt-verify-on-this-machine">What I could and couldn&amp;rsquo;t verify on this machine&lt;/h2>
&lt;p>I read both compatibility keys on the bench machine, read-only. &lt;code>HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers&lt;/code> holds three entries and the HKLM equivalent holds one. They are OneDrive and two AMD setup files with flags like &lt;code>PERPROCESSSYSTEMDPIFORCEOFF&lt;/code> and &lt;code>WIN8RTM&lt;/code>. No game executable appears in either, so I have no ticked example to show you. No Microsoft page I read says where the checkbox is stored, and I didn&amp;rsquo;t tick one to find out, so I won&amp;rsquo;t tell you to edit the registry. Use the Properties dialog.&lt;/p>
&lt;p>I also have no measurement for you. Microsoft&amp;rsquo;s own claim is parity with exclusive fullscreen, and the claims you see elsewhere of a few milliseconds saved, or an FPS gain, come without a method I could check.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/demystifying-full-screen-optimizations/" rel="noopener">Microsoft DirectX Developer Blog, Demystifying Fullscreen Optimizations, December 17, 2019&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/hardware/display-graphics/optimizations-for-windowed-games-in-windows-11" rel="noopener">Microsoft Support, Optimizations for windowed games in Windows 11&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/updates-in-graphics-and-gaming/" rel="noopener">Microsoft DirectX Developer Blog, Updates in Graphics and Gaming, February 16, 2022&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devblogs.microsoft.com/directx/dxgi-flip-model/" rel="noopener">Microsoft DirectX Developer Blog, For best performance, use DXGI flip model, April 9, 2018&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.riotgames.com/en-us/valorant/support-tools/troubleshooting-issues-when-using-alt-tab" rel="noopener">Riot Games Support, Troubleshooting Issues When Using Alt + Tab (VALORANT)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.riotgames.com/en-us/league-of-legends/performance/lag-disabling-full-screen-optimization" rel="noopener">Riot Games Support, Lag - Disabling Full Screen Optimization (League of Legends)&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>Anti-Aliasing On or Off? Which Type to Pick (2026)</title><link>https://techfuelhq.com/gaming/anti-aliasing-on-or-off-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gaming/anti-aliasing-on-or-off-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Anti-aliasing on or off&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>On.&lt;/strong> Anti-aliasing exists to remove stair-stepped edges. The only advice to turn a method off that I found in the vendor text is NVIDIA's note to switch its driver FXAA off if you see artifacts around text.&lt;/li>
&lt;li>&lt;strong>Which kind:&lt;/strong> DLAA, FSR Native AA or XeSS Native AA if the game has one; otherwise the game's TAA or SMAA, MSAA if the engine offers it, FXAA when you need the cheap option.&lt;/li>
&lt;li>&lt;strong>Need frames:&lt;/strong> step down to the upscaler's Quality mode instead of dropping anti-aliasing altogether.&lt;/li>
&lt;li>&lt;strong>NVIDIA driver:&lt;/strong> leave Antialiasing - Mode on Application-controlled. NVIDIA documents Override for games with no anti-aliasing of their own, and for the HDR case covered below.&lt;/li>
&lt;li>&lt;strong>Gamma correction:&lt;/strong> NVIDIA documents it for OpenGL programs. Leave it alone.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>I&amp;rsquo;m not going to tell you one algorithm wins. The documentation describes each method as fixing a different part of the picture at a different price, and Epic&amp;rsquo;s engine docs show the renderer limits which methods a project can use. What I can do is tell you what each one is according to the people who built it, which to reach for first, and where the driver-level switches fit. Everything about image quality below is tied to a vendor description or a named publisher&amp;rsquo;s test. My own bench is a &lt;a href="https://techfuelhq.com/articles/aorus-fo48u-review/">4K 120 Hz OLED&lt;/a> on an RTX 5080, but I ran no image comparison for this page and I&amp;rsquo;m not going to pretend I did.&lt;/p>
&lt;h2 id="what-the-methods-are">What the methods are&lt;/h2>
&lt;p>&lt;strong>MSAA&lt;/strong> (multisample anti-aliasing). Microsoft&amp;rsquo;s Direct3D documentation says it reduces geometry aliasing using pixel coverage and depth-stencil tests at multiple sub-sample locations, and in the same breath that it does not reduce surface aliasing. Unity&amp;rsquo;s documentation agrees: MSAA is better at triangle-edge aliasing than the other techniques but does not fix shader aliasing such as specular or texture aliasing. Epic adds a limit that matters in practice: in Unreal Engine, MSAA is only available on Mobile and Desktop/Console when using the Forward Renderer, and it does not affect aliasing from materials, textures or transparent surfaces.&lt;/p>
&lt;p>&lt;strong>FXAA&lt;/strong> (fast approximate anti-aliasing). A post-processing pass. NVIDIA&amp;rsquo;s white paper calls it a screen-space software approximation that runs as a single pass on a single-sample image, and says it targets aliasing on triangle edges and in shader results. Epic describes FXAA as a spatial-only post-processing technique that is fast to render, but &amp;ldquo;the final image can lose fidelity when compared to other anti-aliasing techniques.&amp;rdquo; Unity calls it the least resource-intensive option in its render pipeline. Tom&amp;rsquo;s Hardware&amp;rsquo;s 2014 explainer says FXAA and MLAA make a scene look softer than MSAA does. For cost, NVIDIA&amp;rsquo;s January 2011 paper gives one figure with its conditions: processing a 1920x1200 frame on a GTX 480 takes under 1 ms with FXAA preset 2. That is 2011 hardware.&lt;/p>
&lt;p>&lt;strong>SMAA&lt;/strong> (subpixel morphological anti-aliasing). Also a post-process. Its authors describe an image-based technique with local contrast analysis for edge detection and handling for sharp geometric features and diagonal lines. Unity&amp;rsquo;s manual says it finds patterns in the borders of an image and blends the pixels along them, and that it gives much sharper results than FXAA.&lt;/p>
&lt;p>&lt;strong>TAA&lt;/strong> (temporal anti-aliasing). Unity: it uses frames from a color history buffer to smooth edges over several frames, and because it works over time it &amp;ldquo;often creates ghosting artifacts in extreme situations,&amp;rdquo; such as an object moving quickly in front of a contrasting surface. Intel&amp;rsquo;s XeSS developer guide describes the same mechanism and says TAA implementations use heuristics to reject mismatched history, and that those heuristics often fail and produce noticeable ghosting, over-blurring or flickering. That is Intel describing TAA&amp;rsquo;s weakness in order to sell its alternative, so read it as a description of the mechanism rather than a verdict. Unity also lists a hard rule: you can&amp;rsquo;t use MSAA with TAA.&lt;/p>
&lt;p>&lt;strong>The upscaler family: DLSS, FSR, XeSS, and their native-resolution modes.&lt;/strong> These are temporal methods that also anti-alias. Intel&amp;rsquo;s guide describes XeSS Super Resolution as a temporal super sampling and anti-aliasing technology that replaces the TAA stage in the renderer. NVIDIA describes DLAA as an anti-aliasing technique that uses the same Super Resolution technology developed for DLSS, constructing the image at native resolution. NVIDIA&amp;rsquo;s programming guide defines it the same way: DLAA is when input and output render sizes are the same, a scaling ratio of 1.0. AMD&amp;rsquo;s FSR Upscaling page (the upscaler formerly called FidelityFX Super Resolution 4) lists a Native AA mode at 1.0x per dimension and says it provides image quality superior to native rendering with a modest performance cost. Intel&amp;rsquo;s guide lists a Native Anti-Aliasing preset at 1.0x, described as anti-aliasing for maximum visual quality.&lt;/p>
&lt;h2 id="what-each-upscaler-mode-renders-at">What each upscaler mode renders at&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Mode&lt;/th>
&lt;th scope="col">Scale (per dimension)&lt;/th>
&lt;th scope="col">Source&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Mode">DLAA&lt;/td>
&lt;td data-label="Scale (per dimension)">1.0&lt;/td>
&lt;td data-label="Source">NVIDIA programming guide&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mode">DLSS Quality&lt;/td>
&lt;td data-label="Scale (per dimension)">1.5&lt;/td>
&lt;td data-label="Source">NVIDIA programming guide&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mode">DLSS Balanced&lt;/td>
&lt;td data-label="Scale (per dimension)">1.724&lt;/td>
&lt;td data-label="Source">NVIDIA programming guide&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mode">DLSS Performance&lt;/td>
&lt;td data-label="Scale (per dimension)">2.0&lt;/td>
&lt;td data-label="Source">NVIDIA programming guide&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mode">FSR Native AA / Quality / Performance&lt;/td>
&lt;td data-label="Scale (per dimension)">1.0 / 1.5 / 2.0&lt;/td>
&lt;td data-label="Source">AMD GPUOpen&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Mode">XeSS Native AA / Quality / Performance (XeSS 1.3 and later)&lt;/td>
&lt;td data-label="Scale (per dimension)">1.0 / 1.7 / 2.3&lt;/td>
&lt;td data-label="Source">Intel XeSS-SR guide&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The scale is how much the render resolution is divided by on each axis, so a 1.5 ratio at 3840x2160 renders internally at 2560x1440 (2160 divided by 1.5). Notice that &amp;ldquo;Quality&amp;rdquo; is not the same ratio on every vendor&amp;rsquo;s menu. Intel&amp;rsquo;s own guide says it raised the scaling for existing presets in XeSS 1.3.&lt;/p>
&lt;p>I won&amp;rsquo;t quote a frame-rate cost for DLAA because NVIDIA&amp;rsquo;s DLSS page gives no figure for it. AMD&amp;rsquo;s wording for Native AA is &amp;ldquo;a modest performance cost.&amp;rdquo; Epic gives numbers for its own Temporal Super Resolution under stated conditions: it says upscaling from 1080p to 4K gets image quality near 4K while reducing GPU frame time by half, and its own captions for the comparison frames read 57.50 ms at native 4K and 33.37 ms at 1080p upscaled (it does not name the GPU, and those two figures are about a 42 percent cut, not half). Unreal&amp;rsquo;s TSR is Epic&amp;rsquo;s own engine feature, not DLSS.&lt;/p>
&lt;p>Hardware support, per each vendor: NVIDIA lists DLAA on RTX 20, 30, 40 and 50 series. AMD lists FSR Upscaling 4.1.2 on Radeon RX 9000, 7000 and 6000 series, with analytical fallback paths (FSR 2.3.4 and 3.1.6) on Radeon RX 500 series and above or equivalent GPUs from other vendors. Intel&amp;rsquo;s repository says XeSS Super Resolution boosts frame rates on all GPUs with Shader Model 6.4 (DP4a) support.&lt;/p>
&lt;h2 id="which-to-pick-and-at-what-resolution">Which to pick, and at what resolution&lt;/h2>
&lt;p>The documents that bear on resolution are these three, and none of them is a rule:&lt;/p>
&lt;ul>
&lt;li>Tom&amp;rsquo;s Hardware&amp;rsquo;s 2014 explainer says higher resolutions reduce the need for heavy anti-aliasing: aliasing is still present and evident in moving scenes as shimmering, but much less noticeable than at lower resolutions, and the cost of AA also rises with resolution.&lt;/li>
&lt;li>Intel&amp;rsquo;s XeSS guide gives recommended output resolutions per preset: Native Anti-Aliasing through Balanced at 1080p and above, Performance and Ultra Performance at 1440p and above.&lt;/li>
&lt;li>Epic says its Temporal Super Resolution approaches native 4K quality with input resolutions as low as 1080p.&lt;/li>
&lt;/ul>
&lt;p>From those, here is my pick order, and it is a judgment, not a measurement:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>The game has DLAA, FSR Native AA or XeSS Native AA and you have frames to spare:&lt;/strong> use it. It is the vendor&amp;rsquo;s anti-aliasing at native resolution with no upscaling.&lt;/li>
&lt;li>&lt;strong>You are short of frames:&lt;/strong> move to that same upscaler&amp;rsquo;s Quality mode rather than turning anti-aliasing off. At 4K that renders at 1440p internally on DLSS or FSR.&lt;/li>
&lt;li>&lt;strong>No upscaler, and the game has TAA or SMAA:&lt;/strong> use whichever looks better to you in motion. TAA&amp;rsquo;s documented weakness is ghosting; SMAA is described as sharper than FXAA.&lt;/li>
&lt;li>&lt;strong>The game offers MSAA:&lt;/strong> Microsoft says it reduces geometry aliasing, and Tom&amp;rsquo;s Hardware says it carries a very high cost in video memory and fill rate. Microsoft and Unity both say it does not fix surface or shader aliasing.&lt;/li>
&lt;li>&lt;strong>You are at the edge of your frame budget:&lt;/strong> FXAA, and accept the softness Epic and Tom&amp;rsquo;s Hardware describe.&lt;/li>
&lt;/ol>
&lt;p>If you are choosing between 4x and 8x MSAA, see the FAQ: the vendors say more samples cost more and look better, and none of them quantify the gap.&lt;/p>
&lt;p>&lt;a href="https://techfuelhq.com/articles/frame-generation-explained-2026/">Frame generation&lt;/a> is a separate switch from anti-aliasing, and so is &lt;a href="https://techfuelhq.com/gaming/vsync-on-or-off-2026/">VSync&lt;/a>; I cover each on its own page. The &lt;a href="https://techfuelhq.com/gaming/dx12-vs-dx11-fps-2026/">DX12 vs DX11&lt;/a> guide matters here only because a game&amp;rsquo;s render path decides which anti-aliasing options it ships with, and I can&amp;rsquo;t tell you that per title from vendor documentation. To see how much pixel density your own screen has, the &lt;a href="https://techfuelhq.com/tools/ppi-calculator/">PPI calculator&lt;/a> does the arithmetic.&lt;/p>
&lt;h2 id="nvidias-driver-level-anti-aliasing-settings">NVIDIA&amp;rsquo;s driver-level anti-aliasing settings&lt;/h2>
&lt;p>NVIDIA&amp;rsquo;s May 26, 2026 driver announcement says the classic Control Panel is retiring for Game Ready and Studio drivers, and says that in the NVIDIA app, Graphics &amp;gt; Program Settings replaces the Control Panel&amp;rsquo;s 3D Settings &amp;gt; Manage 3D Settings screen. On the bench machine the NVIDIA app is 11.0.9.585, and its string table carries these names: Antialiasing - Mode, Antialiasing - Setting, Antialiasing - FXAA, Antialiasing - Gamma Correction, Antialiasing - Transparency and Multi-Frame Sampled AA (MFAA). All but MFAA also appear in the classic help page I read. I did not open the app to see which show up for which game, so check Program Settings for the game you care about.&lt;/p>
&lt;p>&lt;strong>Antialiasing - Mode.&lt;/strong> The app&amp;rsquo;s values read Application-controlled, Enhance the application setting, Override any application setting and Off. NVIDIA&amp;rsquo;s help says Application-controlled is the preferred setting for applications with built-in controls. Enhance requires you to set the game&amp;rsquo;s own anti-aliasing to some level, such as 2x, and then applies NVIDIA&amp;rsquo;s chosen level regardless. Override is for applications with no anti-aliasing controls of their own, or ones whose built-in anti-aliasing doesn&amp;rsquo;t work with HDR rendering. NVIDIA&amp;rsquo;s tips page spells out the HDR case: pick Override, then enable HDR in the game and turn the in-game anti-aliasing off.&lt;/p>
&lt;p>&lt;strong>Does forcing it work?&lt;/strong> NVIDIA&amp;rsquo;s reference doesn&amp;rsquo;t list which graphics APIs honor Override or Enhance. The one named test I found is Tom&amp;rsquo;s Hardware&amp;rsquo;s April 2011 piece, on GeForce and Radeon cards of that generation: across nine games and 14 game-and-render-path scenarios, GeForce Override worked in two of the 14, and Enhance worked in 11 of 14 for adding coverage-sampling modes. In DirectX 10 and 11 titles, it reported that Enhance only took effect if the multisample count matched the one set in the game. That is 2011 drivers and 2011 games. I have not repeated it. Treat it as a reason to test a forced setting in the game you care about, not as a statement about current drivers.&lt;/p>
&lt;p>&lt;strong>Antialiasing - FXAA.&lt;/strong> NVIDIA&amp;rsquo;s app text describes it as a shader-based post-processing technique that can be applied to any program, including those without other forms of hardware-based anti-aliasing. The same text warns that enabling it globally &amp;ldquo;may affect all programs rendered on the GPU, including video players and Windows desktop,&amp;rdquo; and suggests turning it off if you notice artifacts or dithering around edges of objects, particularly text. That is the reason I&amp;rsquo;d set it per game, never globally.&lt;/p>
&lt;p>&lt;strong>Antialiasing - Gamma correction.&lt;/strong> The question behind the &amp;ldquo;on or off&amp;rdquo; searches. NVIDIA&amp;rsquo;s classic help says it &amp;ldquo;allows you to enable or disable gamma correction antialiasing to improve the color and quality of 3D images in OpenGL programs.&amp;rdquo; The NVIDIA app&amp;rsquo;s text says &amp;ldquo;Select On to improve the quality and color of 3D images&amp;rdquo; and doesn&amp;rsquo;t mention OpenGL. Neither says what it does in a DirectX or Vulkan game, and neither says what turning it off costs you. I&amp;rsquo;d leave it at whatever it is and not chase it.&lt;/p>
&lt;p>&lt;strong>Antialiasing - Transparency.&lt;/strong> NVIDIA: it minimizes visible aliasing on the edges of images with transparent textures; multisampling provides superior performance and supersampling superior quality. AMD&amp;rsquo;s equivalent, in the Adrenalin guide I checked (updated March 3, 2025, written against 23.9.1), is Adaptive Anti-Aliasing, which it says covers transparent textures where plain MSAA cannot, such as fences.&lt;/p>
&lt;p>&lt;strong>DSR.&lt;/strong> The app describes Dynamic Super Resolution as rendering at a high resolution and downscaling with filtering, usable with other anti-aliasing settings, aimed at games without in-game anti-aliasing settings or where in-game anti-aliasing is insufficient. Its Smoothness slider text: lower is sharper but more aliased, higher is smoother but blurrier.&lt;/p>
&lt;p>On Radeon, the Adrenalin guide lists the equivalent three modes (Use, Enhance, Override Application Settings), methods Multisampling, Adaptive and Sparse Grid Supersampling, and a Morphological option. AMD says Morphological Anti-Aliasing can add a subtle blur in some situations and works only with Enhance or Override and in exclusive full screen mode.&lt;/p>
&lt;h2 id="edge-cases">Edge cases&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>HDR plus anti-aliasing:&lt;/strong> only the case NVIDIA documents above. Anything else about HDR and a given game is outside what I read.&lt;/li>
&lt;li>&lt;strong>A game with an upscaler but no DLAA option:&lt;/strong> NVIDIA&amp;rsquo;s March 2025 app update post says the &amp;ldquo;DLSS Override - Super Resolution&amp;rdquo; setting can enable DLAA in games lacking native support when Super Resolution is on in the game. On my bench&amp;rsquo;s app build the setting is named &amp;ldquo;DLSS Override - Super Resolution Mode&amp;rdquo; and its Mode list includes DLAA. The app&amp;rsquo;s own text says the setting is supported for select DLSS games and points you to NVIDIA Overlay &amp;gt; Statistics &amp;gt; DLSS to check override status, so check that rather than assuming.&lt;/li>
&lt;li>&lt;strong>Blur you attribute to anti-aliasing:&lt;/strong> a softer image can also come from the display or from motion blur. The &lt;a href="https://techfuelhq.com/gaming/motion-blur-on-or-off-2026/">motion blur guide&lt;/a> covers that switch.&lt;/li>
&lt;/ul></description></item><item><title>PC Making a Buzzing Noise? Fan, Coil Whine, Drive, Pump or PSU (2026)</title><link>https://techfuelhq.com/articles/pc-making-buzzing-noise-2026/</link><pubDate>Wed, 18 Nov 2026 00:47:38 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/pc-making-buzzing-noise-2026/</guid><atom:updated>2026-11-18T00:47:38Z</atom:updated><description>&lt;p>A buzz from a PC doesn&amp;rsquo;t name its own source, so the job is to sort it. The vendor pages I read cover five sources of buzzing, humming or whining: a fan, coil whine, a hard drive, a liquid cooler&amp;rsquo;s pump, and the power supply. The cheapest sorting tool is a question: when does it happen?&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">What you notice&lt;/th>
&lt;th scope="col">What the vendor pages say it is&lt;/th>
&lt;th scope="col">First safe check&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="What you notice">Rattle, click or buzz from a PC with a liquid cooler&lt;/td>
&lt;td data-label="What the vendor pages say it is">NZXT&amp;rsquo;s AIO guide: &amp;ldquo;usually a fan, not the pump&amp;rdquo;&lt;/td>
&lt;td data-label="First safe check">Power off, then check mounting, blade contact, dust&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you notice">High-pitched electrical whine, often under load&lt;/td>
&lt;td data-label="What the vendor pages say it is">Coil whine; Corsair calls it a byproduct of working components&lt;/td>
&lt;td data-label="First safe check">Compare against the &lt;a href="https://techfuelhq.com/articles/gpu-or-psu-coil-whine/">coil whine guide&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you notice">Noise that comes with drive activity, or from the drive bay&lt;/td>
&lt;td data-label="What the vendor pages say it is">Drive sounds, covered by Seagate and Western Digital&lt;/td>
&lt;td data-label="First safe check">Back up first, then test the drive&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you notice">Gurgling near the radiator&lt;/td>
&lt;td data-label="What the vendor pages say it is">Air in the pump, per NZXT&lt;/td>
&lt;td data-label="First safe check">See the &lt;a href="https://techfuelhq.com/articles/how-to-tell-if-aio-pump-is-working-2026/">AIO pump check&lt;/a>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you notice">Grinding that gets worse over weeks&lt;/td>
&lt;td data-label="What the vendor pages say it is">NZXT lists this as a failing pump&lt;/td>
&lt;td data-label="First safe check">Contact the cooler&amp;rsquo;s maker&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Never open the power supply to look for the noise. More on that below.&lt;/p>
&lt;h2 id="start-by-writing-down-when-it-happens">Start by writing down when it happens&lt;/h2>
&lt;p>This part is my method, not a vendor&amp;rsquo;s. Before you pull a side panel off, note whether the buzz is constant, only under load, only when the drive is being read, only at startup, or only after the PC has been running a while. The answer decides which section below to read, and a phone recording held near the case helps if you end up talking to support. Corsair&amp;rsquo;s own support page asks you to find the serial number and open a ticket, and a recording is easier to describe than a sound.&lt;/p>
&lt;h2 id="a-buzzing-fan">A buzzing fan&lt;/h2>
&lt;p>Corsair&amp;rsquo;s fan guide has the plainest checklist I&amp;rsquo;ve found, and it&amp;rsquo;s written for Corsair fans, though I&amp;rsquo;d run the same checks on any case fan:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Check the installation.&lt;/strong> Each fan should be seated and secured in its mount. Corsair says loose screws or improper installation can cause vibrations.&lt;/li>
&lt;li>&lt;strong>Clean the fans.&lt;/strong> Dust and debris can cause noise. Corsair says to turn the system off first and then gently clean the blades and the area around them.&lt;/li>
&lt;li>&lt;strong>Look for obstructions.&lt;/strong> Corsair says to check for wires or foreign objects touching the blades, and that even a slight touch can make noise.&lt;/li>
&lt;li>&lt;strong>Set a consistent fan speed.&lt;/strong> Corsair says doing that in iCUE can eliminate clicking caused by variable fan speeds, or help isolate the issue.&lt;/li>
&lt;/ul>
&lt;p>If the noise persists after those, Corsair says to contact its support team about a replacement.&lt;/p>
&lt;p>One more check comes from NZXT&amp;rsquo;s cooler troubleshooting article. It says to power off the PC and disconnect the affected fan first, then spin it by hand. NZXT says a working fan should spin freely and slow gradually, and that a fan that stops suddenly or resists likely has a seized motor.&lt;/p>
&lt;p>I&amp;rsquo;d keep your hands out of a running case. NZXT&amp;rsquo;s articles do describe stopping each fan one at a time to find the noisy one, and I&amp;rsquo;m not repeating the by-hand method here. NZXT says not to attempt to stop its high-performance F120X and F140X fans by hand, that those fans carry enough force to cause serious injury, and that they should be stopped through software or by disconnecting power. If the fan in question is the CPU fan and it&amp;rsquo;s stopped rather than noisy, the &lt;a href="https://techfuelhq.com/articles/cpu-fan-not-spinning-2026/">CPU fan guide&lt;/a> is the right page.&lt;/p>
&lt;h2 id="coil-whine-the-high-pitched-electrical-one">Coil whine: the high-pitched electrical one&lt;/h2>
&lt;p>NZXT describes it as a high-pitched buzzing or whining sound caused by electrical current. In its AIO guide, a high-pitched electrical whine from the pump motor is listed as coil whine and as normal.&lt;/p>
&lt;p>Corsair&amp;rsquo;s explanation for power supplies is short. When the current through an inductor changes, the magnetic field changes, and the coil&amp;rsquo;s small attraction and repulsion shows up as vibration and sound. Corsair says all power supplies generate it, and that many have sound-dampening material to reduce it. Its words on defects: coil whine is &amp;ldquo;not exactly a defect, but rather a byproduct of the components working as intended.&amp;rdquo; If you&amp;rsquo;re worried about your unit, it says to create a ticket with its support team.&lt;/p>
&lt;p>I won&amp;rsquo;t repeat the GPU-versus-PSU sorting here. The &lt;a href="https://techfuelhq.com/articles/gpu-or-psu-coil-whine/">GPU or PSU coil whine guide&lt;/a> walks through that with a frame-rate cap and fan-speed notes, and the &lt;a href="https://techfuelhq.com/data/coil-whine-database/">coil whine database&lt;/a> collects owner reports by model.&lt;/p>
&lt;h2 id="a-buzzing-humming-or-clicking-hard-drive">A buzzing, humming or clicking hard drive&lt;/h2>
&lt;p>Hard drives are the one source where the vendors give you a clear line between normal and not.&lt;/p>
&lt;p>Seagate&amp;rsquo;s sounds page is written for its Seagate and LaCie external drives, and it says clicking during reads and writes is a sign the drive is active, a hard click can happen when the heads park at shutdown or sleep, and platter spin typically makes a whirring sound. It lists a hard click that persists or comes with repeating clunking or grinding as pointing to a likely physical problem. Western Digital says good drives make clicking noises every few seconds, and that random clicking is normal on helium-based drives.&lt;/p>
&lt;p>Neither page I read uses the word &amp;ldquo;buzzing.&amp;rdquo; Western Digital&amp;rsquo;s list of strange sounds during normal operation includes humming and vibration, and adds that vibration may come from mounting; its suggestion for internal drives is rubber strips between the drive and the case.&lt;/p>
&lt;p>The sounds to act on:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Grinding.&lt;/strong> Seagate&amp;rsquo;s troubleshooter says to power the drive down immediately to avoid further damage. Seagate&amp;rsquo;s sounds page says that if you need the data, contact Data Recovery Services before troubleshooting.&lt;/li>
&lt;li>&lt;strong>Repeated, regular tapping, beeping or clicking.&lt;/strong> Seagate calls these possible indicators of abnormal function, and says two hard clicks at startup followed by a boot error or shutdown is a symptom of a failed drive.&lt;/li>
&lt;li>&lt;strong>Any sound with a drive you can&amp;rsquo;t afford to lose.&lt;/strong> Seagate says it&amp;rsquo;s always important to make an immediate backup if a drive failure is possible.&lt;/li>
&lt;/ul>
&lt;p>To confirm the noise is the drive, Seagate&amp;rsquo;s page for noisy drives describes an acoustical spin-down test in SeaTools that temporarily spins down internal drives. If the sound stops when the drive spins down, the drive is making it; if the sound stays, the drive isn&amp;rsquo;t the cause. Seagate points to its Document ID 201271 for the steps, which I haven&amp;rsquo;t read. For health numbers on any brand, the &lt;a href="https://techfuelhq.com/articles/hard-drive-health-check-2026/">hard drive health check&lt;/a> covers SMART values.&lt;/p>
&lt;h2 id="a-pump-buzzing-or-clicking">A pump buzzing or clicking&lt;/h2>
&lt;p>If you have a liquid cooler, NZXT&amp;rsquo;s guide splits the noises this way: gurgling or bubbling is air in the pump or radiator and worth fixing; rattling, clicking or buzzing is usually a fan, so check the fans first; a high-pitched electrical whine is coil whine from the pump motor and normal; grinding, or noise that worsens over weeks, is a failing pump and means contacting support. That table is for NZXT coolers, and I use a Kraken 360, but the logic of ruling out the fans first is general.&lt;/p>
&lt;p>NZXT&amp;rsquo;s air-clearing steps are specific to its pump design, so I&amp;rsquo;ll leave them in its article and not paraphrase them. The one general point is that NZXT says if the noise persists after two air-clearing attempts or worsens, you contact support. For how to check the pump itself, the &lt;a href="https://techfuelhq.com/articles/how-to-tell-if-aio-pump-is-working-2026/">AIO pump guide&lt;/a> covers reading the tach.&lt;/p>
&lt;h2 id="a-buzzing-power-supply">A buzzing power supply&lt;/h2>
&lt;p>Corsair&amp;rsquo;s guidance on a PSU buzz is the coil whine explanation above. I don&amp;rsquo;t have a manufacturer source for how to tell a power supply&amp;rsquo;s own noise from a graphics card&amp;rsquo;s beyond the site guide linked there, and I won&amp;rsquo;t make one up.&lt;/p>
&lt;p>What I can source is what not to do. Corsair&amp;rsquo;s manual says high voltages are present in the power supply, and: &amp;ldquo;Do not open the power supply case or attempt to repair the power supply; there are no user-serviceable components.&amp;rdquo; It also says failing to comply with the manufacturer&amp;rsquo;s instructions or its safety instructions will immediately void all warranties and guarantees. So the isolation for a power supply happens outside it. The only controlled test I&amp;rsquo;d run is a swap with a compatible known-good unit and its own cables, or I&amp;rsquo;d hand the unit to the maker. For the swap, Corsair&amp;rsquo;s manual starts by disconnecting the AC power cord from the wall outlet and from the existing power supply, and it says not to insert any objects into a power supply&amp;rsquo;s ventilation or fan grill. The &lt;a href="https://techfuelhq.com/articles/psu-failure-symptoms-2026/">PSU failure guide&lt;/a> covers that swap and its limits.&lt;/p>
&lt;h2 id="when-its-a-warranty-matter">When it&amp;rsquo;s a warranty matter&lt;/h2>
&lt;p>Each vendor draws the line slightly differently, so check your own warranty. What I read:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Fans:&lt;/strong> Corsair says if the noise persists after its checks, contact support and they can assist with a replacement. NZXT says to contact its support team for a replacement under warranty.&lt;/li>
&lt;li>&lt;strong>Liquid cooler:&lt;/strong> NZXT says if noise or overheating continues after a second round of its steps, the cooler may need replacing. It says not to open the cooler to drain or clean the coolant, because that is not covered under the limited warranty. NZXT lists 6 years for Kraken Elite, Plus and 2023 models, 5 years for Core, and 3 years for Kraken 120, counted from purchase at an authorized reseller.&lt;/li>
&lt;li>&lt;strong>Power supply:&lt;/strong> Corsair treats coil whine as not exactly a defect and invites a support ticket. Opening the unit is the thing that risks the warranty.&lt;/li>
&lt;li>&lt;strong>Hard drive:&lt;/strong> Seagate&amp;rsquo;s FAQ says a replacement needs the drive in warranty, passing a visual mechanical inspection without being opened or modified, and failing the SeaTools test where that applies. It says its limited warranty does not cover data loss or recovery costs. The FAQ is marked Rev. July 2016, so confirm the current terms. Seagate&amp;rsquo;s noisy-drive page says to replace a drive that fails SeaTools.&lt;/li>
&lt;/ul>
&lt;p>If the noise is loud, getting worse, or comes with shutdowns or errors, stop troubleshooting and contact the maker. A recording and the serial number save a round of emails.&lt;/p></description></item><item><title>ASUS ROG STRIX B650-A GAMING WIFI: Slot, Lane and Port Sharing</title><link>https://techfuelhq.com/data/compatibility-atlas/asus-rog-strix-b650-a-gaming-wifi/</link><pubDate>Tue, 17 Nov 2026 18:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/data/compatibility-atlas/asus-rog-strix-b650-a-gaming-wifi/</guid><atom:updated>2026-11-17T18:00:00Z</atom:updated><description>&lt;h2 id="how-to-check-a-row-yourself">How to check a row yourself&lt;/h2>
&lt;p>Every manual row gives a printed page. Open the manual from the link in the sources section, go to that page, and the sentence I restated is there. The printed page numbers run in Roman numerals for the front matter and as chapter and page, such as 1-10, after that. The PDF page is given too, because a PDF reader counts from the cover.&lt;/p>
&lt;p>The web rows name the row of ASUS&amp;rsquo;s specification table they came from and the day I read it. A web page can change without notice, so a web row is only as good as its date.&lt;/p></description></item><item><title>Deal or Mirage</title><link>https://techfuelhq.com/data/deal-or-mirage/</link><pubDate>Tue, 17 Nov 2026 17:45:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/data/deal-or-mirage/</guid><atom:updated>2026-11-17T17:45:00Z</atom:updated><description>&lt;p>A sale banner compares a price with a number the retailer picked. This page compares it with the part&amp;rsquo;s own recorded prices. Each part I track gets one label, worked out by arithmetic from dated observations: a new observed low, below its recent median, ordinary, or above its recent median. A sale price that sits above the part&amp;rsquo;s own recent median is the mirage in the title.&lt;/p>
&lt;p>A label needs history, and I do not borrow any. Prices collected before the current method came from other sources read by other rules, so none of them is used here. Until a part has enough days recorded the same way, its label reads insufficient history and shows the count.&lt;/p>
&lt;p>The percentage against launch price on the graphics cards is a separate figure. It needs no history, because the launch price is fixed, and it is not one of the labels.&lt;/p></description></item><item><title>The DDR5 Clock</title><link>https://techfuelhq.com/data/ddr5-clock/</link><pubDate>Tue, 17 Nov 2026 17:45:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/data/ddr5-clock/</guid><atom:updated>2026-11-17T17:45:00Z</atom:updated><description>&lt;p>DDR5 prices get passed around as screenshots: a cart, a listing, a chart with no source. A screenshot has no date I can check and no rule I can read. This page is built to be the opposite. It gives one number, the date that number belongs to, and the rules that produced it.&lt;/p>
&lt;p>I read Newegg&amp;rsquo;s catalogue once a day. When the capture runs and enough kits qualify, the reading at the top changes and a frozen page is added for that date. When it does not, nothing on this page moves, and the status panel counts how old the reading is.&lt;/p>
&lt;p>A single reading says nothing about direction. The change cells stay in words until there is a second reading taken the same way, and I do not fill that gap with older numbers collected a different way.&lt;/p>
&lt;p>The table behind the number, every listing title, the method history and the corrections are on the &lt;a href="https://techfuelhq.com/data/ram-price-index/">DDR5 RAM price index&lt;/a>. The Clock is that index reduced to one dated figure with an address you can cite. What forecasters expect next is on &lt;a href="https://techfuelhq.com/articles/when-will-ram-prices-go-down/">When will RAM prices go down?&lt;/a>.&lt;/p></description></item><item><title>Keep It or Upgrade: Is a New Graphics Card Worth It?</title><link>https://techfuelhq.com/tools/keep-it-or-upgrade/</link><pubDate>Tue, 17 Nov 2026 17:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tools/keep-it-or-upgrade/</guid><atom:updated>2026-11-17T17:00:00Z</atom:updated><description>&lt;p>Pick the graphics card you own, the resolution you play at, the smallest speed gain you would pay for and a budget. The tool sets your card to 100%, measures every other card in the benchmark table against it, and answers in one dated sentence: keep the card, or buy a named card at a named price.&lt;/p>
&lt;p>It only uses numbers it can show a source for. Where it has no price for a card, it says so and waits for you to type one.&lt;/p>
&lt;h2 id="how-to-use-it">How to use it&lt;/h2>
&lt;ol>
&lt;li>&lt;strong>Pick the card you own.&lt;/strong> The list is grouped by series and covers the same benchmark table as the &lt;a href="https://techfuelhq.com/tools/gpu-comparison/">GPU Comparison Tool&lt;/a>.&lt;/li>
&lt;li>&lt;strong>Pick the resolution.&lt;/strong> 1080p, 1440p or 4K. It opens at 1440p.&lt;/li>
&lt;li>&lt;strong>Set the smallest uplift worth paying for.&lt;/strong> It opens at 40%. That is my own starting point, not a measurement. The presets are 25%, 40%, 60% and 100%.&lt;/li>
&lt;li>&lt;strong>Enter a budget.&lt;/strong> The verdict needs one. A card that costs a cent more is over budget.&lt;/li>
&lt;li>&lt;strong>Read the verdict.&lt;/strong> The four numbers under it show where the field narrowed: how many other cards there are, how many clear your bar, how many of those have a price, and how many fit the budget.&lt;/li>
&lt;li>&lt;strong>Type a price where you have a real one.&lt;/strong> Every card in the Upgrade column has a &amp;ldquo;Your price&amp;rdquo; field. A typed price replaces the price on file for that card.&lt;/li>
&lt;li>&lt;strong>Copy the verdict or the link.&lt;/strong> The link carries your card, resolution, bar, budget and typed prices, so it reopens the same verdict.&lt;/li>
&lt;/ol>
&lt;h2 id="how-the-verdict-is-worked-out">How the verdict is worked out&lt;/h2>
&lt;p>Everything is whole percents, because the benchmark index only carries one decimal.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Rebase.&lt;/strong> &lt;code>relative score = card's index ÷ your card's index × 100&lt;/code>, rounded to a whole percent. Your card is 100%.&lt;/li>
&lt;li>&lt;strong>Uplift.&lt;/strong> &lt;code>uplift = relative score − 100&lt;/code>. A card clears your bar when its uplift is at least your minimum.&lt;/li>
&lt;li>&lt;strong>Dollars per point.&lt;/strong> &lt;code>price ÷ uplift&lt;/code>. One point is one percentage point of uplift over your card.&lt;/li>
&lt;li>&lt;strong>Best pick.&lt;/strong> The lowest dollars per point among cards that clear the bar and cost no more than the budget. A tie goes to the larger uplift, then the lower price.&lt;/li>
&lt;li>&lt;strong>Keep.&lt;/strong> If priced cards clear the bar but none fits the budget, the verdict is keep. If no card in the table clears the bar at all, the verdict is keep and no price is involved.&lt;/li>
&lt;li>&lt;strong>No verdict.&lt;/strong> If cards clear the bar but none has a price, the tool says so instead of guessing.&lt;/li>
&lt;/ul>
&lt;p>The date in the sentence is the capture date of the listing prices, not the day you read it. When the pick turns on a price you typed, the sentence says so and carries no capture date. When no card is fast enough, the sentence is dated by the benchmark table.&lt;/p>
&lt;h2 id="a-worked-verdict">A worked verdict&lt;/h2>
&lt;p>Take a GeForce RTX 3070 at 1440p with a 40% bar and a $1,000 budget, using the November 17, 2026 price capture.&lt;/p>
&lt;p>The RTX 3070&amp;rsquo;s 1440p index is 34.8 and the Radeon RX 9070 XT&amp;rsquo;s is 69.7. &lt;code>69.7 ÷ 34.8 × 100&lt;/code> is 200%, so the uplift is 100 points. The lowest qualifying RX 9070 XT listing on that capture was $999.99, and &lt;code>999.99 ÷ 100&lt;/code> is $10.00 per point. The GeForce RTX 5070 also cleared the bar and fit the budget: 166% of the RTX 3070, 66 points, $919.99, which is $13.94 per point. The RX 9070 XT was the best pick.&lt;/p>
&lt;p>Drop the budget to $700 and nothing with a price on that capture cleared a 40% bar for the money, so the verdict was keep. A later capture will change these numbers. That is why the sentence is dated.&lt;/p>
&lt;h2 id="where-the-prices-come-from">Where the prices come from&lt;/h2>
&lt;p>Observed prices come from my &lt;a href="https://techfuelhq.com/data/gpu-price-index/">GPU Price Index&lt;/a>. For each card the index tracks, the tool uses the lowest qualifying listing in Newegg&amp;rsquo;s affiliate catalogue on the latest capture date. That catalogue names no seller. The listing is one board from one maker, and the price is a dated observation, not a live quote. Amazon prices are never used.&lt;/p>
&lt;p>A tracked card can have no qualifying listing on a capture. For that card the tool shows the maker&amp;rsquo;s launch price, labelled &amp;ldquo;launch price, not a current price&amp;rdquo;, and leaves it out of the arithmetic.&lt;/p>
&lt;p>Every other card has no price until you type one. The full file is &lt;a href="https://techfuelhq.com/data/gpu-price-observations.csv" download type="text/csv">gpu-price-observations.csv&lt;/a>.&lt;/p>
&lt;h2 id="what-this-tool-does-not-know">What this tool does not know&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Anything but native raster.&lt;/strong> The scores are the &lt;a href="https://www.tomshardware.com/reviews/gpu-hierarchy,4388.html" rel="noopener">Tom&amp;rsquo;s Hardware GPU benchmarks hierarchy&lt;/a> raster table dated June 24, 2026: one 11-game geometric mean at native resolution, with each resolution normalized separately. Ray tracing, DLSS, FSR, XeSS and frame generation are outside it.&lt;/li>
&lt;li>&lt;strong>Prices beyond one retailer&amp;rsquo;s catalogue.&lt;/strong> A cheaper listing elsewhere, a used card or a rebate is yours to type in.&lt;/li>
&lt;li>&lt;strong>Resale value.&lt;/strong> It does not subtract what your current card would sell for.&lt;/li>
&lt;li>&lt;strong>Power and fit.&lt;/strong> It does not check board power, your power supply, connectors or case clearance. Use the &lt;a href="https://techfuelhq.com/tools/psu-wattage-calculator/">PSU calculator&lt;/a> before you buy.&lt;/li>
&lt;li>&lt;strong>Your processor.&lt;/strong> It does not test whether the graphics card is what limits your games.&lt;/li>
&lt;li>&lt;strong>Frame rates.&lt;/strong> A relative score is not FPS and does not promise a result in any one game.&lt;/li>
&lt;/ul>
&lt;h2 id="before-you-spend-anything">Before you spend anything&lt;/h2>
&lt;p>Test whether the graphics card is the limit. The &lt;a href="https://techfuelhq.com/tools/pc-bottleneck-calculator/#test-the-limit-in-your-game">CPU and GPU lookup&amp;rsquo;s diagnostic steps&lt;/a> compare a repeatable scene at two render resolutions. If lowering the render resolution raises the frame rate, rendering work was the limit in that test. If it barely moves, the cause needs more diagnosis before you buy a card. &lt;a href="https://techfuelhq.com/articles/low-gpu-usage-2026/">Low GPU usage in games&lt;/a> covers frame caps, the active GPU and the other usual causes.&lt;/p>
&lt;p>To see two cards side by side at all three resolutions, take them to the &lt;a href="https://techfuelhq.com/tools/gpu-comparison/">GPU Comparison Tool&lt;/a>. For the whole field in one ranked list, use the &lt;a href="https://techfuelhq.com/articles/gpu-hierarchy-2026/">GPU hierarchy&lt;/a>.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>Performance: &lt;a href="https://www.tomshardware.com/reviews/gpu-hierarchy,4388.html" rel="noopener">Tom&amp;rsquo;s Hardware GPU benchmarks hierarchy&lt;/a>, June 24, 2026 raster table.&lt;/li>
&lt;li>Prices: my &lt;a href="https://techfuelhq.com/data/gpu-price-index/">GPU Price Index&lt;/a>, which publishes the method, every observation and the launch-price sources.&lt;/li>
&lt;li>Undervolt results in the keep plan: my &lt;a href="https://techfuelhq.com/articles/gpu-undervolt-settings-database/">GPU undervolt database&lt;/a>, where every row links its source.&lt;/li>
&lt;li>Settings guides in the keep plan: the guides themselves, each with its own sources.&lt;/li>
&lt;/ul></description></item><item><title>Coil Whine Analyzer: Find the Frequency and Test What Changes It</title><link>https://techfuelhq.com/tools/coil-whine-analyzer/</link><pubDate>Tue, 17 Nov 2026 17:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tools/coil-whine-analyzer/</guid><atom:updated>2026-11-17T17:00:00Z</atom:updated><description>&lt;p>Record ten to twenty seconds of the noise with a phone, drop the file above and the instrument reports the strongest narrow peak in the band you search: its frequency, its level, how far it stands above the background and how steady it stayed. Then change one thing, record again, and it tells you in plain words whether the peak moved, dropped or stayed where it was.&lt;/p>
&lt;p>I built it for the point just before a return or a warranty claim. &amp;ldquo;It whines&amp;rdquo; gives a support agent nothing to check. A steady peak at one frequency in an uncapped menu, gone with a 60 FPS cap, same phone in the same spot, is a description someone can act on.&lt;/p>
&lt;h2 id="record-a-capture-the-instrument-can-use">Record a capture the instrument can use&lt;/h2>
&lt;ol>
&lt;li>&lt;strong>Start the scene that makes the noise&lt;/strong> and leave it running. Mute the speakers.&lt;/li>
&lt;li>&lt;strong>Put the phone outside the closed case&lt;/strong>, somewhere you can find again: on the desk a hand&amp;rsquo;s width from the side panel works. Keep it clear of fans and vents. Do not put a phone or anything else inside a running PC.&lt;/li>
&lt;li>&lt;strong>Record ten to twenty seconds&lt;/strong> in the phone&amp;rsquo;s voice recorder. If the recorder offers an uncompressed or lossless setting, use it. The instrument reports where a recording stops carrying signal.&lt;/li>
&lt;li>&lt;strong>Drop the file on the capture panel.&lt;/strong> That is capture A.&lt;/li>
&lt;li>&lt;strong>Change one thing&lt;/strong>, leave the phone exactly where it was, record again and drop that file in as B.&lt;/li>
&lt;/ol>
&lt;p>The phone, the recording app and the position have to be the same for both captures. If they are not, the frequency comparison still holds and the level comparison does not.&lt;/p>
&lt;h2 id="what-the-readout-means">What the readout means&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Peak frequency&lt;/strong> is the strongest narrow peak between the two edges of the search band. The capture is cut into overlapping frames, each frame gets a Hann window and a Fourier transform sized so one bin is at most 6 Hz wide (8,192 points at 48 kHz, which is 5.86 Hz), and the peak is placed between bins by three-point interpolation. A capture shorter than about a second gets a shorter transform and a coarser bin, and the readout prints the bin width it used.&lt;/li>
&lt;li>&lt;strong>Level&lt;/strong> is in dBFS: decibels below the recording&amp;rsquo;s own digital full scale. It is useful only against another capture made the same way.&lt;/li>
&lt;li>&lt;strong>Above background&lt;/strong> is how far the peak stands over the median of the spectrum around it. Anything under 10 dB is not listed, so a recording with no tone in it reports no peak instead of a guess.&lt;/li>
&lt;li>&lt;strong>Steadiness&lt;/strong> has two parts: the share of the capture in which the peak was there, and how far its frequency ranged (5th to 95th percentile).&lt;/li>
&lt;li>&lt;strong>The A/B result&lt;/strong> calls a frequency shift only when it is larger than both two analysis bins and the wobble measured inside the captures. It calls a level change at 3 dB or the frame-to-frame variation, whichever is larger. Smaller differences are reported as no change.&lt;/li>
&lt;/ul>
&lt;p>The search band starts at 1,000 Hz. That is a starting setting and not a statement about where coil noise sits. If what you hear is a buzz, lower the edge and look at the spectrum.&lt;/p>
&lt;p>I test the arithmetic against synthetic tones with known answers. A tone in noise comes back within 1 Hz and 0.5 dB. A tone only 19 dB above the background comes back within 2 Hz and 1.5 dB. Those signals are test files, and none of them is published or presented as a recording.&lt;/p>
&lt;h2 id="what-coil-whine-is">What coil whine is&lt;/h2>
&lt;p>A coil is an inductor or a transformer. &lt;a href="https://www.we-online.com/components/products/media/861473" rel="noopener">Würth Elektronik&amp;rsquo;s application note ANP118&lt;/a> gives two causes. A magnetic core changes its dimensions slightly in a magnetic field, an effect called magnetostriction, and when the field changes at an audible rate the core&amp;rsquo;s vibration reaches the air. The windings also feel a force from the field and vibrate. &lt;a href="https://product.tdk.com/en/techlibrary/solutionguide/acoustic-noise.html" rel="noopener">TDK&amp;rsquo;s guide to acoustic noise in power inductors&lt;/a> lists the same two and adds attraction from the magnetized core. Both say a circuit board or a neighbouring part that resonates at the same frequency makes it louder.&lt;/p>
&lt;p>The switching itself is too fast to hear. Würth puts the switching frequency of a buck converter at 75 kHz to 2.5 MHz in most cases, and TDK at several hundred kilohertz to several megahertz, against the 20 Hz to 20 kHz hearing range Würth gives. What reaches your ear is slower: a regulator that switches in bursts or skips pulses at light load, a switching frequency that falls as the load drops, or a load that itself changes at an audible rate. Each of those depends on what the hardware is doing, which is why the first steps of the sweep change the load.&lt;/p>
&lt;p>Würth also notes that hearing is most sensitive between 2 and 8 kHz, so a whine there is noticed quickly, while one at 18 kHz goes unheard by most people in middle age. The range varies from person to person, which the note gives as the reason not everyone hears the same coil.&lt;/p>
&lt;p>It is not always a coil. A &lt;a href="https://pmc.ncbi.nlm.nih.gov/articles/PMC9147252/" rel="noopener">2022 review in &lt;em>Sensors&lt;/em>&lt;/a> describes ceramic capacitors that vibrate through piezoelectric and electrostrictive effects and drive the circuit board in the audible range. A spectrum cannot tell a coil from a capacitor. It can tell you the frequency, and whether it follows what you changed.&lt;/p>
&lt;h2 id="why-the-frame-cap-comes-first">Why the frame cap comes first&lt;/h2>
&lt;p>It is the change a manufacturer names. &lt;a href="https://www.intel.com/content/www/us/en/support/articles/000093133/graphics.html" rel="noopener">Intel&amp;rsquo;s support article for Arc cards&lt;/a> says the noise usually happens at a high frame rate and lists capping the frame rate and enabling V-Sync as its first two recommendations. &lt;a href="https://www.amd.com/en/products/software/adrenalin/frtc.html" rel="noopener">AMD says its frame-rate target can reduce GPU power consumption&lt;/a> and applies in menus and loading screens, where frame rates can run into the hundreds.&lt;/p>
&lt;p>It does not work for everyone. The &lt;a href="https://techfuelhq.com/data/coil-whine-database/">coil whine database&lt;/a> asks each owner whether a cap changes the noise, and the answers on file are close to an even split. My own ASUS ROG Astral RTX 5080 OC is report number one there: a faint whine in uncapped menus that any cap removes.&lt;/p>
&lt;h2 id="before-you-open-a-warranty-claim">Before you open a warranty claim&lt;/h2>
&lt;p>Read what the maker has already published. &lt;a href="https://www.asus.com/us/support/faq/1050014/" rel="noopener">ASUS&lt;/a> describes slight high-frequency noise from a graphics card as a characteristic of the components and says it will not affect the hardware. &lt;a href="https://us.msi.com/faq/10183" rel="noopener">MSI&lt;/a> describes the vibration as normal behavior and not a hardware defect. Intel says it should not damage the card or affect how it works, and tells owners with an extreme case to contact support. &lt;a href="https://help.corsair.com/hc/en-us/articles/19865055003021-PSU-What-is-coil-whine" rel="noopener">Corsair&lt;/a> says power-supply coil whine is not exactly a defect and asks concerned owners to open a ticket. None of those pages decides an individual claim.&lt;/p>
&lt;p>The copyable summary does not prove a defect. It shows that the noise is repeatable, where it sits and what changes it, in a few lines someone can read quickly. Send it with the exact model, the purchase date, the workload and a recording made from where you normally sit. If the return window is still open, &lt;a href="https://techfuelhq.com/articles/gpu-or-psu-coil-whine/#keep-it-exchange-it-or-test-another-supply">decide between keeping, exchanging and testing another supply&lt;/a> before it closes.&lt;/p>
&lt;p>Stop and power down if the noise comes with smoke, a burning smell, visible connector damage or repeated shutdowns. That is a fault to have assessed, and the &lt;a href="https://techfuelhq.com/articles/psu-failure-symptoms-2026/">power supply failure guide&lt;/a> covers it.&lt;/p>
&lt;h2 id="what-a-phone-recording-cannot-tell-you">What a phone recording cannot tell you&lt;/h2>
&lt;p>&lt;strong>How loud it is.&lt;/strong> The level is relative to the recording. For its voice-recognition input, &lt;a href="https://source.android.com/docs/compatibility/15/android-15-cdd#542_capture_for_voice_recognition" rel="noopener">Android&amp;rsquo;s compatibility document&lt;/a> asks for a microphone response within ±3 dB only between 100 Hz and 4,000 Hz, strongly recommends no more than ±30 dB from 4,000 Hz to 22 kHz, and lets the sensitivity at 1 kHz sit 3 dB either side of its target. Inside that recommendation a peak at 9 kHz can read 30 dB higher or lower than the same sound would at 1 kHz, and two phones need not agree. No sound pressure figure comes out of this page.&lt;/p>
&lt;p>&lt;strong>Anything above half the sample rate.&lt;/strong> A capture sampled at 48,000 Hz can show nothing above 24,000 Hz; &lt;a href="https://developer.mozilla.org/en-US/docs/Web/API/AnalyserNode/getFloatFrequencyData" rel="noopener">MDN&amp;rsquo;s description of browser frequency data&lt;/a> uses the same example. The instrument prints that ceiling beside every result. Browsers &lt;a href="https://developer.mozilla.org/en-US/docs/Web/API/BaseAudioContext/decodeAudioData" rel="noopener">resample audio when they decode it&lt;/a>, so the page reads WAV files itself and, for other formats, decodes at the rate the file&amp;rsquo;s header states when it states one plainly.&lt;/p>
&lt;p>&lt;strong>Anything the recorder removed.&lt;/strong> If a recording carries no signal above some frequency, the instrument measures where it stops and says so, because a whine above that point would not appear at all.&lt;/p>
&lt;p>&lt;strong>Which part made the sound.&lt;/strong> A higher level beside the graphics card than beside the power supply is a clue about location. &lt;a href="https://techfuelhq.com/articles/gpu-or-psu-coil-whine/">Locating the noise before swapping parts&lt;/a> covers the rest.&lt;/p>
&lt;h2 id="live-microphone">Live microphone&lt;/h2>
&lt;p>Live listening appears only when the browser lets this page use a microphone. When it does, I ask for the raw signal with echo cancellation, noise suppression and automatic gain switched off, and the page prints what the browser granted, because a browser may keep them on. The capture goes through the same analysis as a file.&lt;/p>
&lt;h2 id="reference-recordings-come-later">Reference recordings come later&lt;/h2>
&lt;p>There is no library to match against yet. Reference recordings from my own card, cooler and power supply come later. Until then the instrument works on your captures alone, and the &lt;a href="https://techfuelhq.com/data/coil-whine-database/">database&lt;/a> holds what other owners have reported by ear.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;p>Checked November 17, 2026.&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://www.we-online.com/components/products/media/861473" rel="noopener">Würth Elektronik, ANP118a: Acoustic noise &amp;amp; Coil whine effect&lt;/a>, Levi Mark and Theo Ritzmann, May 9, 2025. Hearing range, magnetostriction, forces on windings, burst mode and pulse skipping, resonance, checking against load.&lt;/li>
&lt;li>&lt;a href="https://product.tdk.com/en/techlibrary/solutionguide/acoustic-noise.html" rel="noopener">TDK Product Center: Measures Against Acoustic Noise in Power Inductors&lt;/a>. Causes of vibration, switching frequency against the audible range, load changes.&lt;/li>
&lt;li>&lt;a href="https://pmc.ncbi.nlm.nih.gov/articles/PMC9147252/" rel="noopener">Covaci and Gontean, &amp;ldquo;Singing&amp;rdquo; Multilayer Ceramic Capacitors and Mitigation Methods: A Review&lt;/a>, &lt;em>Sensors&lt;/em> 22(10), 3869, 2022.&lt;/li>
&lt;li>&lt;a href="https://www.intel.com/content/www/us/en/support/articles/000093133/graphics.html" rel="noopener">Intel support article 000093133&lt;/a>, last reviewed December 3, 2024.&lt;/li>
&lt;li>&lt;a href="https://www.amd.com/en/products/software/adrenalin/frtc.html" rel="noopener">AMD: Frame Rate Target Control&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://www.asus.com/us/support/faq/1050014/" rel="noopener">ASUS FAQ 1050014&lt;/a>, updated March 16, 2023.&lt;/li>
&lt;li>&lt;a href="https://us.msi.com/faq/10183" rel="noopener">MSI FAQ 10183&lt;/a>, updated April 26, 2024.&lt;/li>
&lt;li>&lt;a href="https://help.corsair.com/hc/en-us/articles/19865055003021-PSU-What-is-coil-whine" rel="noopener">Corsair: What is coil whine?&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://source.android.com/docs/compatibility/15/android-15-cdd#542_capture_for_voice_recognition" rel="noopener">Android 15 Compatibility Definition, section 5.4.2&lt;/a>. Microphone response and gain requirements for the voice-recognition source.&lt;/li>
&lt;li>MDN: &lt;a href="https://developer.mozilla.org/en-US/docs/Web/API/AnalyserNode/getFloatFrequencyData" rel="noopener">AnalyserNode frequency data&lt;/a>, &lt;a href="https://developer.mozilla.org/en-US/docs/Web/API/BaseAudioContext/decodeAudioData" rel="noopener">decodeAudioData&lt;/a>, &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy/microphone" rel="noopener">Permissions-Policy: microphone&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://techfuelhq.com/data/coil-whine-database/">TechFuelHQ coil whine database&lt;/a>, dataset 0.2.2.&lt;/li>
&lt;/ul></description></item><item><title>The 16 GB Cliff: Measured LLM Memory and Speed on an RTX 5080</title><link>https://techfuelhq.com/data/rtx-5080-16gb-vram-cliff/</link><pubDate>Tue, 17 Nov 2026 17:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/data/rtx-5080-16gb-vram-cliff/</guid><atom:updated>2026-11-17T17:00:00Z</atom:updated><description>&lt;h2 id="the-map">The map&lt;/h2>
&lt;p>Every pin is a local language model I ran on my own retail RTX 5080, placed by the memory in use on the whole card and the decode speed that came with it. Nothing here is estimated. For a card I do not own or a setup I have not run, the &lt;a href="https://techfuelhq.com/tools/llm-vram-calculator/">LLM VRAM calculator&lt;/a> and the &lt;a href="https://techfuelhq.com/tools/llm-speed-calculator/">LLM speed calculator&lt;/a> estimate, and the &lt;a href="https://techfuelhq.com/articles/local-llm-by-gpu-vram-2026/">VRAM tiers guide&lt;/a> covers other card sizes. This page only reports.&lt;/p>
&lt;style data-tfhq="vram-cliff">.vc{--vc-m:var(--viz-measured, var(--cyan));--vc-c:var(--copper);--vc-hatch:repeating-linear-gradient(-45deg, color-mix(in srgb, var(--vc-c) 62%, transparent) 0 2px, transparent 2px 6px);--vc-hatch-soft:repeating-linear-gradient(-45deg, color-mix(in srgb, var(--vc-c) 11%, transparent) 0 2px, transparent 2px 8px);--vc-plot-h:250px;container-type:inline-size;container-name:vc;margin:var(--space-9)0;font-family:var(--font-text);font-size:var(--size-ui);line-height:var(--lh-dense);color:var(--text-body)}.vc.vc--part{margin:var(--space-7)0 var(--space-9)}.vc *,.vc *::before,.vc *::after{box-sizing:border-box}.vc p,.vc ul,.vc ol,.vc dl,.vc dt,.vc dd,.vc li{margin:0;padding:0;max-width:none}.vc ul,.vc ol{list-style:none}.vc [hidden]{display:none!important}.vc a{color:var(--cyan);text-decoration:underline;text-underline-offset:2px}.vc a:hover{color:var(--cyan-hover)}.vc code{font-family:var(--font-mono);font-size:var(--size-meta);padding:0;border:0;background:0 0;color:inherit}.vc time{white-space:nowrap}.vc :focus-visible{outline:var(--focus-w)solid var(--focus-color);outline-offset:var(--focus-offset-control)}.vc .vc-sr{position:absolute;width:1px;height:1px;margin:-1px;overflow:hidden;clip:rect(0 0 0 0);white-space:nowrap}.vc .vc-dim{color:var(--muted);font-family:var(--font-text);font-weight:var(--w-text)}.vc .vc-m{font-family:var(--font-mono);font-variant-numeric:tabular-nums lining-nums;font-weight:600;color:var(--text);border-bottom:2px solid var(--vc-m)}.vc .vc-c{font-family:var(--font-mono);font-variant-numeric:tabular-nums lining-nums;font-weight:600;color:var(--text);border-bottom:2px dashed var(--vc-c)}.vc .vc-formula{display:inline-block;font-family:var(--font-mono);font-size:var(--size-meta);font-weight:var(--w-text);color:var(--vc-c)}.vc .vc-key{display:flex;flex-wrap:wrap;gap:var(--space-4)var(--space-10);margin-bottom:var(--space-7);font-size:var(--size-meta);color:var(--text-body)}.vc .vc-key__item{display:flex;align-items:center;gap:var(--space-5)}.vc .vc-key__item strong{color:var(--text)}.vc .vc-key__swatch{flex:none;width:28px;height:14px;border-radius:2px}.vc .vc-key__item--m .vc-key__swatch{background:var(--vc-m)}.vc .vc-key__item--c .vc-key__swatch{border:1px dashed var(--vc-c);background:var(--vc-hatch)}.vc .vc-panel{min-width:0;border:var(--rule-w)solid var(--rule-strong);border-top:var(--rule-w-heavy)solid var(--cat-ai);border-radius:var(--radius-md);background:var(--bg-bay)}.vc .vc-panel__head{display:flex;flex-wrap:wrap;align-items:baseline;justify-content:space-between;gap:var(--space-2)var(--space-8);padding:var(--space-5)var(--space-7);border-bottom:var(--rule-w)solid var(--rule)}.vc .vc-panel__title{font-family:var(--font-display);font-size:var(--size-ui);font-weight:var(--w-title);letter-spacing:.01em;color:var(--text)}.vc .vc-panel__meta{font-size:var(--size-meta);color:var(--muted)}.vc .vc-btn{display:inline-flex;align-items:center;justify-content:center;min-height:44px;padding:var(--space-3)var(--space-7);border:var(--rule-w)solid var(--rule-strong);border-radius:var(--radius);background:var(--bg-plate);color:var(--text);font-family:var(--font-text);font-size:var(--size-meta);font-weight:var(--w-ui);line-height:var(--lh-control);text-decoration:none;cursor:pointer}.vc .vc-btn:hover{border-color:var(--edge-hover);color:var(--text)}.vc .vc-controls{margin-bottom:var(--space-7);padding:var(--space-6)var(--space-7);border:var(--rule-w)solid var(--rule-strong);border-radius:var(--radius-md);background:var(--bg-raised)}.vc .vc-controls__fields{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:var(--space-5)var(--space-6)}.vc .vc-field-ctl,.vc .vc-sort{display:flex;flex-direction:column;gap:var(--space-2);min-width:0}.vc .vc-field-ctl__label{font-size:var(--size-meta);font-weight:600;letter-spacing:.04em;text-transform:uppercase;color:var(--muted)}.vc select{width:100%;min-height:44px;padding:var(--space-3)var(--space-5);border:var(--rule-w)solid var(--rule-strong);border-radius:var(--radius);background-color:var(--bg-inset);color:var(--text);font-family:var(--font-text);font-size:var(--size-ui)}.vc .vc-controls__foot{display:flex;flex-wrap:wrap;align-items:center;gap:var(--space-4)var(--space-6);margin-top:var(--space-5)}.vc .vc-count{flex:1 1 100%;font-family:var(--font-mono);font-size:var(--size-meta);font-variant-numeric:tabular-nums lining-nums;color:var(--text-body)}.vc .vc-count strong{color:var(--text)}.vc .vc-bench{display:grid;grid-template-columns:minmax(0,1fr);gap:var(--space-7);margin-bottom:var(--space-7)}.vc .vc-map{display:grid;grid-template-columns:42px minmax(0,1fr);grid-template-rows:var(--vc-plot-h)auto auto;padding:28px 26px 0 var(--space-4)}.vc .vc-map__yaxis{position:relative;grid-column:1;grid-row:1}.vc .vc-map__ytick,.vc .vc-map__xtick,.vc .vc-map__ytitle,.vc .vc-map__xtitle,.vc .vc-map__walllabel{font-family:var(--font-mono);font-size:var(--size-meta);font-variant-numeric:tabular-nums lining-nums;line-height:1;color:var(--muted);white-space:nowrap}.vc .vc-map__ytick{position:absolute;right:var(--space-4);bottom:calc(var(--vc-y) * 1%);transform:translateY(50%)}.vc .vc-map__ytitle{position:absolute;right:var(--space-4);top:-24px}.vc .vc-map__plot{position:relative;grid-column:2;grid-row:1;border-left:var(--rule-w)solid var(--viz-axis);background:var(--viz-ground);cursor:crosshair;touch-action:manipulation}.vc:not([data-vc-js]) .vc-map__plot{cursor:default}.vc .vc-map__grid{position:absolute;left:0;right:0;bottom:calc(var(--vc-y) * 1%);border-top:var(--rule-w)solid var(--viz-grid)}.vc .vc-map__links{position:absolute;inset:0;width:100%;height:100%;overflow:visible;pointer-events:none}.vc .vc-link{fill:none;stroke:var(--vc-m);stroke-width:1.5px;stroke-dasharray:5 4;opacity:.8}.vc .vc-link.is-out{opacity:.12}.vc .vc-link.is-selected{stroke:var(--accent);opacity:1}.vc .vc-pin{position:absolute;left:calc(var(--vc-x) * 1%);bottom:0;width:0;height:calc(var(--vc-y) * 1%);border-left:var(--rule-w)solid color-mix(in srgb,var(--vc-m) 50%,transparent);pointer-events:none}.vc .vc-pin::after{content:"";position:absolute;left:-5px;top:-5px;width:9px;height:9px;border:var(--rule-w)solid var(--viz-ground);border-radius:50%;background:var(--vc-m)}.vc .vc-pin--spill::after{border:2px solid var(--vc-m);background:var(--viz-ground)}.vc .vc-pin--shared::after{border:2px solid var(--edge-hover);border-radius:0;background:var(--viz-ground);transform:rotate(45deg)}.vc .vc-pin--shared{border-left-style:dotted;border-left-color:var(--edge)}.vc .vc-pin.is-out{opacity:.13}.vc .vc-pin.is-hover{z-index:2;border-left-color:var(--text)}.vc .vc-pin.is-hover::after{box-shadow:0 0 0 3px color-mix(in srgb,var(--text) 35%,transparent)}.vc .vc-pin.is-selected{z-index:3;border-left:2px solid var(--accent);opacity:1}.vc .vc-pin.is-selected::after{left:-7px;top:-6px;width:12px;height:12px;border-color:var(--accent);box-shadow:0 0 0 3px color-mix(in srgb,var(--accent) 35%,transparent)}.vc .vc-map__wall{position:absolute;top:-14px;right:-2px;bottom:-19px;width:0;border-right:2px solid var(--text);pointer-events:none}.vc .vc-map__wall::after{content:"";position:absolute;left:2px;top:0;bottom:0;width:14px;background:repeating-linear-gradient(-45deg,var(--edge) 0 1px,transparent 1px 5px)}.vc .vc-map__call{display:none;position:absolute;left:calc(var(--vc-x) * 1% + 12px);bottom:calc(var(--vc-y) * 1% + 7px);padding:var(--space-2)var(--space-4);border-left:2px solid var(--vc-m);background:color-mix(in srgb,var(--viz-ground) 88%,transparent);font-size:var(--size-meta);line-height:var(--lh-meta);color:var(--text);pointer-events:none}.vc .vc-map__call>span{display:block;white-space:nowrap}.vc .vc-map__call.is-out{visibility:hidden}.vc .vc-map__tip{position:absolute;z-index:5;max-width:min(280px,78%);padding:var(--space-3)var(--space-4);border:var(--rule-w)solid var(--rule-strong);border-radius:var(--radius);background:var(--bg-plate);box-shadow:var(--shadow-elevated);font-size:var(--size-meta);line-height:var(--lh-meta);color:var(--text);pointer-events:none}.vc .vc-map__rail{--vc-sel:0;position:relative;grid-column:2;grid-row:2;height:18px;border:var(--rule-w)solid var(--viz-axis);border-right:0;background:var(--bg-inset)}.vc .vc-map__railfill{position:absolute;left:0;top:0;bottom:0;width:calc(var(--vc-sel) * 1%);background:var(--vc-m);transition:width .22s ease}.vc .vc-map__railrest{position:absolute;left:calc(var(--vc-sel) * 1%);right:0;top:0;bottom:0;background:var(--vc-hatch);opacity:0;transition:left .22s ease,opacity .22s ease}.vc .vc-map__rail.has-sel .vc-map__railrest{opacity:1}.vc .vc-map__xaxis{position:relative;grid-column:2;grid-row:3;height:50px}.vc .vc-map__xtick{position:absolute;left:calc(var(--vc-x) * 1%);top:var(--space-4);transform:translateX(-50%)}.vc .vc-map__xtick--wall{color:var(--text);font-weight:600}.vc .vc-map__xtitle{position:absolute;left:0;right:0;top:28px;text-align:center}.vc .vc-map__walllabel{position:absolute;right:-26px;top:28px;color:var(--text);font-weight:600}.vc .vc-map__sel{padding:0 var(--space-7)var(--space-4);font-size:var(--size-meta);line-height:var(--lh-text);color:var(--text-body)}.vc .vc-glyphs{display:flex;flex-wrap:wrap;gap:var(--space-3)var(--space-9);padding:var(--space-4)var(--space-7);border-top:var(--rule-w)solid var(--rule);font-size:var(--size-meta);color:var(--text-body)}.vc .vc-glyphs li{display:flex;align-items:center}.vc .vc-glyph{flex:none;display:inline-block;width:10px;height:10px;margin-right:var(--space-4)}.vc .vc-glyph--whole{border-radius:50%;background:var(--vc-m)}.vc .vc-glyph--spill{border:2px solid var(--vc-m);border-radius:50%}.vc .vc-glyph--shared{width:9px;height:9px;border:2px solid var(--edge-hover);transform:rotate(45deg)}.vc .vc-glyph--link{width:20px;height:0;border-top:2px dashed var(--vc-m)}.vc .vc-map__note{padding:0 var(--space-7)var(--space-6);font-size:var(--size-meta);color:var(--muted)}.vc .vc-readout{padding:var(--space-6)var(--space-7)var(--space-7)}.vc .vc-idle__lead{margin-bottom:var(--space-5);font-size:var(--size-ui);color:var(--text-body)}.vc .vc-tally{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:0 var(--space-8);margin-top:var(--space-6);border-top:var(--rule-w)solid var(--rule)}.vc .vc-tally>div{display:flex;align-items:baseline;justify-content:space-between;gap:var(--space-5);padding:var(--space-3)0;border-bottom:var(--rule-w)solid var(--rule);font-size:var(--size-meta)}.vc .vc-tally dt{color:var(--muted)}.vc .vc-tally dd{font-family:var(--font-mono);font-size:var(--size-ui);font-weight:600;font-variant-numeric:tabular-nums lining-nums;color:var(--text)}.vc .vc-idle__foot{margin-top:var(--space-6);font-size:var(--size-meta);line-height:var(--lh-text);color:var(--text-body)}.vc .vc-record__title{font-family:var(--font-mono);font-size:var(--size-body);line-height:var(--lh-title);color:var(--text);overflow-wrap:anywhere}.vc .vc-record__spec{display:block;margin-top:var(--space-1);font-family:var(--font-text);font-size:var(--size-meta);color:var(--muted)}.vc .vc-record__sentence{margin-top:var(--space-4);font-size:var(--size-ui);line-height:var(--lh-text);color:var(--text)}.vc .vc-flag{margin-top:var(--space-4)}.vc .vc-flag__label{display:inline-block;padding:var(--space-1)var(--space-4);border:var(--rule-w)solid var(--edge-hover);border-radius:var(--radius);background:var(--bg-plate);font-size:var(--size-meta);font-weight:600;color:var(--text)}.vc .vc-flag--spill .vc-flag__label{border-color:var(--cat-diag)}.vc .vc-note{margin-top:var(--space-4);padding-left:var(--space-5);border-left:2px solid var(--rule-strong);font-size:var(--size-meta);line-height:var(--lh-text);color:var(--text-body)}.vc .vc-gauge{position:relative;height:14px;margin-top:var(--space-6);border:var(--rule-w)solid var(--viz-axis);border-right:2px solid var(--text);background:var(--bg-inset)}.vc .vc-gauge__fill{position:absolute;left:0;top:0;bottom:0;width:var(--vc-w);background:var(--vc-m)}.vc .vc-gauge__rest{position:absolute;left:var(--vc-w);right:0;top:0;bottom:0;background:var(--vc-hatch)}.vc .vc-kpis{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:var(--space-4);margin-top:var(--space-4)}.vc .vc-kpi{min-width:0;padding:var(--space-4)var(--space-5);border:var(--rule-w)solid var(--rule-strong);border-radius:var(--radius);background:var(--bg-raised)}.vc .vc-kpi--wide{grid-column:1/-1}.vc .vc-kpi--m{border-left:3px solid var(--vc-m)}.vc .vc-kpi--c{border:var(--rule-w)dashed var(--vc-c);background:var(--vc-hatch-soft),var(--bg-raised)}.vc .vc-kpi dt{font-size:var(--size-meta);font-weight:600;letter-spacing:.03em;text-transform:uppercase;color:var(--muted)}.vc .vc-kpi__v{margin:var(--space-1)0;font-family:var(--font-mono);font-size:1.5rem;font-weight:600;font-variant-numeric:tabular-nums lining-nums;line-height:1.15;color:var(--text)}@container vc (max-width:619.98px){.vc .vc-kpi__v { font-size: 1.375rem; } }@container vc (max-width:339.98px){.vc .vc-row__mem { grid-template-columns: auto; justify-content: end; }
.vc .vc-row .vc-bar { display: none; }
}.vc .vc-kpi__v small{font-size:var(--size-meta);font-weight:var(--w-text);color:var(--muted)}.vc .vc-kpi__v--date{font-size:var(--size-body);line-height:var(--lh-title)}.vc .vc-kpi__tag{font-family:var(--font-mono);font-size:var(--size-meta);line-height:var(--lh-meta);color:var(--text-body)}.vc .vc-kpi__tag span{white-space:nowrap}.vc .vc-kpi--m .vc-kpi__tag{color:var(--vc-m)}.vc .vc-kpi--c .vc-kpi__tag{color:var(--vc-c)}.vc .vc-record__full{margin-top:var(--space-7)}.vc .vc-record__sub{margin-bottom:var(--space-3);font-size:var(--size-meta);font-weight:600;letter-spacing:.04em;text-transform:uppercase;color:var(--muted)}.vc .vc-fields{border-top:var(--rule-w)solid var(--rule)}.vc .vc-field{display:grid;grid-template-columns:minmax(0,44%)minmax(0,1fr);gap:var(--space-1)var(--space-6);padding:var(--space-3)0;border-bottom:var(--rule-w)solid var(--rule);font-size:var(--size-meta);line-height:var(--lh-meta)}.vc .vc-field dt{color:var(--muted)}.vc .vc-field dd{font-family:var(--font-mono);font-variant-numeric:tabular-nums lining-nums;color:var(--text);overflow-wrap:anywhere}.vc .vc-field--head{padding-inline:var(--space-4);background:var(--bg-plate)}.vc .vc-field--head dt{font-weight:600;color:var(--text)}.vc .vc-field--head dd,.vc .vc-field--na dd{font-family:var(--font-text);color:var(--text-body)}.vc .vc-field--c{border-bottom-style:dashed;border-bottom-color:var(--vc-c);background:var(--vc-hatch-soft);padding-inline:var(--space-4)}.vc .vc-energy-note{margin-top:var(--space-7);font-size:var(--size-meta);line-height:var(--lh-text);color:var(--text-body)}.vc .vc-record__src{margin-top:var(--space-6);font-size:var(--size-meta);line-height:var(--lh-text);color:var(--text-body)}.vc .vc-record__actions{display:flex;flex-wrap:wrap;gap:var(--space-4);margin-top:var(--space-6)}.vc .vc-row .vc-record__jump{display:none}.vc .vc-sort{flex-direction:row;align-items:center;gap:var(--space-4)}.vc .vc-sort select{width:auto;min-width:190px}.vc .vc-list__cols{display:none}.vc .vc-row{border-bottom:var(--rule-w)solid var(--rule);scroll-margin-top:calc(var(--v3-masthead-h,96px) + var(--v3-anchor-gap,18px))}.vc .vc-row:last-child{border-bottom:0}.vc .vc-row__pick{display:grid;grid-template-columns:auto minmax(0,1fr)auto;grid-template-areas:"model model tps" "spec mem mem" "rt rt date";gap:var(--space-1)var(--space-6);align-items:center;min-height:44px;padding:var(--space-4)var(--space-7);color:var(--text-body);font-size:var(--size-meta);text-decoration:none}.vc .vc-row__pick:hover{background:var(--bg-raised);color:var(--text-body)}.vc .vc-row__model{grid-area:model;display:flex;flex-wrap:wrap;align-items:center;gap:var(--space-2)0;min-width:0}.vc .vc-row__name{font-family:var(--font-mono);font-size:var(--size-ui);font-weight:600;color:var(--text);overflow-wrap:anywhere}.vc .vc-row__flag{margin-left:var(--space-4);padding:0 var(--space-3);border:var(--rule-w)solid var(--edge-hover);border-radius:var(--radius);font-size:var(--size-meta);color:var(--text)}.vc .vc-row__spec{grid-area:spec}.vc .vc-row__rt{grid-area:rt}.vc .vc-row__date{grid-area:date;text-align:right}.vc .vc-row__mem{grid-area:mem;display:grid;grid-template-columns:minmax(40px,1fr)auto;gap:var(--space-5);align-items:center;min-width:0}.vc .vc-row__tps{grid-area:tps;text-align:right}.vc .vc-row__num,.vc .vc-row__tps,.vc .vc-row__date,.vc .vc-row__spec{font-family:var(--font-mono);font-variant-numeric:tabular-nums lining-nums;white-space:nowrap}.vc .vc-row__num b,.vc .vc-row__tps b{font-weight:600;color:var(--text);border-bottom:var(--rule-w)solid var(--vc-m)}.vc .vc-bar{position:relative;display:block;height:8px;border:var(--rule-w)solid var(--rule-strong);border-right:2px solid var(--text);background:var(--bg-inset)}.vc .vc-bar__fill{position:absolute;left:0;top:0;bottom:0;width:var(--vc-w);background:var(--vc-m)}.vc .vc-row.is-selected,.vc:not([data-vc-js]) .vc-row:target{background:var(--bg-raised);box-shadow:inset 3px 0 0 var(--accent)}.vc .vc-row__copy{display:none}.vc .vc-row__more{padding:0 var(--space-7)}.vc .vc-row__more>summary{display:flex;align-items:center;min-height:44px;font-size:var(--size-meta);color:var(--cyan);cursor:pointer}.vc .vc-row__more[open]{padding-bottom:var(--space-7)}.vc[data-vc-js] .vc-row__more>summary{display:none}.vc[data-vc-js] .vc-row__more[open]{padding-top:var(--space-2);border-top:var(--rule-w)dashed var(--rule-strong)}.vc .vc-row__pick::after{content:none}.vc[data-vc-js] .vc-row__pick[aria-expanded] .vc-row__name::after{content:"+";display:inline-block;width:1.2em;margin-left:var(--space-3);font-weight:400;color:var(--muted);text-align:center}.vc[data-vc-js] .vc-row__pick[aria-expanded=true] .vc-row__name::after{content:"−"}.vc .vc-row__more .vc-record{max-width:760px}.vc .vc-empty{padding:var(--space-8)var(--space-7);font-size:var(--size-ui);color:var(--text)}.vc .vc-tablenote{margin-bottom:var(--space-4);font-size:var(--size-meta);line-height:var(--lh-text);color:var(--text-body)}.vc .vc-rows{margin-bottom:var(--space-8);border:var(--rule-w)solid var(--rule-strong);border-radius:var(--radius-md);background:var(--bg-bay);font-size:var(--size-meta);line-height:var(--lh-meta)}.vc .vc-rows__head{position:absolute;width:1px;height:1px;margin:-1px;overflow:hidden;clip:rect(0 0 0 0);white-space:nowrap}.vc .vc-rows__row{display:grid;grid-template-columns:minmax(0,1fr);gap:var(--space-2);padding:var(--space-5)var(--space-7);border-bottom:var(--rule-w)solid var(--rule);color:var(--text)}.vc .vc-rows__row:last-child{border-bottom:0}.vc .vc-rows__lead{font-family:var(--font-mono);font-size:var(--size-ui);color:var(--text);overflow-wrap:anywhere}.vc .vc-rows__sub{display:block;font-family:var(--font-text);font-size:var(--size-meta);font-weight:var(--w-text);color:var(--muted)}.vc .vc-rows__sub--flag{color:var(--text-body)}.vc .vc-rows__row>[role=cell]{display:grid;grid-template-columns:minmax(0,38%)minmax(0,1fr);gap:var(--space-5);align-items:baseline;font-variant-numeric:tabular-nums lining-nums}.vc .vc-rows__row>[role=cell]::before{content:attr(data-label);content:attr(data-label)/"";color:var(--muted)}.vc .vc-rows__row>[role=cell]>span{min-width:0;overflow-wrap:anywhere}.vc .vc-fall{display:inline-block;position:relative;width:52px;height:10px;margin-left:var(--space-5);border:var(--rule-w)solid var(--rule-strong);background:var(--bg-inset);vertical-align:middle}.vc .vc-fall__fill{position:absolute;left:0;top:0;bottom:0;width:var(--vc-w);border-right:var(--rule-w)dashed var(--vc-c);background:var(--vc-hatch)}.vc .vc-energy{display:grid;grid-template-columns:minmax(0,1fr);gap:var(--space-5)}.vc .vc-energy__row{padding:var(--space-6)var(--space-7);border:var(--rule-w)solid var(--rule-strong);border-radius:var(--radius-md);background:var(--bg-bay)}.vc .vc-energy__name{font-family:var(--font-mono);font-size:var(--size-ui);color:var(--text)}.vc .vc-energy__lead{display:grid;grid-template-columns:minmax(0,1fr);gap:var(--space-3);margin:var(--space-4)0 var(--space-5)}.vc .vc-energy__bar{position:relative;display:block;height:14px;border:var(--rule-w)solid var(--rule-strong);background:var(--bg-inset)}.vc .vc-energy__fill{position:absolute;left:0;top:0;bottom:0;width:var(--vc-w);border-right:var(--rule-w)dashed var(--vc-c);background:var(--vc-hatch)}.vc .vc-energy__main{font-size:var(--size-ui);color:var(--text)}.vc .vc-energy__main b{font-size:var(--size-lead)}.vc .vc-energy__facts{display:grid;grid-template-columns:minmax(0,1fr);border-top:var(--rule-w)solid var(--rule);font-size:var(--size-meta);line-height:var(--lh-meta)}.vc .vc-energy__facts>div{display:flex;flex-wrap:wrap;align-items:baseline;justify-content:space-between;gap:var(--space-1)var(--space-6);padding:var(--space-3)0;border-bottom:var(--rule-w)solid var(--rule)}.vc .vc-energy__facts dt{color:var(--muted)}.vc .vc-energy__facts dd{font-family:var(--font-mono);color:var(--text);text-align:right}.vc .vc-energy__more>summary{display:flex;align-items:center;min-height:44px;font-size:var(--size-meta);color:var(--cyan);cursor:pointer}.vc .vc-energy__more[open]>summary{margin-bottom:var(--space-2)}.vc .vc-cover{border:var(--rule-w)solid var(--rule-strong);border-radius:var(--radius-md);background:var(--bg-bay)}.vc .vc-cover__row{display:grid;grid-template-columns:minmax(0,1fr);gap:var(--space-3);padding:var(--space-5)var(--space-7);border-bottom:var(--rule-w)solid var(--rule)}.vc .vc-cover__row:last-child{border-bottom:0}.vc .vc-cover dt{font-size:var(--size-meta);font-weight:600;letter-spacing:.04em;text-transform:uppercase;color:var(--text)}.vc .vc-chips{display:flex;flex-wrap:wrap;gap:var(--space-3)}.vc .vc-chips li{padding:var(--space-1)var(--space-4);border:var(--rule-w)solid var(--rule-strong);border-radius:var(--radius);background:var(--bg-raised);font-family:var(--font-mono);font-size:var(--size-meta);color:var(--text-body)}.vc .vc-chips strong{color:var(--text)}.vc .vc-cover__note{margin-top:var(--space-4);font-size:var(--size-meta);color:var(--text-body)}.vc .vc-files{display:grid;gap:var(--space-5)}.vc .vc-files li{display:grid;grid-template-columns:minmax(0,1fr);gap:var(--space-3);padding-bottom:var(--space-5);border-bottom:var(--rule-w)solid var(--rule);font-size:var(--size-meta);line-height:var(--lh-text);color:var(--text-body)}.vc .vc-files li:last-child{border-bottom:0}.vc .vc-files .vc-btn{justify-self:start;font-family:var(--font-mono);overflow-wrap:anywhere;text-align:left}@container vc (min-width:620px){.vc { --vc-plot-h: 320px; }
.vc .vc-controls__fields { grid-template-columns: repeat(4, minmax(0, 1fr)); }
.vc .vc-count { flex: 1 1 auto; }
.vc .vc-map { grid-template-columns: 46px minmax(0, 1fr); padding-right: 30px; }
.vc .vc-map__call { display: block; }
.vc .vc-btn { min-height: 36px; }
.vc select { min-height: 40px; }
.vc .vc-energy__facts { grid-template-columns: repeat(4, minmax(0, 1fr)); column-gap: var(--space-8); }
.vc .vc-energy__facts > div { display: block; padding: var(--space-4) 0; }
.vc .vc-energy__facts dd { margin-top: var(--space-1); text-align: left; }
.vc .vc-energy__more > summary { min-height: 34px; }
.vc .vc-energy__lead { grid-template-columns: minmax(0, 1fr) minmax(0, 1fr); align-items: center; gap: var(--space-8); }
.vc .vc-cover__row { grid-template-columns: 190px minmax(0, 1fr); gap: var(--space-8); }
.vc .vc-files li { grid-template-columns: minmax(0, 340px) minmax(0, 1fr); gap: var(--space-8); align-items: center; }
}@container vc (min-width:820px){.vc .vc-rows__head,
.vc .vc-rows__row { display: grid; grid-template-columns: var(--vc-cols); gap: var(--space-2) var(--space-8); align-items: baseline; padding: var(--space-4) var(--space-7); }
.vc .vc-rows__head { position: static; width: auto; height: auto; margin: 0; overflow: visible; clip: auto; white-space: normal; border-bottom: var(--rule-w) solid var(--rule-strong); background: var(--bg-raised); border-radius: var(--radius-md) var(--radius-md) 0 0; font-weight: 600; letter-spacing: 0.03em; text-transform: uppercase; color: var(--muted); }
.vc .vc-rows__row > [role="cell"] { display: block; }
.vc .vc-rows__row > [role="cell"]::before { content: none; }
.vc .vc-rows--pairs { --vc-cols: minmax(0, 1.55fr) minmax(0, 0.95fr) minmax(0, 1.05fr) minmax(0, 0.8fr) minmax(0, 0.95fr) minmax(0, 1.1fr); }
.vc .vc-rows--versions { --vc-cols: 108px minmax(0, 1.5fr) minmax(0, 0.9fr) minmax(0, 1.9fr) minmax(0, 0.8fr); }
.vc .vc-rows--drift { --vc-cols: minmax(0, 1fr) minmax(0, 1.5fr) minmax(0, 1.5fr) minmax(0, 0.9fr); }
}@container vc (min-width:1080px){.vc .vc-list__cols,
.vc .vc-row__pick {
display: grid;
grid-template-columns: minmax(0, 1.45fr) minmax(0, 1.25fr) minmax(0, 1fr) minmax(0, 1.5fr) 104px 98px;
grid-template-areas: none;
gap: var(--space-2) var(--space-7);
align-items: center;
}
.vc .vc-list__cols {
padding: var(--space-4) var(--space-7);
border-bottom: var(--rule-w) solid var(--rule);
font-size: var(--size-meta);
font-weight: 600;
letter-spacing: 0.03em;
text-transform: uppercase;
color: var(--muted);
}
.vc .vc-list__cols span:nth-child(5), .vc .vc-list__cols span:nth-child(6) { text-align: right; }
.vc[data-vc-js] .vc-row { display: grid; grid-template-columns: minmax(0, 1fr) 96px; align-items: center; }
.vc[data-vc-js] .vc-row__copy { display: inline-flex; min-height: 32px; margin-right: var(--space-7); padding-inline: var(--space-4); white-space: nowrap; }
.vc[data-vc-js] .vc-row__pick { padding-right: var(--space-5); }
.vc[data-vc-js] .vc-row__more { grid-column: 1 / -1; }
.vc[data-vc-js] .vc-list__cols { grid-template-columns: minmax(0, 1.45fr) minmax(0, 1.25fr) minmax(0, 1fr) minmax(0, 1.5fr) 104px 98px 82px; padding-right: var(--space-7); }
.vc[data-vc-js] .vc-list__cols { column-gap: var(--space-7); }
.vc .vc-row__pick { padding-block: var(--space-4); }
.vc .vc-row__model, .vc .vc-row__spec, .vc .vc-row__rt, .vc .vc-row__mem, .vc .vc-row__tps, .vc .vc-row__date { grid-area: auto; }
.vc .vc-row__mem { grid-template-columns: minmax(60px, 1fr) 92px; }
.vc .vc-row__num { text-align: right; }
.vc .vc-row__more > summary { min-height: 32px; }
.vc .vc-row__more .vc-fields { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); column-gap: var(--space-9); }
.vc .vc-row__more .vc-field--head { grid-column: 1 / -1; }
}@container vc (min-width:980px){.vc { --vc-plot-h: 360px; }
.vc[data-vc-js] .vc-controls { position: sticky; top: var(--v3-masthead-h, 94px); z-index: 4; box-shadow: var(--shadow-elevated); }
.vc[data-vc-js] .vc-row { scroll-margin-top: calc(var(--v3-masthead-h, 94px) + 168px); }
.vc .vc-bench { grid-template-columns: minmax(0, 1.6fr) minmax(360px, 1fr); align-items: stretch; }
.vc .vc-panel--readout { display: flex; flex-direction: column; }
.vc .vc-readout {
flex: 1 1 0;
min-height: 420px;
max-height: 640px;
overflow: auto;
overscroll-behavior: contain;
background:
linear-gradient(var(--bg-bay), var(--bg-bay)) top / 100% 10px no-repeat local,
linear-gradient(var(--bg-bay), var(--bg-bay)) bottom / 100% 10px no-repeat local,
linear-gradient(var(--rule-strong), var(--rule-strong)) top / 100% 3px no-repeat scroll,
linear-gradient(var(--edge), var(--edge)) bottom / 100% 3px no-repeat scroll;
}
}@container vc (max-width:979.98px){.vc .vc-readout .vc-record__full { display: none; }
}@media(prefers-reduced-motion:reduce){.vc .vc-map__railfill,.vc .vc-map__railrest{transition:none}}&lt;/style>
&lt;div class="vc" data-vc data-vc-total="16303" data-vc-total-label="16,303">
&lt;ul class="vc-key" aria-label="How to read the two kinds of value">
&lt;li class="vc-key__item vc-key__item--m">&lt;span class="vc-key__swatch" aria-hidden="true">&lt;/span>&lt;span>&lt;strong>Measured.&lt;/strong> Copied from a capture file, shown with its capture date.&lt;/span>&lt;/li>
&lt;li class="vc-key__item vc-key__item--c">&lt;span class="vc-key__swatch" aria-hidden="true">&lt;/span>&lt;span>&lt;strong>Computed.&lt;/strong> Arithmetic on measured values, shown with its formula.&lt;/span>&lt;/li>
&lt;/ul>
&lt;div class="vc-controls" data-vc-controls hidden>
&lt;div class="vc-controls__fields">
&lt;label class="vc-field-ctl">&lt;span class="vc-field-ctl__label">Model&lt;/span>
&lt;select data-vc-facet="model" data-vc-all="All models">
&lt;option value="">All models (36)&lt;/option>
&lt;option value="llama323b" data-vc-label="llama3.2:3b · 3.2B">llama3.2:3b · 3.2B (9)&lt;/option>
&lt;option value="qwen25coder7b" data-vc-label="qwen2.5-coder:7b · 7.6B">qwen2.5-coder:7b · 7.6B (2)&lt;/option>
&lt;option value="qwen257b" data-vc-label="qwen2.5:7b · 7.6B">qwen2.5:7b · 7.6B (2)&lt;/option>
&lt;option value="qwen25coder14b" data-vc-label="qwen2.5-coder:14b · 14.8B">qwen2.5-coder:14b · 14.8B (2)&lt;/option>
&lt;option value="qwen2514b" data-vc-label="qwen2.5:14b · 14.8B">qwen2.5:14b · 14.8B (8)&lt;/option>
&lt;option value="gptoss20b" data-vc-label="gpt-oss:20b · 20.9B">gpt-oss:20b · 20.9B (10)&lt;/option>
&lt;option value="devstral24b" data-vc-label="devstral:24b · 23.6B">devstral:24b · 23.6B (1)&lt;/option>
&lt;option value="qwen3coder30b" data-vc-label="qwen3-coder:30b · 30.5B">qwen3-coder:30b · 30.5B (2)&lt;/option>
&lt;/select>&lt;/label>
&lt;label class="vc-field-ctl">&lt;span class="vc-field-ctl__label">Quantization&lt;/span>
&lt;select data-vc-facet="quant" data-vc-all="All quantizations">
&lt;option value="">All quantizations (36)&lt;/option>
&lt;option value="MXFP4" data-vc-label="MXFP4">MXFP4 (10)&lt;/option>
&lt;option value="Q4_K_M" data-vc-label="Q4_K_M">Q4_K_M (26)&lt;/option>
&lt;/select>&lt;/label>
&lt;label class="vc-field-ctl">&lt;span class="vc-field-ctl__label">Context length&lt;/span>
&lt;select data-vc-facet="ctx" data-vc-all="All contexts">
&lt;option value="">All contexts (36)&lt;/option>
&lt;option value="4096" data-vc-label="4,096 tokens">4,096 tokens (24)&lt;/option>
&lt;option value="8192" data-vc-label="8,192 tokens">8,192 tokens (3)&lt;/option>
&lt;option value="16384" data-vc-label="16,384 tokens">16,384 tokens (8)&lt;/option>
&lt;option value="131072" data-vc-label="131,072 tokens">131,072 tokens (1)&lt;/option>
&lt;/select>&lt;/label>
&lt;label class="vc-field-ctl">&lt;span class="vc-field-ctl__label">Runtime&lt;/span>
&lt;select data-vc-facet="runtime" data-vc-all="All runtimes">
&lt;option value="">All runtimes (36)&lt;/option>
&lt;option value="llama-cpp-b10507" data-vc-label="llama.cpp b10507">llama.cpp b10507 (3)&lt;/option>
&lt;option value="lm-studio-0-4-21" data-vc-label="LM Studio 0.4.21">LM Studio 0.4.21 (6)&lt;/option>
&lt;option value="ollama-0-32-1" data-vc-label="Ollama 0.32.1">Ollama 0.32.1 (20)&lt;/option>
&lt;option value="ollama-0-32-15" data-vc-label="Ollama 0.32.15">Ollama 0.32.15 (7)&lt;/option>
&lt;/select>&lt;/label>
&lt;/div>
&lt;div class="vc-controls__foot">
&lt;p class="vc-count" data-vc-count role="status">Showing &lt;strong>36&lt;/strong> of 36 measured configurations&lt;/p>
&lt;button type="button" class="vc-btn" data-vc-reset>Clear filters&lt;/button>
&lt;button type="button" class="vc-btn" data-vc-copy-view>Copy link to this view&lt;/button>
&lt;/div>
&lt;/div>
&lt;div class="vc-bench">
&lt;section class="vc-panel vc-panel--map" aria-label="Map of measured configurations">
&lt;div class="vc-panel__head">
&lt;p class="vc-panel__title">The map&lt;/p>
&lt;p class="vc-panel__meta">Across: memory in use on the whole card. Up: decode speed.&lt;/p>
&lt;/div>
&lt;div class="vc-map" data-vc-map aria-hidden="true">
&lt;div class="vc-map__yaxis">
&lt;span class="vc-map__ytitle">tok/s&lt;/span>
&lt;span class="vc-map__ytick" style="--vc-y:0.000">0&lt;/span>
&lt;span class="vc-map__ytick" style="--vc-y:25.000">100&lt;/span>
&lt;span class="vc-map__ytick" style="--vc-y:50.000">200&lt;/span>
&lt;span class="vc-map__ytick" style="--vc-y:75.000">300&lt;/span>
&lt;span class="vc-map__ytick" style="--vc-y:100.000">400&lt;/span>
&lt;/div>
&lt;div class="vc-map__plot" data-vc-plot>
&lt;span class="vc-map__grid" style="--vc-y:0.000">&lt;/span>
&lt;span class="vc-map__grid" style="--vc-y:25.000">&lt;/span>
&lt;span class="vc-map__grid" style="--vc-y:50.000">&lt;/span>
&lt;span class="vc-map__grid" style="--vc-y:75.000">&lt;/span>
&lt;span class="vc-map__grid" style="--vc-y:100.000">&lt;/span>
&lt;svg class="vc-map__links" viewBox="0 0 100 100" preserveAspectRatio="none" focusable="false" aria-hidden="true">
&lt;line class="vc-link" data-vc-link-a="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults" data-vc-link-b="sku-llama3-2-3b-q4-k-m-ctx131072-ollama-0-32-15-2026-08-26-defaults" x1="23.063" y1="12.195" x2="92.523" y2="74.330" vector-effect="non-scaling-stroke">&lt;/line>
&lt;line class="vc-link" data-vc-link-a="sku-qwen3-coder-30b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" data-vc-link-b="sku-qwen3-coder-30b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" x1="92.627" y1="84.527" x2="92.026" y2="87.095" vector-effect="non-scaling-stroke">&lt;/line>
&lt;line class="vc-link" data-vc-link-a="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-12" data-vc-link-b="sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-12" x1="86.285" y1="52.465" x2="88.051" y2="52.843" vector-effect="non-scaling-stroke">&lt;/line>
&lt;line class="vc-link" data-vc-link-a="sku-qwen2-5-coder-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" data-vc-link-b="sku-qwen2-5-coder-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" x1="62.375" y1="76.277" x2="76.581" y2="76.378" vector-effect="non-scaling-stroke">&lt;/line>
&lt;line class="vc-link" data-vc-link-a="sku-qwen2-5-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" data-vc-link-b="sku-qwen2-5-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" x1="37.968" y1="54.995" x2="43.072" y2="55.085" vector-effect="non-scaling-stroke">&lt;/line>
&lt;line class="vc-link" data-vc-link-a="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" data-vc-link-b="sku-qwen2-5-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" x1="66.497" y1="75.837" x2="80.703" y2="75.745" vector-effect="non-scaling-stroke">&lt;/line>
&lt;line class="vc-link" data-vc-link-a="sku-qwen2-5-coder-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" data-vc-link-b="sku-qwen2-5-coder-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" x1="34.785" y1="56.568" x2="39.888" y2="56.355" vector-effect="non-scaling-stroke">&lt;/line>
&lt;line class="vc-link" data-vc-link-a="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-26" data-vc-link-b="sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-26" x1="82.077" y1="54.625" x2="83.929" y2="54.250" vector-effect="non-scaling-stroke">&lt;/line>
&lt;/svg>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults" style="--vc-x:23.063;--vc-y:87.805">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-normalized" style="--vc-x:23.063;--vc-y:87.630">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-llama3-2-3b-q4-k-m-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" style="--vc-x:23.358;--vc-y:79.000">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-llama3-2-3b-q4-k-m-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" style="--vc-x:26.130;--vc-y:78.715">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-llama3-2-3b-q4-k-m-ctx4096-llama-cpp-b10507-2026-08-20" style="--vc-x:26.615;--vc-y:84.555">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20" style="--vc-x:26.639;--vc-y:79.627">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-llama3-2-3b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" style="--vc-x:33.705;--vc-y:78.222">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-coder-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" style="--vc-x:34.785;--vc-y:43.432">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" style="--vc-x:37.968;--vc-y:45.005">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-coder-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" style="--vc-x:39.888;--vc-y:43.645">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" style="--vc-x:43.072;--vc-y:44.915">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-coder-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" style="--vc-x:62.375;--vc-y:23.723">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults" style="--vc-x:63.522;--vc-y:25.562">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-normalized" style="--vc-x:63.522;--vc-y:25.552">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-14b-q4-k-m-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" style="--vc-x:63.823;--vc-y:24.407">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" style="--vc-x:66.497;--vc-y:24.163">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20" style="--vc-x:67.110;--vc-y:24.858">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-14b-q4-k-m-ctx4096-llama-cpp-b10507-2026-08-20" style="--vc-x:67.116;--vc-y:25.345">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-14b-q4-k-m-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" style="--vc-x:68.662;--vc-y:24.538">&lt;/span>
&lt;span class="vc-pin vc-pin--spill" data-vc-pin="sku-gpt-oss-20b-mxfp4-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" style="--vc-x:75.508;--vc-y:46.565">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-coder-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" style="--vc-x:76.581;--vc-y:23.622">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-gpt-oss-20b-mxfp4-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" style="--vc-x:76.875;--vc-y:60.708">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-gpt-oss-20b-mxfp4-ctx4096-llama-cpp-b10507-2026-08-20" style="--vc-x:79.967;--vc-y:55.490">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-qwen2-5-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" style="--vc-x:80.703;--vc-y:24.255">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-26" style="--vc-x:82.077;--vc-y:45.375">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-15-2026-08-26-defaults" style="--vc-x:83.236;--vc-y:53.385">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-15-2026-08-26-normalized" style="--vc-x:83.236;--vc-y:53.413">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-26" style="--vc-x:83.929;--vc-y:45.750">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-12" style="--vc-x:86.285;--vc-y:47.535">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-20" style="--vc-x:86.806;--vc-y:48.947">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-12" style="--vc-x:88.051;--vc-y:47.157">&lt;/span>
&lt;span class="vc-pin vc-pin--whole" data-vc-pin="sku-devstral-24b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" style="--vc-x:91.989;--vc-y:9.080">&lt;/span>
&lt;span class="vc-pin vc-pin--spill" data-vc-pin="sku-qwen3-coder-30b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" style="--vc-x:92.026;--vc-y:12.905">&lt;/span>
&lt;span class="vc-pin vc-pin--spill" data-vc-pin="sku-llama3-2-3b-q4-k-m-ctx131072-ollama-0-32-15-2026-08-26-defaults" style="--vc-x:92.523;--vc-y:25.670">&lt;/span>
&lt;span class="vc-pin vc-pin--spill" data-vc-pin="sku-qwen3-coder-30b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" style="--vc-x:92.627;--vc-y:15.473">&lt;/span>
&lt;span class="vc-pin vc-pin--shared" data-vc-pin="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" style="--vc-x:96.191;--vc-y:77.990">&lt;/span>
&lt;span class="vc-map__wall">&lt;/span>
&lt;span class="vc-map__call" data-vc-link-a="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults" data-vc-link-b="sku-llama3-2-3b-q4-k-m-ctx131072-ollama-0-32-15-2026-08-26-defaults" style="--vc-x:23.063;--vc-y:87.805">&lt;span>llama3.2:3b, 4,096 to 131,072 context&lt;/span>&lt;span>351.22 to 102.68 tok/s&lt;/span>&lt;/span>
&lt;span class="vc-map__tip" data-vc-tip hidden>&lt;/span>
&lt;/div>
&lt;div class="vc-map__rail" data-vc-rail>
&lt;span class="vc-map__railfill">&lt;/span>
&lt;span class="vc-map__railrest">&lt;/span>
&lt;/div>
&lt;div class="vc-map__xaxis">
&lt;span class="vc-map__xtick" style="--vc-x:0.000">0&lt;/span>
&lt;span class="vc-map__xtick" style="--vc-x:25.124">4,096&lt;/span>
&lt;span class="vc-map__xtick" style="--vc-x:50.248">8,192&lt;/span>
&lt;span class="vc-map__xtick" style="--vc-x:75.373">12,288&lt;/span>
&lt;span class="vc-map__xtick vc-map__xtick--wall" style="--vc-x:100">16,303&lt;/span>
&lt;span class="vc-map__xtitle">MiB in use&lt;/span>
&lt;span class="vc-map__walllabel">card total&lt;/span>
&lt;/div>
&lt;/div>
&lt;p class="vc-map__sel" data-vc-raillabel hidden>&lt;/p>
&lt;ul class="vc-glyphs">
&lt;li>&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>A measured configuration&lt;/li>
&lt;li>&lt;span class="vc-glyph vc-glyph--spill" aria-hidden="true">&lt;/span>Ran partly off the card&lt;/li>
&lt;li>&lt;span class="vc-glyph vc-glyph--shared" aria-hidden="true">&lt;/span>Reading includes another model&lt;/li>
&lt;li>&lt;span class="vc-glyph vc-glyph--link" aria-hidden="true">&lt;/span>Same setup, context raised&lt;/li>
&lt;/ul>
&lt;p class="vc-map__note">Every pin is one row from a capture file. Nothing between two pins was measured, and nothing here is an estimate.&lt;/p>
&lt;/section>
&lt;section class="vc-panel vc-panel--readout" aria-label="Readout for the selected configuration">
&lt;div class="vc-panel__head">
&lt;p class="vc-panel__title">Readout&lt;/p>
&lt;p class="vc-panel__meta" data-vc-readout-meta>Nothing selected&lt;/p>
&lt;/div>
&lt;div class="vc-readout" data-vc-readout>
&lt;div class="vc-idle" data-vc-idle>
&lt;p class="vc-idle__lead" data-vc-idle-js hidden>Click or tap near a pin, or pick a row in the list, and its measured record appears here.&lt;/p>
&lt;noscript>&lt;p class="vc-idle__lead">Scripts are off, so the readout stays empty. Every record is in the list below: open a row to read it.&lt;/p>&lt;/noscript>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m vc-kpi--wide">
&lt;dt>Card total&lt;/dt>
&lt;dd class="vc-kpi__v">16,303 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>, &lt;code>nvidia-smi&lt;/code> total in &lt;a href="https://techfuelhq.com/data/vram-cliff-raw/ollama-256k-slider-3b.json" download>the raw capture&lt;/a>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--n">
&lt;dt>Configurations&lt;/dt>
&lt;dd class="vc-kpi__v">36&lt;/dd>
&lt;dd class="vc-kpi__tag">Rows pinned on the map&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--n">
&lt;dt>Captured&lt;/dt>
&lt;dd class="vc-kpi__v vc-kpi__v--date">2026-08-12&lt;br>to 2026-08-26&lt;/dd>
&lt;dd class="vc-kpi__tag">First and last capture date&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;dl class="vc-tally">
&lt;div>&lt;dt>Model tags&lt;/dt>&lt;dd>8&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Quantizations&lt;/dt>&lt;dd>2&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Context lengths&lt;/dt>&lt;dd>4&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Runtime versions&lt;/dt>&lt;dd>4&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-idle__foot">For a card or a setup that is not on this map, the &lt;a href="https://techfuelhq.com/tools/llm-vram-calculator/">LLM VRAM calculator&lt;/a> estimates. This page does not.&lt;/p>
&lt;/div>
&lt;/div>
&lt;/section>
&lt;/div>
&lt;section class="vc-panel vc-panel--list" aria-label="Every measured configuration">
&lt;div class="vc-panel__head">
&lt;p class="vc-panel__title">Every measured configuration&lt;/p>
&lt;label class="vc-sort" data-vc-sortwrap hidden>&lt;span class="vc-field-ctl__label">Sort&lt;/span>
&lt;select data-vc-sort>
&lt;option value="vram-asc">Memory, low to high&lt;/option>
&lt;option value="vram-desc">Memory, high to low&lt;/option>
&lt;option value="decode-desc">Decode, fast to slow&lt;/option>
&lt;option value="decode-asc">Decode, slow to fast&lt;/option>
&lt;option value="date-desc">Capture date, newest first&lt;/option>
&lt;option value="model-asc">Model, A to Z&lt;/option>
&lt;/select>&lt;/label>
&lt;/div>
&lt;div class="vc-list__cols" aria-hidden="true">
&lt;span>Model&lt;/span>&lt;span>Quant · context&lt;/span>&lt;span>Runtime&lt;/span>&lt;span>Resident, whole card&lt;/span>&lt;span>Decode&lt;/span>&lt;span>Captured&lt;/span>&lt;span>&lt;/span>
&lt;/div>
&lt;ol class="vc-list" data-vc-list>
&lt;li class="vc-row" id="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults" data-vc-row data-family="llama323b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="ollama-0-32-15" data-vram="3760" data-decode="351.22" data-date="2026-08-26" data-model="llama3.2:3b" data-x="23.063" data-y="87.805" data-status="" data-vram-label="3,760" data-headroom-label="12,543" data-tip="llama3.2:3b · 4,096 context · Ollama 0.32.15 · defaults: 3,760 MiB, 351.22 tok/s">
&lt;a class="vc-row__pick" href="#sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">llama3.2:3b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.15 &lt;span class="vc-dim">defaults&lt;/span>&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:23.063%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>3,760&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>351.22&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults" aria-label="Copy link to llama3.2:3b, 4,096 context, Ollama 0.32.15, defaults, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>llama3.2:3b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · Ollama 0.32.15 · defaults&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">3,760 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.15. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="3,760 of 16,303 MiB in use, measured. 12,543 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:23.063%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:23.063%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">3,760 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">351.22 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">12,543 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 3,760&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">23.1&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>3,760 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time> &lt;span class="vc-dim">from the file's name&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App&lt;/dt>&lt;dd>ollama 0.32.15&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Engine&lt;/dt>&lt;dd>vendored llama.cpp 9d77fa172&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Condition&lt;/dt>&lt;dd>defaults&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>llama3.2:3b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>351.22 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>345.19 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>351.15 · 350.9 · 351.86 · 351.32 · 351.22 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt, median&lt;/dt>&lt;dd>17802.7 tok/s at 434 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Time to first token&lt;/dt>&lt;dd>Empty in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>3760 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory before the load&lt;/dt>&lt;dd>1053 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Added by loading the model&lt;/dt>&lt;dd>2,707 MiB &lt;span class="vc-formula">Computed: 3,760 − 1,053&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>2.67 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Cold first request&lt;/dt>&lt;dd>2.79 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App RAM while loaded&lt;/dt>&lt;dd>1234.0 MB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>3.67 GiB &lt;span class="vc-formula">Computed: 3,760 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of llama3.2:3b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">318.3 tok/s&lt;/b> at &lt;b class="vc-m">265.2 W&lt;/b> board power, &lt;b class="vc-m">0.833 J&lt;/b> per token in the file. That is &lt;b class="vc-c">833 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 0.833 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download>llm-server-compare-2026-08-26-lmstudio.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-normalized" data-vc-row data-family="llama323b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="ollama-0-32-15" data-vram="3760" data-decode="350.52" data-date="2026-08-26" data-model="llama3.2:3b" data-x="23.063" data-y="87.630" data-status="" data-vram-label="3,760" data-headroom-label="12,543" data-tip="llama3.2:3b · 4,096 context · Ollama 0.32.15 · normalized: 3,760 MiB, 350.52 tok/s">
&lt;a class="vc-row__pick" href="#sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-normalized" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">llama3.2:3b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.15 &lt;span class="vc-dim">normalized&lt;/span>&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:23.063%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>3,760&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>350.52&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-normalized" aria-label="Copy link to llama3.2:3b, 4,096 context, Ollama 0.32.15, normalized, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>llama3.2:3b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · Ollama 0.32.15 · normalized&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">3,760 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.15. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="3,760 of 16,303 MiB in use, measured. 12,543 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:23.063%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:23.063%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">3,760 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">350.52 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">12,543 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 3,760&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">23.1&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>3,760 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time> &lt;span class="vc-dim">from the file's name&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App&lt;/dt>&lt;dd>ollama 0.32.15&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Engine&lt;/dt>&lt;dd>vendored llama.cpp 9d77fa172&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Condition&lt;/dt>&lt;dd>normalized&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>llama3.2:3b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>350.52 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>338.11 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>349.35 · 350.38 · 350.52 · 350.63 · 350.96 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt, median&lt;/dt>&lt;dd>17862.3 tok/s at 432 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Time to first token&lt;/dt>&lt;dd>Empty in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>3760 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory before the load&lt;/dt>&lt;dd>1057 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Added by loading the model&lt;/dt>&lt;dd>2,703 MiB &lt;span class="vc-formula">Computed: 3,760 − 1,057&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>2.27 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Cold first request&lt;/dt>&lt;dd>2.38 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App RAM while loaded&lt;/dt>&lt;dd>1239.6 MB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>3.67 GiB &lt;span class="vc-formula">Computed: 3,760 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of llama3.2:3b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">318.3 tok/s&lt;/b> at &lt;b class="vc-m">265.2 W&lt;/b> board power, &lt;b class="vc-m">0.833 J&lt;/b> per token in the file. That is &lt;b class="vc-c">833 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 0.833 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download>llm-server-compare-2026-08-26-lmstudio.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-normalized">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-normalized" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-llama3-2-3b-q4-k-m-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" data-vc-row data-family="llama323b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="lm-studio-0-4-21" data-vram="3808" data-decode="316" data-date="2026-08-26" data-model="llama3.2:3b" data-x="23.358" data-y="79.000" data-status="" data-vram-label="3,808" data-headroom-label="12,495" data-tip="llama3.2:3b · 4,096 context · LM Studio 0.4.21 · normalized: 3,808 MiB, 316.00 tok/s">
&lt;a class="vc-row__pick" href="#sku-llama3-2-3b-q4-k-m-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">llama3.2:3b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">LM Studio 0.4.21 &lt;span class="vc-dim">normalized&lt;/span>&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:23.358%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>3,808&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>316.00&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" aria-label="Copy link to llama3.2:3b, 4,096 context, LM Studio 0.4.21, normalized, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>llama3.2:3b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · LM Studio 0.4.21 · normalized&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">3,808 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with LM Studio 0.4.21. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="3,808 of 16,303 MiB in use, measured. 12,495 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:23.358%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:23.358%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">3,808 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">316.00 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">12,495 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 3,808&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">23.4&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>3,808 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time> &lt;span class="vc-dim">from the file's name&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App&lt;/dt>&lt;dd>LM Studio 0.4.21&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Engine&lt;/dt>&lt;dd>llama.cpp-win-x86_64-nvidia-cuda12-avx2@2.29.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Condition&lt;/dt>&lt;dd>normalized&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>llama-3.2-3b-q4km&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>316.0 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>309.91 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>310.55 · 316.0 · 315.86 · 316.23 · 316.6 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt, median&lt;/dt>&lt;dd>20336.7 tok/s at 442 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Time to first token, median&lt;/dt>&lt;dd>9.2 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>3808 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory before the load&lt;/dt>&lt;dd>1103 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Added by loading the model&lt;/dt>&lt;dd>2,705 MiB &lt;span class="vc-formula">Computed: 3,808 − 1,103&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>2.76 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Cold first request&lt;/dt>&lt;dd>0.07 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App RAM while loaded&lt;/dt>&lt;dd>3469.6 MB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>3.72 GiB &lt;span class="vc-formula">Computed: 3,808 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download>llm-server-compare-2026-08-26-lmstudio.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-llama3-2-3b-q4-k-m-ctx4096-lm-studio-0-4-21-2026-08-26-normalized">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-llama3-2-3b-q4-k-m-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" data-vc-row data-family="llama323b" data-quant="Q4_K_M" data-ctx="8192" data-runtime="lm-studio-0-4-21" data-vram="4260" data-decode="314.86" data-date="2026-08-26" data-model="llama3.2:3b" data-x="26.130" data-y="78.715" data-status="" data-vram-label="4,260" data-headroom-label="12,043" data-tip="llama3.2:3b · 8,192 context · LM Studio 0.4.21 · defaults: 4,260 MiB, 314.86 tok/s">
&lt;a class="vc-row__pick" href="#sku-llama3-2-3b-q4-k-m-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">llama3.2:3b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 8,192 ctx&lt;/span>
&lt;span class="vc-row__rt">LM Studio 0.4.21 &lt;span class="vc-dim">defaults&lt;/span>&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:26.130%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>4,260&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>314.86&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" aria-label="Copy link to llama3.2:3b, 8,192 context, LM Studio 0.4.21, defaults, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>llama3.2:3b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 8,192 context · LM Studio 0.4.21 · defaults&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">4,260 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with LM Studio 0.4.21. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="4,260 of 16,303 MiB in use, measured. 12,043 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:26.130%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:26.130%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">4,260 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">314.86 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">12,043 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 4,260&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">26.1&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>4,260 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time> &lt;span class="vc-dim">from the file's name&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App&lt;/dt>&lt;dd>LM Studio 0.4.21&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Engine&lt;/dt>&lt;dd>llama.cpp-win-x86_64-nvidia-cuda12-avx2@2.29.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Condition&lt;/dt>&lt;dd>defaults&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>llama-3.2-3b-q4km&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>8192&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>314.86 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>308.68 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>273.28 · 312.54 · 316.75 · 315.22 · 314.86 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt, median&lt;/dt>&lt;dd>20341.8 tok/s at 440 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Time to first token, median&lt;/dt>&lt;dd>9.4 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>4260 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory before the load&lt;/dt>&lt;dd>1122 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Added by loading the model&lt;/dt>&lt;dd>3,138 MiB &lt;span class="vc-formula">Computed: 4,260 − 1,122&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>2.75 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Cold first request&lt;/dt>&lt;dd>0.07 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App RAM while loaded&lt;/dt>&lt;dd>3471.9 MB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>4.16 GiB &lt;span class="vc-formula">Computed: 4,260 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download>llm-server-compare-2026-08-26-lmstudio.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-llama3-2-3b-q4-k-m-ctx8192-lm-studio-0-4-21-2026-08-26-defaults">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-llama3-2-3b-q4-k-m-ctx4096-llama-cpp-b10507-2026-08-20" data-vc-row data-family="llama323b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="llama-cpp-b10507" data-vram="4339" data-decode="338.22" data-date="2026-08-20" data-model="llama3.2:3b" data-x="26.615" data-y="84.555" data-status="" data-vram-label="4,339" data-headroom-label="11,964" data-tip="llama3.2:3b · 4,096 context · llama.cpp b10507: 4,339 MiB, 338.22 tok/s">
&lt;a class="vc-row__pick" href="#sku-llama3-2-3b-q4-k-m-ctx4096-llama-cpp-b10507-2026-08-20" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">llama3.2:3b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">llama.cpp b10507&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:26.615%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>4,339&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>338.22&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx4096-llama-cpp-b10507-2026-08-20" aria-label="Copy link to llama3.2:3b, 4,096 context, llama.cpp b10507, 2026-08-20" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>llama3.2:3b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · llama.cpp b10507&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">4,339 MiB&lt;/b> resident on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> with llama.cpp b10507. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="4,339 of 16,303 MiB in use, measured. 11,964 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:26.615%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:26.615%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">4,339 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">338.22 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">11,964 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 4,339&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">26.6&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>4,339 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-20">2026-08-20&lt;/time> &lt;span class="vc-dim">from the file's footer notes&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>llama.cpp b10507&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>llama3.2:3b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096 &lt;span class="vc-dim">from the file's settings note&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Offload&lt;/dt>&lt;dd>Full offload &lt;span class="vc-dim">from the file's settings note&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>338.22 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>336.01 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>339.2 · 338.2 · 335.0 · 338.2 · 339.7 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, short prompt, median&lt;/dt>&lt;dd>5321.0 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt&lt;/dt>&lt;dd>16809 tok/s at 407 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>4339 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>2.5 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Desktop baseline at bench start&lt;/dt>&lt;dd>1642 MiB &lt;span class="vc-dim">one reading for the whole capture&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>4.24 GiB &lt;span class="vc-formula">Computed: 4,339 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08.csv" download>llm-server-compare-2026-08.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-llama3-2-3b-q4-k-m-ctx4096-llama-cpp-b10507-2026-08-20">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx4096-llama-cpp-b10507-2026-08-20" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20" data-vc-row data-family="llama323b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="ollama-0-32-1" data-vram="4343" data-decode="318.51" data-date="2026-08-20" data-model="llama3.2:3b" data-x="26.639" data-y="79.627" data-status="" data-vram-label="4,343" data-headroom-label="11,960" data-tip="llama3.2:3b · 4,096 context · Ollama 0.32.1: 4,343 MiB, 318.51 tok/s">
&lt;a class="vc-row__pick" href="#sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">llama3.2:3b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:26.639%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>4,343&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>318.51&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20" aria-label="Copy link to llama3.2:3b, 4,096 context, Ollama 0.32.1, 2026-08-20" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>llama3.2:3b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">4,343 MiB&lt;/b> resident on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="4,343 of 16,303 MiB in use, measured. 11,960 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:26.639%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:26.639%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">4,343 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">318.51 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">11,960 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 4,343&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">26.6&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>4,343 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-20">2026-08-20&lt;/time> &lt;span class="vc-dim">from the file's footer notes&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>llama3.2:3b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096 &lt;span class="vc-dim">from the file's settings note&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Offload&lt;/dt>&lt;dd>Full offload &lt;span class="vc-dim">from the file's settings note&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>318.51 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>313.25 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>319.0 · 318.7 · 318.2 · 318.5 · 317.5 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, short prompt, median&lt;/dt>&lt;dd>7038.1 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt&lt;/dt>&lt;dd>17444 tok/s at 433 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>4343 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>3.2 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Desktop baseline at bench start&lt;/dt>&lt;dd>1642 MiB &lt;span class="vc-dim">one reading for the whole capture&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>4.24 GiB &lt;span class="vc-formula">Computed: 4,343 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of llama3.2:3b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">318.3 tok/s&lt;/b> at &lt;b class="vc-m">265.2 W&lt;/b> board power, &lt;b class="vc-m">0.833 J&lt;/b> per token in the file. That is &lt;b class="vc-c">833 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 0.833 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08.csv" download>llm-server-compare-2026-08.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-llama3-2-3b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" data-vc-row data-family="llama323b" data-quant="Q4_K_M" data-ctx="16384" data-runtime="ollama-0-32-1" data-vram="5495" data-decode="312.89" data-date="2026-08-12" data-model="llama3.2:3b" data-x="33.705" data-y="78.222" data-status="" data-vram-label="5,495" data-headroom-label="10,808" data-tip="llama3.2:3b · 16,384 context · Ollama 0.32.1: 5,495 MiB, 312.89 tok/s">
&lt;a class="vc-row__pick" href="#sku-llama3-2-3b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">llama3.2:3b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 16,384 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:33.705%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>5,495&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>312.89&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" aria-label="Copy link to llama3.2:3b, 16,384 context, Ollama 0.32.1, 2026-08-12" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>llama3.2:3b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 16,384 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">5,495 MiB&lt;/b> resident on &lt;time datetime="2026-08-12">2026-08-12&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="5,495 of 16,303 MiB in use, measured. 10,808 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:33.705%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:33.705%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">5,495 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">312.89 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">10,808 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 5,495&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">33.7&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>5,495 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>llama3.2:3b &lt;span class="vc-dim">digest a80c4f17acd5&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>3.2B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>16384&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>471&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>312.89 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>17885.62 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>162.9 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>5495 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1657&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>298.59 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>19397.36 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>158.0 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>5501 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>5.37 GiB &lt;span class="vc-formula">Computed: 5,495 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of llama3.2:3b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">318.3 tok/s&lt;/b> at &lt;b class="vc-m">265.2 W&lt;/b> board power, &lt;b class="vc-m">0.833 J&lt;/b> per token in the file. That is &lt;b class="vc-c">833 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 0.833 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-llama3-2-3b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-coder-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" data-vc-row data-family="qwen25coder7b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="ollama-0-32-1" data-vram="5671" data-decode="173.73" data-date="2026-08-26" data-model="qwen2.5-coder:7b" data-x="34.785" data-y="43.432" data-status="" data-vram-label="5,671" data-headroom-label="10,632" data-tip="qwen2.5-coder:7b · 4,096 context · Ollama 0.32.1: 5,671 MiB, 173.73 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-coder-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5-coder:7b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:34.785%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>5,671&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>173.73&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-coder-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" aria-label="Copy link to qwen2.5-coder:7b, 4,096 context, Ollama 0.32.1, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5-coder:7b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">5,671 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="5,671 of 16,303 MiB in use, measured. 10,632 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:34.785%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:34.785%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">5,671 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">173.73 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">10,632 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 5,671&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">34.8&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>5,671 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>qwen2.5-coder:7b &lt;span class="vc-dim">digest dae161e27b0e&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>7.6B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>488&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>173.73 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>9651.9 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>159.1 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>5671 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1368&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>171.73 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>9506.54 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>159.6 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>5671 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>5.54 GiB &lt;span class="vc-formula">Computed: 5,671 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-coder-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-coder-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" data-vc-row data-family="qwen257b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="ollama-0-32-1" data-vram="6190" data-decode="180.02" data-date="2026-08-12" data-model="qwen2.5:7b" data-x="37.968" data-y="45.005" data-status="" data-vram-label="6,190" data-headroom-label="10,113" data-tip="qwen2.5:7b · 4,096 context · Ollama 0.32.1: 6,190 MiB, 180.02 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5:7b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:37.968%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>6,190&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>180.02&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" aria-label="Copy link to qwen2.5:7b, 4,096 context, Ollama 0.32.1, 2026-08-12" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5:7b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">6,190 MiB&lt;/b> resident on &lt;time datetime="2026-08-12">2026-08-12&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="6,190 of 16,303 MiB in use, measured. 10,113 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:37.968%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:37.968%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">6,190 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">180.02 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">10,113 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 6,190&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">38.0&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>6,190 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>qwen2.5:7b &lt;span class="vc-dim">digest 845dbda0ea48&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>7.6B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>488&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>180.02 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>10152.28 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>129.8 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>6190 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1674&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>176.79 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>9672.39 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>123.4 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>6190 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>6.04 GiB &lt;span class="vc-formula">Computed: 6,190 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of qwen2.5:7b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">182.2 tok/s&lt;/b> at &lt;b class="vc-m">343.6 W&lt;/b> board power, &lt;b class="vc-m">1.886 J&lt;/b> per token in the file. That is &lt;b class="vc-c">1,886 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 1.886 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-coder-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" data-vc-row data-family="qwen25coder7b" data-quant="Q4_K_M" data-ctx="16384" data-runtime="ollama-0-32-1" data-vram="6503" data-decode="174.58" data-date="2026-08-26" data-model="qwen2.5-coder:7b" data-x="39.888" data-y="43.645" data-status="" data-vram-label="6,503" data-headroom-label="9,800" data-tip="qwen2.5-coder:7b · 16,384 context · Ollama 0.32.1: 6,503 MiB, 174.58 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-coder-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5-coder:7b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 16,384 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:39.888%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>6,503&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>174.58&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-coder-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" aria-label="Copy link to qwen2.5-coder:7b, 16,384 context, Ollama 0.32.1, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5-coder:7b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 16,384 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">6,503 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="6,503 of 16,303 MiB in use, measured. 9,800 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:39.888%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:39.888%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">6,503 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">174.58 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">9,800 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 6,503&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">39.9&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>6,503 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>qwen2.5-coder:7b &lt;span class="vc-dim">digest dae161e27b0e&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>7.6B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>16384&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>488&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>174.58 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>9471.68 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>145.9 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>6503 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1368&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>171.41 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>9825.47 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>178.3 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>6515 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>6.35 GiB &lt;span class="vc-formula">Computed: 6,503 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-coder-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-coder-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" data-vc-row data-family="qwen257b" data-quant="Q4_K_M" data-ctx="16384" data-runtime="ollama-0-32-1" data-vram="7022" data-decode="179.66" data-date="2026-08-12" data-model="qwen2.5:7b" data-x="43.072" data-y="44.915" data-status="" data-vram-label="7,022" data-headroom-label="9,281" data-tip="qwen2.5:7b · 16,384 context · Ollama 0.32.1: 7,022 MiB, 179.66 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5:7b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 16,384 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:43.072%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>7,022&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>179.66&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" aria-label="Copy link to qwen2.5:7b, 16,384 context, Ollama 0.32.1, 2026-08-12" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5:7b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 16,384 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">7,022 MiB&lt;/b> resident on &lt;time datetime="2026-08-12">2026-08-12&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="7,022 of 16,303 MiB in use, measured. 9,281 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:43.072%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:43.072%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">7,022 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">179.66 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">9,281 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 7,022&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">43.1&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>7,022 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>qwen2.5:7b &lt;span class="vc-dim">digest 845dbda0ea48&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>7.6B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>16384&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>488&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>179.66 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>10133.1 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>127.9 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>7022 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1674&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>176.61 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>9984.37 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>127.7 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>7034 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>6.86 GiB &lt;span class="vc-formula">Computed: 7,022 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of qwen2.5:7b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">182.2 tok/s&lt;/b> at &lt;b class="vc-m">343.6 W&lt;/b> board power, &lt;b class="vc-m">1.886 J&lt;/b> per token in the file. That is &lt;b class="vc-c">1,886 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 1.886 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-coder-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" data-vc-row data-family="qwen25coder14b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="ollama-0-32-1" data-vram="10169" data-decode="94.89" data-date="2026-08-26" data-model="qwen2.5-coder:14b" data-x="62.375" data-y="23.723" data-status="" data-vram-label="10,169" data-headroom-label="6,134" data-tip="qwen2.5-coder:14b · 4,096 context · Ollama 0.32.1: 10,169 MiB, 94.89 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-coder-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5-coder:14b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:62.375%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>10,169&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>94.89&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-coder-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" aria-label="Copy link to qwen2.5-coder:14b, 4,096 context, Ollama 0.32.1, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5-coder:14b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">10,169 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="10,169 of 16,303 MiB in use, measured. 6,134 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:62.375%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:62.375%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">10,169 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">94.89 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">6,134 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 10,169&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">62.4&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>10,169 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>qwen2.5-coder:14b &lt;span class="vc-dim">digest 9ec8897f747e&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>14.8B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>488&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>94.89 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>5271.63 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>219.8 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>10169 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1368&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>93.8 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>4942.3 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>159.4 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>10171 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>9.93 GiB &lt;span class="vc-formula">Computed: 10,169 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-coder-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-coder-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults" data-vc-row data-family="qwen2514b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="ollama-0-32-15" data-vram="10356" data-decode="102.25" data-date="2026-08-26" data-model="qwen2.5:14b" data-x="63.522" data-y="25.562" data-status="" data-vram-label="10,356" data-headroom-label="5,947" data-tip="qwen2.5:14b · 4,096 context · Ollama 0.32.15 · defaults: 10,356 MiB, 102.25 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5:14b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.15 &lt;span class="vc-dim">defaults&lt;/span>&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:63.522%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>10,356&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>102.25&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults" aria-label="Copy link to qwen2.5:14b, 4,096 context, Ollama 0.32.15, defaults, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5:14b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · Ollama 0.32.15 · defaults&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">10,356 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.15. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="10,356 of 16,303 MiB in use, measured. 5,947 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:63.522%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:63.522%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">10,356 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">102.25 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">5,947 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 10,356&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">63.5&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>10,356 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time> &lt;span class="vc-dim">from the file's name&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App&lt;/dt>&lt;dd>ollama 0.32.15&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Engine&lt;/dt>&lt;dd>vendored llama.cpp 9d77fa172&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Condition&lt;/dt>&lt;dd>defaults&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>qwen2.5:14b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>102.25 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>101.06 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>102.13 · 102.34 · 102.25 · 102.3 · 102.25 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt, median&lt;/dt>&lt;dd>4983.8 tok/s at 453 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Time to first token&lt;/dt>&lt;dd>Empty in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>10356 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory before the load&lt;/dt>&lt;dd>1053 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Added by loading the model&lt;/dt>&lt;dd>9,303 MiB &lt;span class="vc-formula">Computed: 10,356 − 1,053&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>5.51 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Cold first request&lt;/dt>&lt;dd>5.67 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App RAM while loaded&lt;/dt>&lt;dd>1604.1 MB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>10.11 GiB &lt;span class="vc-formula">Computed: 10,356 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of qwen2.5:14b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">98.8 tok/s&lt;/b> at &lt;b class="vc-m">311.6 W&lt;/b> board power, &lt;b class="vc-m">3.154 J&lt;/b> per token in the file. That is &lt;b class="vc-c">3,154 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 3.154 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download>llm-server-compare-2026-08-26-lmstudio.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-normalized" data-vc-row data-family="qwen2514b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="ollama-0-32-15" data-vram="10356" data-decode="102.21" data-date="2026-08-26" data-model="qwen2.5:14b" data-x="63.522" data-y="25.552" data-status="" data-vram-label="10,356" data-headroom-label="5,947" data-tip="qwen2.5:14b · 4,096 context · Ollama 0.32.15 · normalized: 10,356 MiB, 102.21 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-normalized" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5:14b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.15 &lt;span class="vc-dim">normalized&lt;/span>&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:63.522%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>10,356&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>102.21&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-normalized" aria-label="Copy link to qwen2.5:14b, 4,096 context, Ollama 0.32.15, normalized, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5:14b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · Ollama 0.32.15 · normalized&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">10,356 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.15. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="10,356 of 16,303 MiB in use, measured. 5,947 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:63.522%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:63.522%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">10,356 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">102.21 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">5,947 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 10,356&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">63.5&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>10,356 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time> &lt;span class="vc-dim">from the file's name&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App&lt;/dt>&lt;dd>ollama 0.32.15&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Engine&lt;/dt>&lt;dd>vendored llama.cpp 9d77fa172&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Condition&lt;/dt>&lt;dd>normalized&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>qwen2.5:14b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>102.21 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>101.23 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>102.21 · 102.21 · 102.17 · 102.21 · 102.21 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt, median&lt;/dt>&lt;dd>5038.3 tok/s at 452 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Time to first token&lt;/dt>&lt;dd>Empty in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>10356 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory before the load&lt;/dt>&lt;dd>1053 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Added by loading the model&lt;/dt>&lt;dd>9,303 MiB &lt;span class="vc-formula">Computed: 10,356 − 1,053&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>5.52 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Cold first request&lt;/dt>&lt;dd>5.68 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App RAM while loaded&lt;/dt>&lt;dd>1617.6 MB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>10.11 GiB &lt;span class="vc-formula">Computed: 10,356 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of qwen2.5:14b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">98.8 tok/s&lt;/b> at &lt;b class="vc-m">311.6 W&lt;/b> board power, &lt;b class="vc-m">3.154 J&lt;/b> per token in the file. That is &lt;b class="vc-c">3,154 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 3.154 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download>llm-server-compare-2026-08-26-lmstudio.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-normalized">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-normalized" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-14b-q4-k-m-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" data-vc-row data-family="qwen2514b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="lm-studio-0-4-21" data-vram="10405" data-decode="97.63" data-date="2026-08-26" data-model="qwen2.5:14b" data-x="63.823" data-y="24.407" data-status="" data-vram-label="10,405" data-headroom-label="5,898" data-tip="qwen2.5:14b · 4,096 context · LM Studio 0.4.21 · normalized: 10,405 MiB, 97.63 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-14b-q4-k-m-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5:14b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">LM Studio 0.4.21 &lt;span class="vc-dim">normalized&lt;/span>&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:63.823%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>10,405&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>97.63&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" aria-label="Copy link to qwen2.5:14b, 4,096 context, LM Studio 0.4.21, normalized, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5:14b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · LM Studio 0.4.21 · normalized&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">10,405 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with LM Studio 0.4.21. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="10,405 of 16,303 MiB in use, measured. 5,898 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:63.823%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:63.823%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">10,405 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">97.63 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">5,898 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 10,405&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">63.8&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>10,405 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time> &lt;span class="vc-dim">from the file's name&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App&lt;/dt>&lt;dd>LM Studio 0.4.21&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Engine&lt;/dt>&lt;dd>llama.cpp-win-x86_64-nvidia-cuda12-avx2@2.29.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Condition&lt;/dt>&lt;dd>normalized&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>qwen2.5-14b-q4km&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>97.63 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>96.62 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>96.89 · 97.75 · 97.46 · 97.79 · 97.63 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt, median&lt;/dt>&lt;dd>5566.5 tok/s at 453 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Time to first token, median&lt;/dt>&lt;dd>24.7 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>10405 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory before the load&lt;/dt>&lt;dd>1106 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Added by loading the model&lt;/dt>&lt;dd>9,299 MiB &lt;span class="vc-formula">Computed: 10,405 − 1,106&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>7.68 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Cold first request&lt;/dt>&lt;dd>0.16 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App RAM while loaded&lt;/dt>&lt;dd>10411.1 MB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>10.16 GiB &lt;span class="vc-formula">Computed: 10,405 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download>llm-server-compare-2026-08-26-lmstudio.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-14b-q4-k-m-ctx4096-lm-studio-0-4-21-2026-08-26-normalized">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" data-vc-row data-family="qwen2514b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="ollama-0-32-1" data-vram="10841" data-decode="96.65" data-date="2026-08-12" data-model="qwen2.5:14b" data-x="66.497" data-y="24.163" data-status="" data-vram-label="10,841" data-headroom-label="5,462" data-tip="qwen2.5:14b · 4,096 context · Ollama 0.32.1: 10,841 MiB, 96.65 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5:14b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:66.497%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>10,841&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>96.65&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" aria-label="Copy link to qwen2.5:14b, 4,096 context, Ollama 0.32.1, 2026-08-12" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5:14b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">10,841 MiB&lt;/b> resident on &lt;time datetime="2026-08-12">2026-08-12&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="10,841 of 16,303 MiB in use, measured. 5,462 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:66.497%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:66.497%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">10,841 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">96.65 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">5,462 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 10,841&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">66.5&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>10,841 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>qwen2.5:14b &lt;span class="vc-dim">digest 7cdf5a0187d5&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>14.8B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>488&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>96.65 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>5202.23 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>182.5 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>10841 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1674&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>94.48 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>4876.41 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>125.8 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>10855 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>10.59 GiB &lt;span class="vc-formula">Computed: 10,841 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of qwen2.5:14b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">98.8 tok/s&lt;/b> at &lt;b class="vc-m">311.6 W&lt;/b> board power, &lt;b class="vc-m">3.154 J&lt;/b> per token in the file. That is &lt;b class="vc-c">3,154 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 3.154 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20" data-vc-row data-family="qwen2514b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="ollama-0-32-1" data-vram="10941" data-decode="99.43" data-date="2026-08-20" data-model="qwen2.5:14b" data-x="67.110" data-y="24.858" data-status="" data-vram-label="10,941" data-headroom-label="5,362" data-tip="qwen2.5:14b · 4,096 context · Ollama 0.32.1: 10,941 MiB, 99.43 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5:14b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:67.110%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>10,941&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>99.43&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20" aria-label="Copy link to qwen2.5:14b, 4,096 context, Ollama 0.32.1, 2026-08-20" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5:14b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">10,941 MiB&lt;/b> resident on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="10,941 of 16,303 MiB in use, measured. 5,362 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:67.110%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:67.110%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">10,941 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">99.43 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">5,362 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 10,941&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">67.1&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>10,941 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-20">2026-08-20&lt;/time> &lt;span class="vc-dim">from the file's footer notes&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>qwen2.5:14b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096 &lt;span class="vc-dim">from the file's settings note&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Offload&lt;/dt>&lt;dd>Full offload &lt;span class="vc-dim">from the file's settings note&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>99.43 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>98.59 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>99.5 · 99.5 · 99.4 · 99.4 · 99.3 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, short prompt, median&lt;/dt>&lt;dd>3151.4 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt&lt;/dt>&lt;dd>5004 tok/s at 451 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>10941 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>5.6 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Desktop baseline at bench start&lt;/dt>&lt;dd>1642 MiB &lt;span class="vc-dim">one reading for the whole capture&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>10.68 GiB &lt;span class="vc-formula">Computed: 10,941 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of qwen2.5:14b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">98.8 tok/s&lt;/b> at &lt;b class="vc-m">311.6 W&lt;/b> board power, &lt;b class="vc-m">3.154 J&lt;/b> per token in the file. That is &lt;b class="vc-c">3,154 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 3.154 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08.csv" download>llm-server-compare-2026-08.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-14b-q4-k-m-ctx4096-llama-cpp-b10507-2026-08-20" data-vc-row data-family="qwen2514b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="llama-cpp-b10507" data-vram="10942" data-decode="101.38" data-date="2026-08-20" data-model="qwen2.5:14b" data-x="67.116" data-y="25.345" data-status="" data-vram-label="10,942" data-headroom-label="5,361" data-tip="qwen2.5:14b · 4,096 context · llama.cpp b10507: 10,942 MiB, 101.38 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-14b-q4-k-m-ctx4096-llama-cpp-b10507-2026-08-20" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5:14b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">llama.cpp b10507&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:67.116%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>10,942&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>101.38&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx4096-llama-cpp-b10507-2026-08-20" aria-label="Copy link to qwen2.5:14b, 4,096 context, llama.cpp b10507, 2026-08-20" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5:14b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · llama.cpp b10507&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">10,942 MiB&lt;/b> resident on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> with llama.cpp b10507. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="10,942 of 16,303 MiB in use, measured. 5,361 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:67.116%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:67.116%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">10,942 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">101.38 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">5,361 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 10,942&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">67.1&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>10,942 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-20">2026-08-20&lt;/time> &lt;span class="vc-dim">from the file's footer notes&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>llama.cpp b10507&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>qwen2.5:14b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096 &lt;span class="vc-dim">from the file's settings note&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Offload&lt;/dt>&lt;dd>Full offload &lt;span class="vc-dim">from the file's settings note&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>101.38 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>101.29 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>101.3 · 101.2 · 101.4 · 101.4 · 101.4 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, short prompt, median&lt;/dt>&lt;dd>2037.8 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt&lt;/dt>&lt;dd>4697 tok/s at 423 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>10942 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>8.1 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Desktop baseline at bench start&lt;/dt>&lt;dd>1642 MiB &lt;span class="vc-dim">one reading for the whole capture&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>10.69 GiB &lt;span class="vc-formula">Computed: 10,942 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08.csv" download>llm-server-compare-2026-08.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-14b-q4-k-m-ctx4096-llama-cpp-b10507-2026-08-20">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx4096-llama-cpp-b10507-2026-08-20" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-14b-q4-k-m-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" data-vc-row data-family="qwen2514b" data-quant="Q4_K_M" data-ctx="8192" data-runtime="lm-studio-0-4-21" data-vram="11194" data-decode="98.15" data-date="2026-08-26" data-model="qwen2.5:14b" data-x="68.662" data-y="24.538" data-status="" data-vram-label="11,194" data-headroom-label="5,109" data-tip="qwen2.5:14b · 8,192 context · LM Studio 0.4.21 · defaults: 11,194 MiB, 98.15 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-14b-q4-k-m-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5:14b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 8,192 ctx&lt;/span>
&lt;span class="vc-row__rt">LM Studio 0.4.21 &lt;span class="vc-dim">defaults&lt;/span>&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:68.662%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>11,194&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>98.15&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" aria-label="Copy link to qwen2.5:14b, 8,192 context, LM Studio 0.4.21, defaults, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5:14b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 8,192 context · LM Studio 0.4.21 · defaults&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">11,194 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with LM Studio 0.4.21. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="11,194 of 16,303 MiB in use, measured. 5,109 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:68.662%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:68.662%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">11,194 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">98.15 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">5,109 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 11,194&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">68.7&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>11,194 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time> &lt;span class="vc-dim">from the file's name&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App&lt;/dt>&lt;dd>LM Studio 0.4.21&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Engine&lt;/dt>&lt;dd>llama.cpp-win-x86_64-nvidia-cuda12-avx2@2.29.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Condition&lt;/dt>&lt;dd>defaults&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>qwen2.5-14b-q4km&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>8192&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>98.15 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>97.31 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>97.36 · 98.14 · 98.17 · 98.15 · 98.17 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt, median&lt;/dt>&lt;dd>5195.8 tok/s at 454 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Time to first token, median&lt;/dt>&lt;dd>24.6 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>11194 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory before the load&lt;/dt>&lt;dd>1103 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Added by loading the model&lt;/dt>&lt;dd>10,091 MiB &lt;span class="vc-formula">Computed: 11,194 − 1,103&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>7.38 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Cold first request&lt;/dt>&lt;dd>0.15 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App RAM while loaded&lt;/dt>&lt;dd>10406.8 MB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>10.93 GiB &lt;span class="vc-formula">Computed: 11,194 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download>llm-server-compare-2026-08-26-lmstudio.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-14b-q4-k-m-ctx8192-lm-studio-0-4-21-2026-08-26-defaults">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-gpt-oss-20b-mxfp4-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" data-vc-row data-family="gptoss20b" data-quant="MXFP4" data-ctx="8192" data-runtime="lm-studio-0-4-21" data-vram="12310" data-decode="186.26" data-date="2026-08-26" data-model="gpt-oss:20b" data-x="75.508" data-y="46.565" data-status="spill" data-vram-label="12,310" data-headroom-label="3,993" data-tip="gpt-oss:20b · 8,192 context · LM Studio 0.4.21 · defaults: 12,310 MiB, 186.26 tok/s">
&lt;a class="vc-row__pick" href="#sku-gpt-oss-20b-mxfp4-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--spill" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">gpt-oss:20b&lt;/span>&lt;span class="vc-row__flag">Ran partly off the card&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">MXFP4 · 8,192 ctx&lt;/span>
&lt;span class="vc-row__rt">LM Studio 0.4.21 &lt;span class="vc-dim">defaults&lt;/span>&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:75.508%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>12,310&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>186.26&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" aria-label="Copy link to gpt-oss:20b, 8,192 context, LM Studio 0.4.21, defaults, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--spill" aria-hidden="true">&lt;/span>&lt;strong>gpt-oss:20b&lt;/strong>
&lt;span class="vc-record__spec">MXFP4 · 8,192 context · LM Studio 0.4.21 · defaults&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">12,310 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with LM Studio 0.4.21. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;p class="vc-flag vc-flag--spill">&lt;span class="vc-flag__label">Ran partly off the card&lt;/span>&lt;/p>
&lt;p class="vc-note">LM Studio&amp;#39;s default automatic GPU offload was in effect, at its default 8,192 context. The dataset attributes the lower decode rate to that setting. The normalized row is the same model with full offload. &lt;a href="https://techfuelhq.com/data/llm-server-compare/">Runtime comparison dataset&lt;/a>.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="12,310 of 16,303 MiB in use, measured. 3,993 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:75.508%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:75.508%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">12,310 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">186.26 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">3,993 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 12,310&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">75.5&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>12,310 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time> &lt;span class="vc-dim">from the file's name&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App&lt;/dt>&lt;dd>LM Studio 0.4.21&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Engine&lt;/dt>&lt;dd>llama.cpp-win-x86_64-nvidia-cuda12-avx2@2.29.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Condition&lt;/dt>&lt;dd>defaults&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>gpt-oss-20b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>MXFP4. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>8192&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>186.26 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>184.34 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>183.42 · 186.26 · 186.84 · 186.98 · 185.4 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt, median&lt;/dt>&lt;dd>5241.3 tok/s at 474 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Time to first token, median&lt;/dt>&lt;dd>78.9 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>12310 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory before the load&lt;/dt>&lt;dd>1119 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Added by loading the model&lt;/dt>&lt;dd>11,191 MiB &lt;span class="vc-formula">Computed: 12,310 − 1,119&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>8.43 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Cold first request&lt;/dt>&lt;dd>0.36 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App RAM while loaded&lt;/dt>&lt;dd>12917.9 MB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>12.02 GiB &lt;span class="vc-formula">Computed: 12,310 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download>llm-server-compare-2026-08-26-lmstudio.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-gpt-oss-20b-mxfp4-ctx8192-lm-studio-0-4-21-2026-08-26-defaults">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx8192-lm-studio-0-4-21-2026-08-26-defaults" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-coder-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" data-vc-row data-family="qwen25coder14b" data-quant="Q4_K_M" data-ctx="16384" data-runtime="ollama-0-32-1" data-vram="12485" data-decode="94.49" data-date="2026-08-26" data-model="qwen2.5-coder:14b" data-x="76.581" data-y="23.622" data-status="" data-vram-label="12,485" data-headroom-label="3,818" data-tip="qwen2.5-coder:14b · 16,384 context · Ollama 0.32.1: 12,485 MiB, 94.49 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-coder-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5-coder:14b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 16,384 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:76.581%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>12,485&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>94.49&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-coder-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" aria-label="Copy link to qwen2.5-coder:14b, 16,384 context, Ollama 0.32.1, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5-coder:14b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 16,384 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">12,485 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="12,485 of 16,303 MiB in use, measured. 3,818 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:76.581%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:76.581%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">12,485 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">94.49 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">3,818 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 12,485&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">76.6&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>12,485 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>qwen2.5-coder:14b &lt;span class="vc-dim">digest 9ec8897f747e&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>14.8B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>16384&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>488&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>94.49 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>4909.36 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>159.5 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>12485 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1368&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>93.41 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>4842.15 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>153.2 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>12487 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>12.19 GiB &lt;span class="vc-formula">Computed: 12,485 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-coder-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-coder-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-gpt-oss-20b-mxfp4-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" data-vc-row data-family="gptoss20b" data-quant="MXFP4" data-ctx="4096" data-runtime="lm-studio-0-4-21" data-vram="12533" data-decode="242.83" data-date="2026-08-26" data-model="gpt-oss:20b" data-x="76.875" data-y="60.708" data-status="" data-vram-label="12,533" data-headroom-label="3,770" data-tip="gpt-oss:20b · 4,096 context · LM Studio 0.4.21 · normalized: 12,533 MiB, 242.83 tok/s">
&lt;a class="vc-row__pick" href="#sku-gpt-oss-20b-mxfp4-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">gpt-oss:20b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">MXFP4 · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">LM Studio 0.4.21 &lt;span class="vc-dim">normalized&lt;/span>&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:76.875%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>12,533&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>242.83&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" aria-label="Copy link to gpt-oss:20b, 4,096 context, LM Studio 0.4.21, normalized, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>gpt-oss:20b&lt;/strong>
&lt;span class="vc-record__spec">MXFP4 · 4,096 context · LM Studio 0.4.21 · normalized&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">12,533 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with LM Studio 0.4.21. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="12,533 of 16,303 MiB in use, measured. 3,770 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:76.875%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:76.875%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">12,533 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">242.83 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">3,770 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 12,533&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">76.9&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>12,533 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time> &lt;span class="vc-dim">from the file's name&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App&lt;/dt>&lt;dd>LM Studio 0.4.21&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Engine&lt;/dt>&lt;dd>llama.cpp-win-x86_64-nvidia-cuda12-avx2@2.29.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Condition&lt;/dt>&lt;dd>normalized&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>gpt-oss-20b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>MXFP4. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>242.83 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>240.13 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>242.83 · 242.82 · 243.14 · 241.74 · 244.35 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt, median&lt;/dt>&lt;dd>9617.7 tok/s at 474 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Time to first token, median&lt;/dt>&lt;dd>38.6 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>12533 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory before the load&lt;/dt>&lt;dd>1101 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Added by loading the model&lt;/dt>&lt;dd>11,432 MiB &lt;span class="vc-formula">Computed: 12,533 − 1,101&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>8.43 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Cold first request&lt;/dt>&lt;dd>0.27 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App RAM while loaded&lt;/dt>&lt;dd>13176.6 MB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>12.24 GiB &lt;span class="vc-formula">Computed: 12,533 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download>llm-server-compare-2026-08-26-lmstudio.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-gpt-oss-20b-mxfp4-ctx4096-lm-studio-0-4-21-2026-08-26-normalized">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-lm-studio-0-4-21-2026-08-26-normalized" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-gpt-oss-20b-mxfp4-ctx4096-llama-cpp-b10507-2026-08-20" data-vc-row data-family="gptoss20b" data-quant="MXFP4" data-ctx="4096" data-runtime="llama-cpp-b10507" data-vram="13037" data-decode="221.96" data-date="2026-08-20" data-model="gpt-oss:20b" data-x="79.967" data-y="55.490" data-status="" data-vram-label="13,037" data-headroom-label="3,266" data-tip="gpt-oss:20b · 4,096 context · llama.cpp b10507: 13,037 MiB, 221.96 tok/s">
&lt;a class="vc-row__pick" href="#sku-gpt-oss-20b-mxfp4-ctx4096-llama-cpp-b10507-2026-08-20" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">gpt-oss:20b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">MXFP4 · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">llama.cpp b10507&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:79.967%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>13,037&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>221.96&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-llama-cpp-b10507-2026-08-20" aria-label="Copy link to gpt-oss:20b, 4,096 context, llama.cpp b10507, 2026-08-20" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>gpt-oss:20b&lt;/strong>
&lt;span class="vc-record__spec">MXFP4 · 4,096 context · llama.cpp b10507&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">13,037 MiB&lt;/b> resident on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> with llama.cpp b10507. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="13,037 of 16,303 MiB in use, measured. 3,266 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:79.967%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:79.967%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">13,037 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">221.96 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">3,266 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 13,037&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">80.0&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>13,037 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-20">2026-08-20&lt;/time> &lt;span class="vc-dim">from the file's footer notes&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>llama.cpp b10507 (upstream GGUF)&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>gpt-oss:20b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>MXFP4. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096 &lt;span class="vc-dim">from the file's settings note&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Offload&lt;/dt>&lt;dd>Full offload &lt;span class="vc-dim">from the file's settings note&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>221.96 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>220.53 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>185.8 · 242.6 · 222.0 · 231.9 · 175.3 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, short prompt, median&lt;/dt>&lt;dd>1078.7 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Prefill, long prompt&lt;/dt>&lt;dd>Empty in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>13037 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>19.8 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Desktop baseline at bench start&lt;/dt>&lt;dd>1642 MiB &lt;span class="vc-dim">one reading for the whole capture&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>12.73 GiB &lt;span class="vc-formula">Computed: 13,037 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08.csv" download>llm-server-compare-2026-08.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-gpt-oss-20b-mxfp4-ctx4096-llama-cpp-b10507-2026-08-20">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-llama-cpp-b10507-2026-08-20" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen2-5-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" data-vc-row data-family="qwen2514b" data-quant="Q4_K_M" data-ctx="16384" data-runtime="ollama-0-32-1" data-vram="13157" data-decode="97.02" data-date="2026-08-12" data-model="qwen2.5:14b" data-x="80.703" data-y="24.255" data-status="" data-vram-label="13,157" data-headroom-label="3,146" data-tip="qwen2.5:14b · 16,384 context · Ollama 0.32.1: 13,157 MiB, 97.02 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen2-5-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen2.5:14b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 16,384 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:80.703%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>13,157&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>97.02&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" aria-label="Copy link to qwen2.5:14b, 16,384 context, Ollama 0.32.1, 2026-08-12" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>qwen2.5:14b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 16,384 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">13,157 MiB&lt;/b> resident on &lt;time datetime="2026-08-12">2026-08-12&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="13,157 of 16,303 MiB in use, measured. 3,146 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:80.703%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:80.703%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">13,157 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">97.02 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">3,146 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 13,157&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">80.7&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>13,157 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>qwen2.5:14b &lt;span class="vc-dim">digest 7cdf5a0187d5&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>14.8B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>16384&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>488&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>97.02 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>5225.96 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>131.3 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>13157 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1674&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>94.58 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>4864.67 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>128.9 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>13159 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>12.85 GiB &lt;span class="vc-formula">Computed: 13,157 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of qwen2.5:14b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">98.8 tok/s&lt;/b> at &lt;b class="vc-m">311.6 W&lt;/b> board power, &lt;b class="vc-m">3.154 J&lt;/b> per token in the file. That is &lt;b class="vc-c">3,154 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 3.154 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen2-5-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen2-5-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-26" data-vc-row data-family="gptoss20b" data-quant="MXFP4" data-ctx="4096" data-runtime="ollama-0-32-1" data-vram="13381" data-decode="181.5" data-date="2026-08-26" data-model="gpt-oss:20b" data-x="82.077" data-y="45.375" data-status="" data-vram-label="13,381" data-headroom-label="2,922" data-tip="gpt-oss:20b · 4,096 context · Ollama 0.32.1: 13,381 MiB, 181.50 tok/s">
&lt;a class="vc-row__pick" href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-26" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">gpt-oss:20b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">MXFP4 · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:82.077%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>13,381&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>181.50&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-26" aria-label="Copy link to gpt-oss:20b, 4,096 context, Ollama 0.32.1, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>gpt-oss:20b&lt;/strong>
&lt;span class="vc-record__spec">MXFP4 · 4,096 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">13,381 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;p class="vc-note">A re-capture of the same model. The dataset&amp;#39;s change log notes it ran below the 2026-08-12 rows on a card several hours into continuous bench work. &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">Throughput dataset, change log&lt;/a>.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="13,381 of 16,303 MiB in use, measured. 2,922 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:82.077%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:82.077%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">13,381 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">181.50 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">2,922 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 13,381&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">82.1&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>13,381 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>gpt-oss:20b &lt;span class="vc-dim">digest 17052f91a42e&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>20.9B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>MXFP4&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>503&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>181.5 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>9607.49 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>383.7 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>13381 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1360&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>178.37 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>11001.37 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>375.9 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>13385 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>13.07 GiB &lt;span class="vc-formula">Computed: 13,381 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of gpt-oss:20b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">194.4 tok/s&lt;/b> at &lt;b class="vc-m">292.4 W&lt;/b> board power, &lt;b class="vc-m">1.504 J&lt;/b> per token in the file. That is &lt;b class="vc-c">1,504 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 1.504 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-26">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-26" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-15-2026-08-26-defaults" data-vc-row data-family="gptoss20b" data-quant="MXFP4" data-ctx="4096" data-runtime="ollama-0-32-15" data-vram="13570" data-decode="213.54" data-date="2026-08-26" data-model="gpt-oss:20b" data-x="83.236" data-y="53.385" data-status="" data-vram-label="13,570" data-headroom-label="2,733" data-tip="gpt-oss:20b · 4,096 context · Ollama 0.32.15 · defaults: 13,570 MiB, 213.54 tok/s">
&lt;a class="vc-row__pick" href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-15-2026-08-26-defaults" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">gpt-oss:20b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">MXFP4 · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.15 &lt;span class="vc-dim">defaults&lt;/span>&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:83.236%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>13,570&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>213.54&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-15-2026-08-26-defaults" aria-label="Copy link to gpt-oss:20b, 4,096 context, Ollama 0.32.15, defaults, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>gpt-oss:20b&lt;/strong>
&lt;span class="vc-record__spec">MXFP4 · 4,096 context · Ollama 0.32.15 · defaults&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">13,570 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.15. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="13,570 of 16,303 MiB in use, measured. 2,733 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:83.236%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:83.236%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">13,570 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">213.54 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">2,733 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 13,570&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">83.2&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>13,570 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time> &lt;span class="vc-dim">from the file's name&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App&lt;/dt>&lt;dd>ollama 0.32.15&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Engine&lt;/dt>&lt;dd>vendored llama.cpp 9d77fa172&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Condition&lt;/dt>&lt;dd>defaults&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>gpt-oss:20b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>MXFP4. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>213.54 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>212.03 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>213.22 · 213.64 · 213.48 · 213.54 · 213.76 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt, median&lt;/dt>&lt;dd>9239.4 tok/s at 475 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Time to first token&lt;/dt>&lt;dd>Empty in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>13570 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory before the load&lt;/dt>&lt;dd>1053 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Added by loading the model&lt;/dt>&lt;dd>12,517 MiB &lt;span class="vc-formula">Computed: 13,570 − 1,053&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>18.56 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Cold first request&lt;/dt>&lt;dd>23.67 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App RAM while loaded&lt;/dt>&lt;dd>2138.8 MB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>13.25 GiB &lt;span class="vc-formula">Computed: 13,570 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of gpt-oss:20b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">194.4 tok/s&lt;/b> at &lt;b class="vc-m">292.4 W&lt;/b> board power, &lt;b class="vc-m">1.504 J&lt;/b> per token in the file. That is &lt;b class="vc-c">1,504 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 1.504 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download>llm-server-compare-2026-08-26-lmstudio.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-15-2026-08-26-defaults">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-15-2026-08-26-defaults" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-15-2026-08-26-normalized" data-vc-row data-family="gptoss20b" data-quant="MXFP4" data-ctx="4096" data-runtime="ollama-0-32-15" data-vram="13570" data-decode="213.65" data-date="2026-08-26" data-model="gpt-oss:20b" data-x="83.236" data-y="53.413" data-status="" data-vram-label="13,570" data-headroom-label="2,733" data-tip="gpt-oss:20b · 4,096 context · Ollama 0.32.15 · normalized: 13,570 MiB, 213.65 tok/s">
&lt;a class="vc-row__pick" href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-15-2026-08-26-normalized" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">gpt-oss:20b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">MXFP4 · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.15 &lt;span class="vc-dim">normalized&lt;/span>&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:83.236%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>13,570&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>213.65&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-15-2026-08-26-normalized" aria-label="Copy link to gpt-oss:20b, 4,096 context, Ollama 0.32.15, normalized, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>gpt-oss:20b&lt;/strong>
&lt;span class="vc-record__spec">MXFP4 · 4,096 context · Ollama 0.32.15 · normalized&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">13,570 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.15. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="13,570 of 16,303 MiB in use, measured. 2,733 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:83.236%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:83.236%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">13,570 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">213.65 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">2,733 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 13,570&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">83.2&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>13,570 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time> &lt;span class="vc-dim">from the file's name&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App&lt;/dt>&lt;dd>ollama 0.32.15&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Engine&lt;/dt>&lt;dd>vendored llama.cpp 9d77fa172&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Condition&lt;/dt>&lt;dd>normalized&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>gpt-oss:20b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>MXFP4. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>213.65 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>211.8 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>213.62 · 213.65 · 213.68 · 213.25 · 213.73 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt, median&lt;/dt>&lt;dd>9187.1 tok/s at 474 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Time to first token&lt;/dt>&lt;dd>Empty in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>13570 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory before the load&lt;/dt>&lt;dd>1053 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Added by loading the model&lt;/dt>&lt;dd>12,517 MiB &lt;span class="vc-formula">Computed: 13,570 − 1,053&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>8.05 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Cold first request&lt;/dt>&lt;dd>8.36 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App RAM while loaded&lt;/dt>&lt;dd>2152.1 MB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>13.25 GiB &lt;span class="vc-formula">Computed: 13,570 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of gpt-oss:20b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">194.4 tok/s&lt;/b> at &lt;b class="vc-m">292.4 W&lt;/b> board power, &lt;b class="vc-m">1.504 J&lt;/b> per token in the file. That is &lt;b class="vc-c">1,504 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 1.504 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download>llm-server-compare-2026-08-26-lmstudio.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-15-2026-08-26-normalized">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-15-2026-08-26-normalized" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-26" data-vc-row data-family="gptoss20b" data-quant="MXFP4" data-ctx="16384" data-runtime="ollama-0-32-1" data-vram="13683" data-decode="183" data-date="2026-08-26" data-model="gpt-oss:20b" data-x="83.929" data-y="45.750" data-status="" data-vram-label="13,683" data-headroom-label="2,620" data-tip="gpt-oss:20b · 16,384 context · Ollama 0.32.1: 13,683 MiB, 183.00 tok/s">
&lt;a class="vc-row__pick" href="#sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-26" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">gpt-oss:20b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">MXFP4 · 16,384 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:83.929%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>13,683&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>183.00&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-26" aria-label="Copy link to gpt-oss:20b, 16,384 context, Ollama 0.32.1, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>gpt-oss:20b&lt;/strong>
&lt;span class="vc-record__spec">MXFP4 · 16,384 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">13,683 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;p class="vc-note">A re-capture of the same model. The dataset&amp;#39;s change log notes it ran below the 2026-08-12 rows on a card several hours into continuous bench work. &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">Throughput dataset, change log&lt;/a>.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="13,683 of 16,303 MiB in use, measured. 2,620 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:83.929%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:83.929%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">13,683 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">183.00 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">2,620 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 13,683&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">83.9&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>13,683 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>gpt-oss:20b &lt;span class="vc-dim">digest 17052f91a42e&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>20.9B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>MXFP4&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>16384&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>503&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>183.0 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>9092.22 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>347.7 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>13683 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1360&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>178.34 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>10328.62 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>345.3 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>13683 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>13.36 GiB &lt;span class="vc-formula">Computed: 13,683 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of gpt-oss:20b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">194.4 tok/s&lt;/b> at &lt;b class="vc-m">292.4 W&lt;/b> board power, &lt;b class="vc-m">1.504 J&lt;/b> per token in the file. That is &lt;b class="vc-c">1,504 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 1.504 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-26">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-26" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-12" data-vc-row data-family="gptoss20b" data-quant="MXFP4" data-ctx="4096" data-runtime="ollama-0-32-1" data-vram="14067" data-decode="190.14" data-date="2026-08-12" data-model="gpt-oss:20b" data-x="86.285" data-y="47.535" data-status="" data-vram-label="14,067" data-headroom-label="2,236" data-tip="gpt-oss:20b · 4,096 context · Ollama 0.32.1: 14,067 MiB, 190.14 tok/s">
&lt;a class="vc-row__pick" href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-12" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">gpt-oss:20b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">MXFP4 · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:86.285%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>14,067&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>190.14&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-12" aria-label="Copy link to gpt-oss:20b, 4,096 context, Ollama 0.32.1, 2026-08-12" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>gpt-oss:20b&lt;/strong>
&lt;span class="vc-record__spec">MXFP4 · 4,096 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">14,067 MiB&lt;/b> resident on &lt;time datetime="2026-08-12">2026-08-12&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="14,067 of 16,303 MiB in use, measured. 2,236 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:86.285%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:86.285%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">14,067 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">190.14 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">2,236 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 14,067&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">86.3&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>14,067 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>gpt-oss:20b &lt;span class="vc-dim">digest 17052f91a42e&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>20.9B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>MXFP4&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>503&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>190.14 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>9078.28 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>297.7 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>14067 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1658&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>187.27 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>10464.66 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>279.5 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>14060 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>13.74 GiB &lt;span class="vc-formula">Computed: 14,067 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of gpt-oss:20b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">194.4 tok/s&lt;/b> at &lt;b class="vc-m">292.4 W&lt;/b> board power, &lt;b class="vc-m">1.504 J&lt;/b> per token in the file. That is &lt;b class="vc-c">1,504 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 1.504 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-12">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-12" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-20" data-vc-row data-family="gptoss20b" data-quant="MXFP4" data-ctx="4096" data-runtime="ollama-0-32-1" data-vram="14152" data-decode="195.79" data-date="2026-08-20" data-model="gpt-oss:20b" data-x="86.806" data-y="48.947" data-status="" data-vram-label="14,152" data-headroom-label="2,151" data-tip="gpt-oss:20b · 4,096 context · Ollama 0.32.1: 14,152 MiB, 195.79 tok/s">
&lt;a class="vc-row__pick" href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-20" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">gpt-oss:20b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">MXFP4 · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:86.806%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>14,152&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>195.79&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-20" aria-label="Copy link to gpt-oss:20b, 4,096 context, Ollama 0.32.1, 2026-08-20" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>gpt-oss:20b&lt;/strong>
&lt;span class="vc-record__spec">MXFP4 · 4,096 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">14,152 MiB&lt;/b> resident on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="14,152 of 16,303 MiB in use, measured. 2,151 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:86.806%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:86.806%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">14,152 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">195.79 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">2,151 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 14,152&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">86.8&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>14,152 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured&lt;/dt>&lt;dd>&lt;time datetime="2026-08-20">2026-08-20&lt;/time> &lt;span class="vc-dim">from the file's footer notes&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model name in the file&lt;/dt>&lt;dd>gpt-oss:20b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>MXFP4. Not a column in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>4096 &lt;span class="vc-dim">from the file's settings note&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Offload&lt;/dt>&lt;dd>Full offload &lt;span class="vc-dim">from the file's settings note&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>195.79 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>194.59 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>195.8 · 195.7 · 196.3 · 196.1 · 195.7 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, short prompt, median&lt;/dt>&lt;dd>3744.3 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Prefill, long prompt&lt;/dt>&lt;dd>Empty in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>14152 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>8.6 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Desktop baseline at bench start&lt;/dt>&lt;dd>1642 MiB &lt;span class="vc-dim">one reading for the whole capture&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Driver&lt;/dt>&lt;dd>Not recorded in this file&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>13.82 GiB &lt;span class="vc-formula">Computed: 14,152 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of gpt-oss:20b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">194.4 tok/s&lt;/b> at &lt;b class="vc-m">292.4 W&lt;/b> board power, &lt;b class="vc-m">1.504 J&lt;/b> per token in the file. That is &lt;b class="vc-c">1,504 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 1.504 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08.csv" download>llm-server-compare-2026-08.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_total_mib_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-20">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-20" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-12" data-vc-row data-family="gptoss20b" data-quant="MXFP4" data-ctx="16384" data-runtime="ollama-0-32-1" data-vram="14355" data-decode="188.63" data-date="2026-08-12" data-model="gpt-oss:20b" data-x="88.051" data-y="47.157" data-status="" data-vram-label="14,355" data-headroom-label="1,948" data-tip="gpt-oss:20b · 16,384 context · Ollama 0.32.1: 14,355 MiB, 188.63 tok/s">
&lt;a class="vc-row__pick" href="#sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-12" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">gpt-oss:20b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">MXFP4 · 16,384 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:88.051%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>14,355&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>188.63&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-12" aria-label="Copy link to gpt-oss:20b, 16,384 context, Ollama 0.32.1, 2026-08-12" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>gpt-oss:20b&lt;/strong>
&lt;span class="vc-record__spec">MXFP4 · 16,384 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">14,355 MiB&lt;/b> resident on &lt;time datetime="2026-08-12">2026-08-12&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="14,355 of 16,303 MiB in use, measured. 1,948 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:88.051%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:88.051%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">14,355 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">188.63 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">1,948 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 14,355&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">88.1&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>14,355 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>gpt-oss:20b &lt;span class="vc-dim">digest 17052f91a42e&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>20.9B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>MXFP4&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>16384&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>503&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>188.63 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>9286.61 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>299.2 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>14355 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1658&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>187.73 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>10554.32 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>280.2 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>14355 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>14.02 GiB &lt;span class="vc-formula">Computed: 14,355 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of gpt-oss:20b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">194.4 tok/s&lt;/b> at &lt;b class="vc-m">292.4 W&lt;/b> board power, &lt;b class="vc-m">1.504 J&lt;/b> per token in the file. That is &lt;b class="vc-c">1,504 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 1.504 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-12">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-12" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-devstral-24b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" data-vc-row data-family="devstral24b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="ollama-0-32-1" data-vram="14997" data-decode="36.32" data-date="2026-08-26" data-model="devstral:24b" data-x="91.989" data-y="9.080" data-status="" data-vram-label="14,997" data-headroom-label="1,306" data-tip="devstral:24b · 4,096 context · Ollama 0.32.1: 14,997 MiB, 36.32 tok/s">
&lt;a class="vc-row__pick" href="#sku-devstral-24b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">devstral:24b&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:91.989%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>14,997&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>36.32&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-devstral-24b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" aria-label="Copy link to devstral:24b, 4,096 context, Ollama 0.32.1, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--whole" aria-hidden="true">&lt;/span>&lt;strong>devstral:24b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">14,997 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;p class="vc-note">Measured at a 4,096 context only. The dataset reports that an 8K attempt spilled and decode collapsed, but no row for that attempt was published, so it has no pin here. &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">Throughput dataset, coding models note&lt;/a>.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="14,997 of 16,303 MiB in use, measured. 1,306 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:91.989%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:91.989%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">14,997 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">36.32 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">1,306 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 14,997&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">92.0&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>14,997 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>devstral:24b &lt;span class="vc-dim">digest 9bd74193e939&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>23.6B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1694&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>36.32 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>9377.3 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>238.2 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>14997 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>2597&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>34.9 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>5334.83 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>241.7 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>14997 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>14.65 GiB &lt;span class="vc-formula">Computed: 14,997 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-devstral-24b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-devstral-24b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen3-coder-30b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" data-vc-row data-family="qwen3coder30b" data-quant="Q4_K_M" data-ctx="16384" data-runtime="ollama-0-32-1" data-vram="15003" data-decode="51.62" data-date="2026-08-26" data-model="qwen3-coder:30b" data-x="92.026" data-y="12.905" data-status="spill" data-vram-label="15,003" data-headroom-label="1,300" data-tip="qwen3-coder:30b · 16,384 context · Ollama 0.32.1: 15,003 MiB, 51.62 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen3-coder-30b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--spill" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen3-coder:30b&lt;/span>&lt;span class="vc-row__flag">Ran partly off the card&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 16,384 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:92.026%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>15,003&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>51.62&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen3-coder-30b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" aria-label="Copy link to qwen3-coder:30b, 16,384 context, Ollama 0.32.1, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--spill" aria-hidden="true">&lt;/span>&lt;strong>qwen3-coder:30b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 16,384 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">15,003 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;p class="vc-flag vc-flag--spill">&lt;span class="vc-flag__label">Ran partly off the card&lt;/span>&lt;/p>
&lt;p class="vc-note">The model file is larger than the card, so Ollama ran it partially offloaded with part of it in system RAM. The dataset warns that its decode rate depends on how much system RAM was free when it loaded. &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">Throughput dataset, coding models note&lt;/a>.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="15,003 of 16,303 MiB in use, measured. 1,300 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:92.026%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:92.026%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">15,003 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">51.62 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">1,300 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 15,003&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">92.0&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>15,003 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>qwen3-coder:30b &lt;span class="vc-dim">digest 06c1097efce0&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>30.5B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>16384&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>467&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>51.62 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>1524.77 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>219.9 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>15003 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1347&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>51.65 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>1928.14 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>188.9 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>15003 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>14.65 GiB &lt;span class="vc-formula">Computed: 15,003 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen3-coder-30b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen3-coder-30b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-llama3-2-3b-q4-k-m-ctx131072-ollama-0-32-15-2026-08-26-defaults" data-vc-row data-family="llama323b" data-quant="Q4_K_M" data-ctx="131072" data-runtime="ollama-0-32-15" data-vram="15084" data-decode="102.68" data-date="2026-08-26" data-model="llama3.2:3b" data-x="92.523" data-y="25.670" data-status="spill" data-vram-label="15,084" data-headroom-label="1,219" data-tip="llama3.2:3b · 131,072 context · Ollama 0.32.15 · defaults: 15,084 MiB, 102.68 tok/s">
&lt;a class="vc-row__pick" href="#sku-llama3-2-3b-q4-k-m-ctx131072-ollama-0-32-15-2026-08-26-defaults" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--spill" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">llama3.2:3b&lt;/span>&lt;span class="vc-row__flag">Ran partly off the card&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 131,072 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.15 &lt;span class="vc-dim">defaults&lt;/span>&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:92.523%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>15,084&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>102.68&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx131072-ollama-0-32-15-2026-08-26-defaults" aria-label="Copy link to llama3.2:3b, 131,072 context, Ollama 0.32.15, defaults, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--spill" aria-hidden="true">&lt;/span>&lt;strong>llama3.2:3b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 131,072 context · Ollama 0.32.15 · defaults&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">15,084 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.15. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;p class="vc-flag vc-flag--spill">&lt;span class="vc-flag__label">Ran partly off the card&lt;/span>&lt;/p>
&lt;p class="vc-note">The capture&amp;#39;s own ollama ps line reads 22%/78% CPU/GPU at context 131,072, so part of this model ran from system RAM.&lt;/p>
&lt;p class="vc-note">Ollama&amp;#39;s app-level context slider was set to 256k, which this model clamps to 131,072. The dataset describes the result as the KV cache spilling to the CPU. &lt;a href="https://techfuelhq.com/data/llm-server-compare/">Runtime comparison dataset&lt;/a>.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="15,084 of 16,303 MiB in use, measured. 1,219 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:92.523%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:92.523%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">15,084 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">102.68 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">1,219 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 15,084&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">92.5&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>15,084 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26T07:23:09.539508&amp;#43;00:00">2026-08-26 07:23:09&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.15&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Condition&lt;/dt>&lt;dd>defaults&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Schema&lt;/dt>&lt;dd>techfuelhq:lmstudio-vs-ollama:1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>llama3.2:3b&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--na">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M. Not a field in this file. Taken from the same model in the throughput CSV.&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context&lt;/dt>&lt;dd>131072 &lt;span class="vc-dim">from the capture's ollama ps line&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Processor split&lt;/dt>&lt;dd>22% CPU / 78% GPU &lt;span class="vc-dim">from the capture's ollama ps line&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Size reported by ollama ps&lt;/dt>&lt;dd>18 GB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runs&lt;/dt>&lt;dd>5&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (server counters)&lt;/dt>&lt;dd>102.68 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median (wall clock)&lt;/dt>&lt;dd>101.58 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Each run&lt;/dt>&lt;dd>97.57 · 99.85 · 103.59 · 102.68 · 103.21 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, long prompt, median&lt;/dt>&lt;dd>9998.8 tok/s at 434 prompt tokens&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory, median&lt;/dt>&lt;dd>15084 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory before the load&lt;/dt>&lt;dd>1067 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Added by loading the model&lt;/dt>&lt;dd>14,017 MiB &lt;span class="vc-formula">Computed: 15,084 − 1,067&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load&lt;/dt>&lt;dd>4.02 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Cold first request&lt;/dt>&lt;dd>4.2 s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>App RAM while loaded&lt;/dt>&lt;dd>4745.7 MB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>14.73 GiB &lt;span class="vc-formula">Computed: 15,084 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of llama3.2:3b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">318.3 tok/s&lt;/b> at &lt;b class="vc-m">265.2 W&lt;/b> board power, &lt;b class="vc-m">0.833 J&lt;/b> per token in the file. That is &lt;b class="vc-c">833 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 0.833 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/vram-cliff-raw/ollama-256k-slider-3b.json" download>ollama-256k-slider-3b.json&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_mb_median&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-llama3-2-3b-q4-k-m-ctx131072-ollama-0-32-15-2026-08-26-defaults">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx131072-ollama-0-32-15-2026-08-26-defaults" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-qwen3-coder-30b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" data-vc-row data-family="qwen3coder30b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="ollama-0-32-1" data-vram="15101" data-decode="61.89" data-date="2026-08-26" data-model="qwen3-coder:30b" data-x="92.627" data-y="15.473" data-status="spill" data-vram-label="15,101" data-headroom-label="1,202" data-tip="qwen3-coder:30b · 4,096 context · Ollama 0.32.1: 15,101 MiB, 61.89 tok/s">
&lt;a class="vc-row__pick" href="#sku-qwen3-coder-30b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--spill" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">qwen3-coder:30b&lt;/span>&lt;span class="vc-row__flag">Ran partly off the card&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:92.627%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>15,101&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>61.89&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-qwen3-coder-30b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" aria-label="Copy link to qwen3-coder:30b, 4,096 context, Ollama 0.32.1, 2026-08-26" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--spill" aria-hidden="true">&lt;/span>&lt;strong>qwen3-coder:30b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">15,101 MiB&lt;/b> resident on &lt;time datetime="2026-08-26">2026-08-26&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;p class="vc-flag vc-flag--spill">&lt;span class="vc-flag__label">Ran partly off the card&lt;/span>&lt;/p>
&lt;p class="vc-note">The model file is larger than the card, so Ollama ran it partially offloaded with part of it in system RAM. The dataset warns that its decode rate depends on how much system RAM was free when it loaded. &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">Throughput dataset, coding models note&lt;/a>.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="15,101 of 16,303 MiB in use, measured. 1,202 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:92.627%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:92.627%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">15,101 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">61.89 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">1,202 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 15,101&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">92.6&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>15,101 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>qwen3-coder:30b &lt;span class="vc-dim">digest 06c1097efce0&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>30.5B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>467&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>61.89 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>1744.18 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>197.7 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>15101 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1347&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>61.55 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>2368.71 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>177.2 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>15101 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>14.75 GiB &lt;span class="vc-formula">Computed: 15,101 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-qwen3-coder-30b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-qwen3-coder-30b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;li class="vc-row" id="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" data-vc-row data-family="llama323b" data-quant="Q4_K_M" data-ctx="4096" data-runtime="ollama-0-32-1" data-vram="15682" data-decode="311.96" data-date="2026-08-12" data-model="llama3.2:3b" data-x="96.191" data-y="77.990" data-status="shared" data-vram-label="15,682" data-headroom-label="621" data-tip="llama3.2:3b · 4,096 context · Ollama 0.32.1: 15,682 MiB, 311.96 tok/s">
&lt;a class="vc-row__pick" href="#sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" data-vc-pick>
&lt;span class="vc-row__model">&lt;span class="vc-glyph vc-glyph--shared" aria-hidden="true">&lt;/span>&lt;span class="vc-row__name">llama3.2:3b&lt;/span>&lt;span class="vc-row__flag">Reading includes another model&lt;/span>&lt;/span>
&lt;span class="vc-row__spec">Q4_K_M · 4,096 ctx&lt;/span>
&lt;span class="vc-row__rt">Ollama 0.32.1&lt;/span>
&lt;span class="vc-row__mem">&lt;span class="vc-bar" aria-hidden="true">&lt;span class="vc-bar__fill" style="--vc-w:96.191%">&lt;/span>&lt;/span>&lt;span class="vc-row__num">&lt;b>15,682&lt;/b> MiB&lt;/span>&lt;/span>
&lt;span class="vc-row__tps">&lt;b>311.96&lt;/b> tok/s&lt;/span>
&lt;span class="vc-row__date">&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/span>
&lt;/a>
&lt;button type="button" class="vc-btn vc-row__copy" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" aria-label="Copy link to llama3.2:3b, 4,096 context, Ollama 0.32.1, 2026-08-12" hidden>Copy link&lt;/button>
&lt;details class="vc-row__more" data-vc-more>
&lt;summary>Full measured record&lt;/summary>
&lt;div class="vc-record" data-vc-record>
&lt;p class="vc-record__title">&lt;span class="vc-glyph vc-glyph--shared" aria-hidden="true">&lt;/span>&lt;strong>llama3.2:3b&lt;/strong>
&lt;span class="vc-record__spec">Q4_K_M · 4,096 context · Ollama 0.32.1&lt;/span>&lt;/p>
&lt;p class="vc-record__sentence">Measured at &lt;b class="vc-m">15,682 MiB&lt;/b> resident on &lt;time datetime="2026-08-12">2026-08-12&lt;/time> with Ollama 0.32.1. That figure is the whole card as &lt;code>nvidia-smi&lt;/code> reported it, Windows desktop included.&lt;/p>
&lt;p class="vc-flag vc-flag--shared">&lt;span class="vc-flag__label">Reading includes another model&lt;/span>&lt;/p>
&lt;p class="vc-note">gpt-oss:20b was still loaded from the cell before this one, so this reading is the whole card with two models on it, not Llama 3.2 3B alone. The 16,384-context row from the same capture was read after the larger model had been evicted. &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">Throughput dataset, VRAM note&lt;/a>.&lt;/p>
&lt;div class="vc-gauge" role="img" aria-label="15,682 of 16,303 MiB in use, measured. 621 MiB left, computed.">
&lt;span class="vc-gauge__fill" style="--vc-w:96.191%">&lt;/span>
&lt;span class="vc-gauge__rest" style="--vc-w:96.191%">&lt;/span>
&lt;/div>
&lt;dl class="vc-kpis">
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Resident, whole card&lt;/dt>
&lt;dd class="vc-kpi__v">15,682 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--m">
&lt;dt>Decode&lt;/dt>
&lt;dd class="vc-kpi__v">311.96 &lt;small>tok/s&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Measured &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Left on the card&lt;/dt>
&lt;dd class="vc-kpi__v">621 &lt;small>MiB&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>16,303 − 15,682&lt;/span>&lt;/dd>
&lt;/div>
&lt;div class="vc-kpi vc-kpi--c">
&lt;dt>Share of the card&lt;/dt>
&lt;dd class="vc-kpi__v">96.2&lt;small>%&lt;/small>&lt;/dd>
&lt;dd class="vc-kpi__tag">Computed: &lt;span>15,682 ÷ 16,303&lt;/span>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;div class="vc-record__full">
&lt;p class="vc-record__sub">Full measured row&lt;/p>
&lt;dl class="vc-fields">
&lt;div class="vc-field">&lt;dt>Captured (UTC)&lt;/dt>&lt;dd>&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>GPU&lt;/dt>&lt;dd>NVIDIA GeForce RTX 5080&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Driver&lt;/dt>&lt;dd>610.88&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Runtime&lt;/dt>&lt;dd>Ollama 0.32.1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Method&lt;/dt>&lt;dd>llm-throughput-ollama-v1&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Model&lt;/dt>&lt;dd>llama3.2:3b &lt;span class="vc-dim">digest a80c4f17acd5&lt;/span>&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Parameters&lt;/dt>&lt;dd>3.2B&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Quantization&lt;/dt>&lt;dd>Q4_K_M&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Context (num_ctx)&lt;/dt>&lt;dd>4096&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 1&lt;/dt>&lt;dd>The row pinned on the map&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>471&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>311.96 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>18196.57 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>162.8 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>15682 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--head">&lt;dt>Prompt cell 2&lt;/dt>&lt;dd>Same configuration, longer prompt&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prompt tokens&lt;/dt>&lt;dd>1657&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Repetitions&lt;/dt>&lt;dd>3&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Decode, median&lt;/dt>&lt;dd>298.21 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Prefill, median&lt;/dt>&lt;dd>17681.08 tok/s&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Load, median&lt;/dt>&lt;dd>156.2 ms&lt;/dd>&lt;/div>
&lt;div class="vc-field">&lt;dt>Whole-card memory after the cell&lt;/dt>&lt;dd>15682 MiB&lt;/dd>&lt;/div>
&lt;div class="vc-field vc-field--c">&lt;dt>Resident in GiB&lt;/dt>&lt;dd>15.31 GiB &lt;span class="vc-formula">Computed: 15,682 ÷ 1,024&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;div class="vc-energy-note">
&lt;p class="vc-record__sub">Energy for this model, from its own power run&lt;/p>
&lt;p>A separate run of llama3.2:3b on &lt;time datetime="2026-08-20">2026-08-20&lt;/time> (UTC), stock power limit: &lt;b class="vc-m">318.3 tok/s&lt;/b> at &lt;b class="vc-m">265.2 W&lt;/b> board power, &lt;b class="vc-m">0.833 J&lt;/b> per token in the file. That is &lt;b class="vc-c">833 J per 1,000 tokens&lt;/b> &lt;span class="vc-formula">Computed: 0.833 × 1,000&lt;/span>. The power file records no context length, driver or runtime version, so read it as the model's energy at stock, not this row's.&lt;/p>
&lt;/div>
&lt;p class="vc-record__src">Source file: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a> &lt;span class="vc-dim">(column &lt;code>vram_resident_mib&lt;/code>)&lt;/span>. Method and caveats: &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/">RTX 5080 LLM throughput dataset&lt;/a>.&lt;/p>
&lt;/div>
&lt;p class="vc-record__actions">
&lt;a class="vc-btn vc-record__jump" href="#sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12">Full record in the list&lt;/a>
&lt;button type="button" class="vc-btn" data-vc-copy="sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12" hidden>Copy link to this configuration&lt;/button>
&lt;/p>
&lt;/div>
&lt;/details>
&lt;/li>
&lt;/ol>
&lt;p class="vc-empty" data-vc-empty hidden>No measured configuration matches those filters. That combination was not on the bench, and I do not estimate here. For an estimate, use the &lt;a href="https://techfuelhq.com/tools/llm-vram-calculator/">LLM VRAM calculator&lt;/a>.&lt;/p>
&lt;/section>
&lt;/div>
&lt;script defer src="https://techfuelhq.com/js/vram-cliff.bundle.min.b3281adf7a0a41c57cc0a469a1892850eeea16ccdf9abb6665727463862d8fba.js" integrity="sha256-syga33oKQcV8wKRpoYkoUO7qFszfmrtmZXJ0Y4Ytj7o=">&lt;/script>
&lt;h2 id="how-to-read-it">How to read it&lt;/h2>
&lt;p>The map answers a narrow question: what did this model, at this context length, on this runtime version, take on a 16 GB card, and what speed came with it. Each record reads &amp;ldquo;measured at so many MiB resident on a date with a runtime version&amp;rdquo; because that is all a measurement can say. It is not a promise that the same model fits on your card today.&lt;/p>
&lt;p>The line along the bottom is the card, from zero to the total it reports to &lt;code>nvidia-smi&lt;/code>. A pin&amp;rsquo;s position across is the memory in use on the whole card while that model was loaded, Windows desktop included, and its height is the decode rate. Select a pin and the line fills to it in the measured colour. The hatched remainder is headroom, which I compute by subtracting.&lt;/p>
&lt;p>A dashed connector joins the same model, runtime and capture at two context lengths. Flat means memory grew and speed held; a drop means the model stopped fitting. A ring is a run recorded as partly off the card. A diamond is a reading taken while another model was still loaded, so it overstates that model.&lt;/p>
&lt;h2 id="where-the-cliff-shows-up">Where the cliff shows up&lt;/h2>
&lt;p>The cliff is not a memory number. In these files, a model that sits whole on the card decodes at the same speed whether it uses a third of the memory or nearly all of it. Speed falls when part of the model no longer fits and runs from system RAM instead.&lt;/p>
&lt;div class="vc vc--part">
&lt;p class="vc-tablenote" id="vc-pairs-note">Each row is the same model, runtime version and capture at two context lengths, and both ends are measured rows. &lt;span class="vc-c">Memory change&lt;/span> is the second reading minus the first. &lt;span class="vc-c">Decode change&lt;/span> is (second − first) ÷ first.&lt;/p>
&lt;div class="vc-rows vc-rows--pairs" role="table" aria-label="Context pairs" aria-describedby="vc-pairs-note">
&lt;div class="vc-rows__head" role="row">
&lt;span role="columnheader">Model and runtime&lt;/span>
&lt;span role="columnheader">Context&lt;/span>
&lt;span role="columnheader">Resident MiB, measured&lt;/span>
&lt;span role="columnheader">Memory change, computed&lt;/span>
&lt;span role="columnheader">Decode tok/s, measured&lt;/span>
&lt;span role="columnheader">Decode change, computed&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>llama3.2:3b&lt;/strong>
&lt;span class="vc-rows__sub">Ollama 0.32.15, defaults · &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>&lt;span class="vc-rows__sub vc-rows__sub--flag">131,072: ran partly off the card&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Context">&lt;span>&lt;a href="#sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults">4,096&lt;/a> → &lt;a href="#sku-llama3-2-3b-q4-k-m-ctx131072-ollama-0-32-15-2026-08-26-defaults">131,072&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Resident MiB">&lt;span>&lt;span class="vc-m">3,760&lt;/span> → &lt;span class="vc-m">15,084&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Memory change">&lt;span>&lt;span class="vc-c">&amp;#43;11,324&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode tok/s">&lt;span>&lt;span class="vc-m">351.22&lt;/span> → &lt;span class="vc-m">102.68&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode change">&lt;span>&lt;span class="vc-c">−70.8%&lt;/span>&lt;span class="vc-fall" aria-hidden="true">&lt;span class="vc-fall__fill" style="--vc-w:100.000%">&lt;/span>&lt;/span>&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>qwen3-coder:30b&lt;/strong>
&lt;span class="vc-rows__sub">Ollama 0.32.1 · &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>&lt;span class="vc-rows__sub vc-rows__sub--flag">16,384: ran partly off the card&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Context">&lt;span>&lt;a href="#sku-qwen3-coder-30b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26">4,096&lt;/a> → &lt;a href="#sku-qwen3-coder-30b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26">16,384&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Resident MiB">&lt;span>&lt;span class="vc-m">15,101&lt;/span> → &lt;span class="vc-m">15,003&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Memory change">&lt;span>&lt;span class="vc-c">−98&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode tok/s">&lt;span>&lt;span class="vc-m">61.89&lt;/span> → &lt;span class="vc-m">51.62&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode change">&lt;span>&lt;span class="vc-c">−16.6%&lt;/span>&lt;span class="vc-fall" aria-hidden="true">&lt;span class="vc-fall__fill" style="--vc-w:23.449%">&lt;/span>&lt;/span>&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>gpt-oss:20b&lt;/strong>
&lt;span class="vc-rows__sub">Ollama 0.32.1 · &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Context">&lt;span>&lt;a href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-12">4,096&lt;/a> → &lt;a href="#sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-12">16,384&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Resident MiB">&lt;span>&lt;span class="vc-m">14,067&lt;/span> → &lt;span class="vc-m">14,355&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Memory change">&lt;span>&lt;span class="vc-c">&amp;#43;288&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode tok/s">&lt;span>&lt;span class="vc-m">190.14&lt;/span> → &lt;span class="vc-m">188.63&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode change">&lt;span>&lt;span class="vc-c">−0.8%&lt;/span>&lt;span class="vc-fall" aria-hidden="true">&lt;span class="vc-fall__fill" style="--vc-w:1.122%">&lt;/span>&lt;/span>&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>qwen2.5-coder:14b&lt;/strong>
&lt;span class="vc-rows__sub">Ollama 0.32.1 · &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Context">&lt;span>&lt;a href="#sku-qwen2-5-coder-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26">4,096&lt;/a> → &lt;a href="#sku-qwen2-5-coder-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26">16,384&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Resident MiB">&lt;span>&lt;span class="vc-m">10,169&lt;/span> → &lt;span class="vc-m">12,485&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Memory change">&lt;span>&lt;span class="vc-c">&amp;#43;2,316&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode tok/s">&lt;span>&lt;span class="vc-m">94.89&lt;/span> → &lt;span class="vc-m">94.49&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode change">&lt;span>&lt;span class="vc-c">−0.4%&lt;/span>&lt;span class="vc-fall" aria-hidden="true">&lt;span class="vc-fall__fill" style="--vc-w:0.596%">&lt;/span>&lt;/span>&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>qwen2.5:7b&lt;/strong>
&lt;span class="vc-rows__sub">Ollama 0.32.1 · &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Context">&lt;span>&lt;a href="#sku-qwen2-5-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12">4,096&lt;/a> → &lt;a href="#sku-qwen2-5-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12">16,384&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Resident MiB">&lt;span>&lt;span class="vc-m">6,190&lt;/span> → &lt;span class="vc-m">7,022&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Memory change">&lt;span>&lt;span class="vc-c">&amp;#43;832&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode tok/s">&lt;span>&lt;span class="vc-m">180.02&lt;/span> → &lt;span class="vc-m">179.66&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode change">&lt;span>&lt;span class="vc-c">−0.2%&lt;/span>&lt;span class="vc-fall" aria-hidden="true">&lt;span class="vc-fall__fill" style="--vc-w:0.283%">&lt;/span>&lt;/span>&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>llama3.2:3b&lt;/strong>
&lt;span class="vc-rows__sub">Ollama 0.32.1 · &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/span>&lt;span class="vc-rows__sub vc-rows__sub--flag">4,096: reading includes another model&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Context">&lt;span>&lt;a href="#sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12">4,096&lt;/a> → &lt;a href="#sku-llama3-2-3b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12">16,384&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Resident MiB">&lt;span>&lt;span class="vc-m">15,682&lt;/span> → &lt;span class="vc-m">5,495&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Memory change">&lt;span>&lt;span class="vc-dim">Not comparable&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode tok/s">&lt;span>&lt;span class="vc-m">311.96&lt;/span> → &lt;span class="vc-m">312.89&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode change">&lt;span>&lt;span class="vc-c">&amp;#43;0.3%&lt;/span>&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>qwen2.5:14b&lt;/strong>
&lt;span class="vc-rows__sub">Ollama 0.32.1 · &lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Context">&lt;span>&lt;a href="#sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-12">4,096&lt;/a> → &lt;a href="#sku-qwen2-5-14b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-12">16,384&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Resident MiB">&lt;span>&lt;span class="vc-m">10,841&lt;/span> → &lt;span class="vc-m">13,157&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Memory change">&lt;span>&lt;span class="vc-c">&amp;#43;2,316&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode tok/s">&lt;span>&lt;span class="vc-m">96.65&lt;/span> → &lt;span class="vc-m">97.02&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode change">&lt;span>&lt;span class="vc-c">&amp;#43;0.4%&lt;/span>&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>qwen2.5-coder:7b&lt;/strong>
&lt;span class="vc-rows__sub">Ollama 0.32.1 · &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Context">&lt;span>&lt;a href="#sku-qwen2-5-coder-7b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26">4,096&lt;/a> → &lt;a href="#sku-qwen2-5-coder-7b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26">16,384&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Resident MiB">&lt;span>&lt;span class="vc-m">5,671&lt;/span> → &lt;span class="vc-m">6,503&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Memory change">&lt;span>&lt;span class="vc-c">&amp;#43;832&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode tok/s">&lt;span>&lt;span class="vc-m">173.73&lt;/span> → &lt;span class="vc-m">174.58&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode change">&lt;span>&lt;span class="vc-c">&amp;#43;0.5%&lt;/span>&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>gpt-oss:20b&lt;/strong>
&lt;span class="vc-rows__sub">Ollama 0.32.1 · &lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Context">&lt;span>&lt;a href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-26">4,096&lt;/a> → &lt;a href="#sku-gpt-oss-20b-mxfp4-ctx16384-ollama-0-32-1-2026-08-26">16,384&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Resident MiB">&lt;span>&lt;span class="vc-m">13,381&lt;/span> → &lt;span class="vc-m">13,683&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Memory change">&lt;span>&lt;span class="vc-c">&amp;#43;302&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode tok/s">&lt;span>&lt;span class="vc-m">181.50&lt;/span> → &lt;span class="vc-m">183.00&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode change">&lt;span>&lt;span class="vc-c">&amp;#43;0.8%&lt;/span>&lt;/span>&lt;/span>
&lt;/div>
&lt;/div>
&lt;/div>
&lt;p>The table has two rows where raising the context cost speed, and both are runs that left the card. Llama 3.2 3B is the small model in this set, and a large enough context still pushed it over. Qwen3-Coder 30B never fit whole, so its memory reading barely moved and its speed did.&lt;/p>
&lt;p>Every other pair held its decode rate within one percent while the context quadrupled. What they paid was memory, and how much depended on the model: the two 14B Qwen models paid the most, and gpt-oss:20b, the largest of them by parameter count, paid the least.&lt;/p>
&lt;p>What the files do not hold is a dense model caught in the act of falling off. The throughput dataset says Devstral 24B collapsed when I tried it at an 8K context, but that attempt was never written to the CSV, so there is no pin for it and I have not drawn one.&lt;/p>
&lt;h2 id="energy-per-thousand-tokens">Energy per thousand tokens&lt;/h2>
&lt;div class="vc vc--part">
&lt;ol class="vc-energy">
&lt;li class="vc-energy__row">
&lt;p class="vc-energy__name">&lt;strong>llama3.2:3b&lt;/strong> &lt;span class="vc-dim">Q4_K_M · named “Llama 3.2 3B” in the file · run logged &lt;time datetime="2026-08-20T00:15:26&amp;#43;00:00">2026-08-20 00:15&lt;/time> UTC&lt;/span>&lt;/p>
&lt;div class="vc-energy__lead">
&lt;span class="vc-energy__bar" aria-hidden="true">&lt;span class="vc-energy__fill" style="--vc-w:26.411%">&lt;/span>&lt;/span>
&lt;p class="vc-energy__main">&lt;b class="vc-c">833 J&lt;/b> per 1,000 tokens &lt;span class="vc-formula">Computed: 0.833 J per token × 1,000&lt;/span>&lt;/p>
&lt;/div>
&lt;dl class="vc-energy__facts">
&lt;div>&lt;dt>Decode, median of 3&lt;/dt>&lt;dd>&lt;span class="vc-m">318.3&lt;/span> tok/s&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Board power, median while loaded&lt;/dt>&lt;dd>&lt;span class="vc-m">265.2&lt;/span> W&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Tokens per joule, as filed&lt;/dt>&lt;dd>&lt;span class="vc-m">1.2&lt;/span>&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Joules per token, as filed&lt;/dt>&lt;dd>&lt;span class="vc-m">0.833&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;details class="vc-energy__more">
&lt;summary>More from the power file&lt;/summary>
&lt;dl class="vc-energy__facts">
&lt;div>&lt;dt>Watt-hours per 1,000 tokens&lt;/dt>&lt;dd>&lt;span class="vc-c">0.231&lt;/span> Wh &lt;span class="vc-formula">Computed: 231.0 Wh per million ÷ 1,000&lt;/span>&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Decode, slowest and fastest run&lt;/dt>&lt;dd>&lt;span class="vc-m">315.5&lt;/span> to &lt;span class="vc-m">318.5&lt;/span> tok/s&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Board power, peak&lt;/dt>&lt;dd>&lt;span class="vc-m">307.78&lt;/span> W&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Memory in use, median&lt;/dt>&lt;dd>&lt;span class="vc-m">3,590&lt;/span> MiB&lt;/dd>&lt;/div>
&lt;div>&lt;dt>GPU temperature, median&lt;/dt>&lt;dd>&lt;span class="vc-m">49.0&lt;/span> °C&lt;/dd>&lt;/div>
&lt;div>&lt;dt>GPU load, median&lt;/dt>&lt;dd>&lt;span class="vc-m">82.0&lt;/span>%&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Telemetry samples while loaded&lt;/dt>&lt;dd>&lt;span class="vc-m">9&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;/details>
&lt;/li>
&lt;li class="vc-energy__row">
&lt;p class="vc-energy__name">&lt;strong>qwen2.5:7b&lt;/strong> &lt;span class="vc-dim">Q4_K_M · named “Qwen 2.5 7B” in the file · run logged &lt;time datetime="2026-08-20T00:16:03&amp;#43;00:00">2026-08-20 00:16&lt;/time> UTC&lt;/span>&lt;/p>
&lt;div class="vc-energy__lead">
&lt;span class="vc-energy__bar" aria-hidden="true">&lt;span class="vc-energy__fill" style="--vc-w:59.797%">&lt;/span>&lt;/span>
&lt;p class="vc-energy__main">&lt;b class="vc-c">1,886 J&lt;/b> per 1,000 tokens &lt;span class="vc-formula">Computed: 1.886 J per token × 1,000&lt;/span>&lt;/p>
&lt;/div>
&lt;dl class="vc-energy__facts">
&lt;div>&lt;dt>Decode, median of 3&lt;/dt>&lt;dd>&lt;span class="vc-m">182.2&lt;/span> tok/s&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Board power, median while loaded&lt;/dt>&lt;dd>&lt;span class="vc-m">343.6&lt;/span> W&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Tokens per joule, as filed&lt;/dt>&lt;dd>&lt;span class="vc-m">0.53&lt;/span>&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Joules per token, as filed&lt;/dt>&lt;dd>&lt;span class="vc-m">1.886&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;details class="vc-energy__more">
&lt;summary>More from the power file&lt;/summary>
&lt;dl class="vc-energy__facts">
&lt;div>&lt;dt>Watt-hours per 1,000 tokens&lt;/dt>&lt;dd>&lt;span class="vc-c">0.524&lt;/span> Wh &lt;span class="vc-formula">Computed: 524.0 Wh per million ÷ 1,000&lt;/span>&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Decode, slowest and fastest run&lt;/dt>&lt;dd>&lt;span class="vc-m">182.1&lt;/span> to &lt;span class="vc-m">182.3&lt;/span> tok/s&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Board power, peak&lt;/dt>&lt;dd>&lt;span class="vc-m">346.08&lt;/span> W&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Memory in use, median&lt;/dt>&lt;dd>&lt;span class="vc-m">5,665&lt;/span> MiB&lt;/dd>&lt;/div>
&lt;div>&lt;dt>GPU temperature, median&lt;/dt>&lt;dd>&lt;span class="vc-m">52.0&lt;/span> °C&lt;/dd>&lt;/div>
&lt;div>&lt;dt>GPU load, median&lt;/dt>&lt;dd>&lt;span class="vc-m">88.0&lt;/span>%&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Telemetry samples while loaded&lt;/dt>&lt;dd>&lt;span class="vc-m">14&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;/details>
&lt;/li>
&lt;li class="vc-energy__row">
&lt;p class="vc-energy__name">&lt;strong>qwen2.5:14b&lt;/strong> &lt;span class="vc-dim">Q4_K_M · named “Qwen 2.5 14B” in the file · run logged &lt;time datetime="2026-08-20T00:16:50&amp;#43;00:00">2026-08-20 00:16&lt;/time> UTC&lt;/span>&lt;/p>
&lt;div class="vc-energy__lead">
&lt;span class="vc-energy__bar" aria-hidden="true">&lt;span class="vc-energy__fill" style="--vc-w:100.000%">&lt;/span>&lt;/span>
&lt;p class="vc-energy__main">&lt;b class="vc-c">3,154 J&lt;/b> per 1,000 tokens &lt;span class="vc-formula">Computed: 3.154 J per token × 1,000&lt;/span>&lt;/p>
&lt;/div>
&lt;dl class="vc-energy__facts">
&lt;div>&lt;dt>Decode, median of 3&lt;/dt>&lt;dd>&lt;span class="vc-m">98.8&lt;/span> tok/s&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Board power, median while loaded&lt;/dt>&lt;dd>&lt;span class="vc-m">311.6&lt;/span> W&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Tokens per joule, as filed&lt;/dt>&lt;dd>&lt;span class="vc-m">0.317&lt;/span>&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Joules per token, as filed&lt;/dt>&lt;dd>&lt;span class="vc-m">3.154&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;details class="vc-energy__more">
&lt;summary>More from the power file&lt;/summary>
&lt;dl class="vc-energy__facts">
&lt;div>&lt;dt>Watt-hours per 1,000 tokens&lt;/dt>&lt;dd>&lt;span class="vc-c">0.876&lt;/span> Wh &lt;span class="vc-formula">Computed: 876.0 Wh per million ÷ 1,000&lt;/span>&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Decode, slowest and fastest run&lt;/dt>&lt;dd>&lt;span class="vc-m">98.6&lt;/span> to &lt;span class="vc-m">98.8&lt;/span> tok/s&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Board power, peak&lt;/dt>&lt;dd>&lt;span class="vc-m">319.69&lt;/span> W&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Memory in use, median&lt;/dt>&lt;dd>&lt;span class="vc-m">10,171&lt;/span> MiB&lt;/dd>&lt;/div>
&lt;div>&lt;dt>GPU temperature, median&lt;/dt>&lt;dd>&lt;span class="vc-m">50.0&lt;/span> °C&lt;/dd>&lt;/div>
&lt;div>&lt;dt>GPU load, median&lt;/dt>&lt;dd>&lt;span class="vc-m">93.0&lt;/span>%&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Telemetry samples while loaded&lt;/dt>&lt;dd>&lt;span class="vc-m">27&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;/details>
&lt;/li>
&lt;li class="vc-energy__row">
&lt;p class="vc-energy__name">&lt;strong>gpt-oss:20b&lt;/strong> &lt;span class="vc-dim">MXFP4 · named “gpt-oss 20B” in the file · run logged &lt;time datetime="2026-08-20T00:17:38&amp;#43;00:00">2026-08-20 00:17&lt;/time> UTC&lt;/span>&lt;/p>
&lt;div class="vc-energy__lead">
&lt;span class="vc-energy__bar" aria-hidden="true">&lt;span class="vc-energy__fill" style="--vc-w:47.685%">&lt;/span>&lt;/span>
&lt;p class="vc-energy__main">&lt;b class="vc-c">1,504 J&lt;/b> per 1,000 tokens &lt;span class="vc-formula">Computed: 1.504 J per token × 1,000&lt;/span>&lt;/p>
&lt;/div>
&lt;dl class="vc-energy__facts">
&lt;div>&lt;dt>Decode, median of 3&lt;/dt>&lt;dd>&lt;span class="vc-m">194.4&lt;/span> tok/s&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Board power, median while loaded&lt;/dt>&lt;dd>&lt;span class="vc-m">292.4&lt;/span> W&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Tokens per joule, as filed&lt;/dt>&lt;dd>&lt;span class="vc-m">0.665&lt;/span>&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Joules per token, as filed&lt;/dt>&lt;dd>&lt;span class="vc-m">1.504&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;details class="vc-energy__more">
&lt;summary>More from the power file&lt;/summary>
&lt;dl class="vc-energy__facts">
&lt;div>&lt;dt>Watt-hours per 1,000 tokens&lt;/dt>&lt;dd>&lt;span class="vc-c">0.418&lt;/span> Wh &lt;span class="vc-formula">Computed: 418.0 Wh per million ÷ 1,000&lt;/span>&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Decode, slowest and fastest run&lt;/dt>&lt;dd>&lt;span class="vc-m">194.3&lt;/span> to &lt;span class="vc-m">194.5&lt;/span> tok/s&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Board power, peak&lt;/dt>&lt;dd>&lt;span class="vc-m">294.86&lt;/span> W&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Memory in use, median&lt;/dt>&lt;dd>&lt;span class="vc-m">13,381&lt;/span> MiB&lt;/dd>&lt;/div>
&lt;div>&lt;dt>GPU temperature, median&lt;/dt>&lt;dd>&lt;span class="vc-m">51.0&lt;/span> °C&lt;/dd>&lt;/div>
&lt;div>&lt;dt>GPU load, median&lt;/dt>&lt;dd>&lt;span class="vc-m">84.0&lt;/span>%&lt;/dd>&lt;/div>
&lt;div>&lt;dt>Telemetry samples while loaded&lt;/dt>&lt;dd>&lt;span class="vc-m">18&lt;/span>&lt;/dd>&lt;/div>
&lt;/dl>
&lt;/details>
&lt;/li>
&lt;/ol>
&lt;/div>
&lt;p>These four runs are a separate capture from the map: one short prompt, three iterations per model, board power sampled once a second and counted only while the GPU was at least half loaded. They were taken at the card&amp;rsquo;s stock 448 W power limit, which none of the runs reached. Board power is the graphics card alone, not the wall.&lt;/p>
&lt;p>The power file records no context length, driver or runtime version, which is why these runs are not pinned on the map. Its dataset page gives the runtime as Ollama 0.32.1.&lt;/p>
&lt;p>There is no undervolt or power-limit comparison here because I have not measured one for language models. My undervolt database holds one row for this card and it is a stock 3DMark baseline. Method and the idle-power finding are on the &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-power-efficiency/">power efficiency dataset&lt;/a>.&lt;/p>
&lt;h2 id="versions-on-the-bench-and-how-stale-they-are">Versions on the bench, and how stale they are&lt;/h2>
&lt;div class="vc vc--part">
&lt;p class="vc-tablenote" id="vc-versions-note">Driver and runtime versions per capture, exactly as each file records them. Where a file is silent, the cell says so.&lt;/p>
&lt;div class="vc-rows vc-rows--versions" role="table" aria-label="Versions per capture" aria-describedby="vc-versions-note">
&lt;div class="vc-rows__head" role="row">
&lt;span role="columnheader">Captured&lt;/span>
&lt;span role="columnheader">File&lt;/span>
&lt;span role="columnheader">GPU driver&lt;/span>
&lt;span role="columnheader">Runtime versions&lt;/span>
&lt;span role="columnheader">Rows used here&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>&lt;time datetime="2026-08-12">2026-08-12&lt;/time>&lt;/strong>&lt;/span>
&lt;span role="cell" data-label="File">&lt;span>&lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="GPU driver">&lt;span>&lt;span class="vc-m">610.88&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Runtime versions">&lt;span>Ollama 0.32.1&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Rows used here">&lt;span>8 configurations&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>&lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/strong>&lt;/span>
&lt;span role="cell" data-label="File">&lt;span>&lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08.csv" download>llm-server-compare-2026-08.csv&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="GPU driver">&lt;span>&lt;span class="vc-dim">Not recorded in this file&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Runtime versions">&lt;span>llama.cpp b10507, Ollama 0.32.1&lt;span class="vc-rows__sub">llama.cpp b10507: (upstream GGUF)&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Rows used here">&lt;span>6 configurations&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>&lt;time datetime="2026-08-20">2026-08-20&lt;/time>&lt;/strong>&lt;/span>
&lt;span role="cell" data-label="File">&lt;span>&lt;a href="https://techfuelhq.com/data/rtx-5080-llm-power-efficiency.csv" download>rtx-5080-llm-power-efficiency.csv&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="GPU driver">&lt;span>&lt;span class="vc-dim">Not recorded in this file&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Runtime versions">&lt;span>&lt;span class="vc-dim">Not recorded in this file&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Rows used here">&lt;span>4 power rows&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/strong>&lt;/span>
&lt;span role="cell" data-label="File">&lt;span>&lt;a href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download>llm-server-compare-2026-08-26-lmstudio.csv&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="GPU driver">&lt;span>&lt;span class="vc-dim">Not recorded in this file&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Runtime versions">&lt;span>LM Studio 0.4.21, Ollama 0.32.15&lt;span class="vc-rows__sub">Ollama 0.32.15: vendored llama.cpp 9d77fa172&lt;/span>&lt;span class="vc-rows__sub">LM Studio 0.4.21: llama.cpp-win-x86_64-nvidia-cuda12-avx2@2.29.1&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Rows used here">&lt;span>12 configurations&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/strong>&lt;/span>
&lt;span role="cell" data-label="File">&lt;span>&lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download>rtx-5080-llm-throughput.csv&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="GPU driver">&lt;span>&lt;span class="vc-m">610.88&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Runtime versions">&lt;span>Ollama 0.32.1&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Rows used here">&lt;span>9 configurations&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>&lt;time datetime="2026-08-26">2026-08-26&lt;/time>&lt;/strong>&lt;/span>
&lt;span role="cell" data-label="File">&lt;span>&lt;a href="https://techfuelhq.com/data/vram-cliff-raw/ollama-256k-slider-3b.json" download>ollama-256k-slider-3b.json&lt;/a>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="GPU driver">&lt;span>&lt;span class="vc-m">610.88&lt;/span>&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Runtime versions">&lt;span>Ollama 0.32.15&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Rows used here">&lt;span>1 configuration&lt;/span>&lt;/span>
&lt;/div>
&lt;/div>
&lt;p class="vc-tablenote" id="vc-drift-note">The same model at the same context on two Ollama versions. &lt;span class="vc-c">Decode change&lt;/span> is (later − earlier) ÷ earlier.&lt;/p>
&lt;div class="vc-rows vc-rows--drift" role="table" aria-label="The same rows on two Ollama versions" aria-describedby="vc-drift-note">
&lt;div class="vc-rows__head" role="row">
&lt;span role="columnheader">Model&lt;/span>
&lt;span role="columnheader">Earlier row, measured&lt;/span>
&lt;span role="columnheader">Later row, measured&lt;/span>
&lt;span role="columnheader">Decode change, computed&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>llama3.2:3b&lt;/strong>&lt;span class="vc-rows__sub">4,096 context&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Earlier row">&lt;span>&lt;a href="#sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20">Ollama 0.32.1&lt;/a>, &lt;time datetime="2026-08-20">2026-08-20&lt;/time>: &lt;span class="vc-m">318.51&lt;/span> tok/s&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Later row">&lt;span>&lt;a href="#sku-llama3-2-3b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults">Ollama 0.32.15&lt;/a>, &lt;time datetime="2026-08-26">2026-08-26&lt;/time>: &lt;span class="vc-m">351.22&lt;/span> tok/s&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode change">&lt;span>&lt;span class="vc-c">&amp;#43;10.3%&lt;/span>&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>qwen2.5:14b&lt;/strong>&lt;span class="vc-rows__sub">4,096 context&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Earlier row">&lt;span>&lt;a href="#sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-20">Ollama 0.32.1&lt;/a>, &lt;time datetime="2026-08-20">2026-08-20&lt;/time>: &lt;span class="vc-m">99.43&lt;/span> tok/s&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Later row">&lt;span>&lt;a href="#sku-qwen2-5-14b-q4-k-m-ctx4096-ollama-0-32-15-2026-08-26-defaults">Ollama 0.32.15&lt;/a>, &lt;time datetime="2026-08-26">2026-08-26&lt;/time>: &lt;span class="vc-m">102.25&lt;/span> tok/s&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode change">&lt;span>&lt;span class="vc-c">&amp;#43;2.8%&lt;/span>&lt;/span>&lt;/span>
&lt;/div>
&lt;div class="vc-rows__row" role="row">
&lt;span class="vc-rows__lead" role="rowheader">&lt;strong>gpt-oss:20b&lt;/strong>&lt;span class="vc-rows__sub">4,096 context&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Earlier row">&lt;span>&lt;a href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-1-2026-08-20">Ollama 0.32.1&lt;/a>, &lt;time datetime="2026-08-20">2026-08-20&lt;/time>: &lt;span class="vc-m">195.79&lt;/span> tok/s&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Later row">&lt;span>&lt;a href="#sku-gpt-oss-20b-mxfp4-ctx4096-ollama-0-32-15-2026-08-26-defaults">Ollama 0.32.15&lt;/a>, &lt;time datetime="2026-08-26">2026-08-26&lt;/time>: &lt;span class="vc-m">213.54&lt;/span> tok/s&lt;/span>&lt;/span>
&lt;span role="cell" data-label="Decode change">&lt;span>&lt;span class="vc-c">&amp;#43;9.1%&lt;/span>&lt;/span>&lt;/span>
&lt;/div>
&lt;/div>
&lt;/div>
&lt;p>Those are the versions that were installed on the capture dates. Drivers and runtimes have both moved since, and I have not re-run this matrix on newer ones. Read every pin as true for its date and versions, and expect a current install to differ.&lt;/p>
&lt;p>The second table is why I say that plainly. Two captures six days apart put the same three models on two Ollama versions, and all three decoded faster on the later one. The &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a> notes that the earlier capture had less control over background load, so not all of that gap is the version. Either way, a few percent between runtimes does not survive an update.&lt;/p>
&lt;h2 id="what-the-data-covers">What the data covers&lt;/h2>
&lt;div class="vc vc--part">
&lt;dl class="vc-cover">
&lt;div class="vc-cover__row">
&lt;dt>Model tags &lt;span class="vc-dim">(8)&lt;/span>&lt;/dt>
&lt;dd>&lt;ul class="vc-chips">&lt;li>&lt;strong>llama3.2:3b&lt;/strong> 3.2B · Q4_K_M &lt;span class="vc-dim">9 configurations&lt;/span>&lt;/li>&lt;li>&lt;strong>qwen2.5-coder:7b&lt;/strong> 7.6B · Q4_K_M &lt;span class="vc-dim">2 configurations&lt;/span>&lt;/li>&lt;li>&lt;strong>qwen2.5:7b&lt;/strong> 7.6B · Q4_K_M &lt;span class="vc-dim">2 configurations&lt;/span>&lt;/li>&lt;li>&lt;strong>qwen2.5-coder:14b&lt;/strong> 14.8B · Q4_K_M &lt;span class="vc-dim">2 configurations&lt;/span>&lt;/li>&lt;li>&lt;strong>qwen2.5:14b&lt;/strong> 14.8B · Q4_K_M &lt;span class="vc-dim">8 configurations&lt;/span>&lt;/li>&lt;li>&lt;strong>gpt-oss:20b&lt;/strong> 20.9B · MXFP4 &lt;span class="vc-dim">10 configurations&lt;/span>&lt;/li>&lt;li>&lt;strong>devstral:24b&lt;/strong> 23.6B · Q4_K_M &lt;span class="vc-dim">1 configuration&lt;/span>&lt;/li>&lt;li>&lt;strong>qwen3-coder:30b&lt;/strong> 30.5B · Q4_K_M &lt;span class="vc-dim">2 configurations&lt;/span>&lt;/li>&lt;/ul>&lt;/dd>
&lt;/div>
&lt;div class="vc-cover__row">
&lt;dt>Quantizations &lt;span class="vc-dim">(2)&lt;/span>&lt;/dt>
&lt;dd>&lt;ul class="vc-chips">&lt;li>&lt;strong>MXFP4&lt;/strong> &lt;span class="vc-dim">10&lt;/span>&lt;/li>&lt;li>&lt;strong>Q4_K_M&lt;/strong> &lt;span class="vc-dim">26&lt;/span>&lt;/li>&lt;/ul>
&lt;p class="vc-cover__note">No model was measured at more than one quantization.&lt;/p>&lt;/dd>
&lt;/div>
&lt;div class="vc-cover__row">
&lt;dt>Context lengths &lt;span class="vc-dim">(4)&lt;/span>&lt;/dt>
&lt;dd>&lt;ul class="vc-chips">&lt;li>&lt;strong>4,096&lt;/strong> &lt;span class="vc-dim">24&lt;/span>&lt;/li>&lt;li>&lt;strong>8,192&lt;/strong> &lt;span class="vc-dim">3&lt;/span>&lt;/li>&lt;li>&lt;strong>16,384&lt;/strong> &lt;span class="vc-dim">8&lt;/span>&lt;/li>&lt;li>&lt;strong>131,072&lt;/strong> &lt;span class="vc-dim">1&lt;/span>&lt;/li>&lt;/ul>&lt;/dd>
&lt;/div>
&lt;div class="vc-cover__row">
&lt;dt>Runtimes &lt;span class="vc-dim">(4)&lt;/span>&lt;/dt>
&lt;dd>&lt;ul class="vc-chips">&lt;li>&lt;strong>llama.cpp b10507&lt;/strong> &lt;span class="vc-dim">3&lt;/span>&lt;/li>&lt;li>&lt;strong>LM Studio 0.4.21&lt;/strong> &lt;span class="vc-dim">6&lt;/span>&lt;/li>&lt;li>&lt;strong>Ollama 0.32.1&lt;/strong> &lt;span class="vc-dim">20&lt;/span>&lt;/li>&lt;li>&lt;strong>Ollama 0.32.15&lt;/strong> &lt;span class="vc-dim">7&lt;/span>&lt;/li>&lt;/ul>&lt;/dd>
&lt;/div>
&lt;div class="vc-cover__row">
&lt;dt>Ran partly off the card &lt;span class="vc-dim">(4)&lt;/span>&lt;/dt>
&lt;dd>&lt;ul class="vc-chips">&lt;li>&lt;a href="#sku-gpt-oss-20b-mxfp4-ctx8192-lm-studio-0-4-21-2026-08-26-defaults">gpt-oss:20b, 8,192 context, LM Studio 0.4.21&lt;/a>&lt;/li>&lt;li>&lt;a href="#sku-qwen3-coder-30b-q4-k-m-ctx16384-ollama-0-32-1-2026-08-26">qwen3-coder:30b, 16,384 context, Ollama 0.32.1&lt;/a>&lt;/li>&lt;li>&lt;a href="#sku-llama3-2-3b-q4-k-m-ctx131072-ollama-0-32-15-2026-08-26-defaults">llama3.2:3b, 131,072 context, Ollama 0.32.15&lt;/a>&lt;/li>&lt;li>&lt;a href="#sku-qwen3-coder-30b-q4-k-m-ctx4096-ollama-0-32-1-2026-08-26">qwen3-coder:30b, 4,096 context, Ollama 0.32.1&lt;/a>&lt;/li>&lt;/ul>&lt;/dd>
&lt;/div>
&lt;div class="vc-cover__row">
&lt;dt>Power runs &lt;span class="vc-dim">(4)&lt;/span>&lt;/dt>
&lt;dd>&lt;ul class="vc-chips">&lt;li>&lt;strong>llama3.2:3b&lt;/strong> &lt;span class="vc-dim">stock limit&lt;/span>&lt;/li>&lt;li>&lt;strong>qwen2.5:7b&lt;/strong> &lt;span class="vc-dim">stock limit&lt;/span>&lt;/li>&lt;li>&lt;strong>qwen2.5:14b&lt;/strong> &lt;span class="vc-dim">stock limit&lt;/span>&lt;/li>&lt;li>&lt;strong>gpt-oss:20b&lt;/strong> &lt;span class="vc-dim">stock limit&lt;/span>&lt;/li>&lt;/ul>&lt;/dd>
&lt;/div>
&lt;/dl>
&lt;/div>
&lt;h2 id="what-it-does-not-cover-yet">What it does not cover yet&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>One quantization per model.&lt;/strong> I cannot show the same model at three quantizations stepping down the card, because each model was measured at one.&lt;/li>
&lt;li>&lt;strong>No dense model past the cliff.&lt;/strong> The runs that left the card are a 3B model at an extreme context, a mixture-of-experts model that never fit, and one LM Studio default that offloaded part of a model that otherwise fits. A dense model that fits at one context and spills at the next is the row this map most needs.&lt;/li>
&lt;li>&lt;strong>A gap between 16,384 and 131,072 context.&lt;/strong> One run sits at the far end. Nothing was measured at 32K or 64K.&lt;/li>
&lt;li>&lt;strong>Energy at stock only.&lt;/strong> No undervolt, no reduced power limit, and no energy figure for a run that spilled.&lt;/li>
&lt;li>&lt;strong>One card.&lt;/strong> Another 16 GB card, or this one with a different desktop load, will read differently.&lt;/li>
&lt;/ul>
&lt;h2 id="method-exactly">Method, exactly&lt;/h2>
&lt;p>I did not run anything new for this page. It reads files I had already published and puts them on one axis.&lt;/p>
&lt;p>The throughput rows come from &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput-raw/llm_throughput_capture.py">my capture script&lt;/a>. For each model, context and prompt size it calls Ollama&amp;rsquo;s &lt;code>/api/generate&lt;/code> three times at temperature 0, seed 42 and a 256-token output, with a unique prefix on every prompt so each run pays a full prefill. Decode and prefill rates are Ollama&amp;rsquo;s own &lt;code>eval_count&lt;/code> over &lt;code>eval_duration&lt;/code> and &lt;code>prompt_eval_count&lt;/code> over &lt;code>prompt_eval_duration&lt;/code>, and the CSV keeps the median of the three. After each cell the script asks &lt;code>nvidia-smi&lt;/code> for &lt;code>memory.used&lt;/code> and stores it as &lt;code>vram_resident_mib&lt;/code>. That one reading is the pin&amp;rsquo;s position.&lt;/p>
&lt;p>That reading is the whole card. It includes the desktop, and it includes any model Ollama had not yet unloaded, which is how one Llama 3.2 3B row came to read 15,682 MiB. The runtime comparison captures used a different script that took the median memory reading across runs and, in the later capture, also read the card before each load.&lt;/p>
&lt;p>Each throughput configuration was measured with two prompt sizes. The pin is the first of the two, the shorter prompt, and both are in the record. The model names differ between files, so I join them on the name with punctuation and a trailing quantization tag removed. Only the throughput CSV has a quantization column; where another file&amp;rsquo;s row shows a quantization, the record says it was taken from the same model there.&lt;/p>
&lt;p>The card total, 16,303 MiB, is the &lt;code>nvidia-smi&lt;/code> total written into the raw capture file from 2026-08-26. Headroom, share of the card, GiB, the memory a load added, the changes between two rows and the per-thousand-token energy are computed when the site is built, from the measured values beside them, and each one is shown with its formula. Your browser does no arithmetic on them.&lt;/p>
&lt;h2 id="download-the-files">Download the files&lt;/h2>
&lt;div class="vc vc--part">
&lt;ul class="vc-files">
&lt;li>&lt;a class="vc-btn" href="https://techfuelhq.com/data/rtx-5080-llm-throughput.csv" download type="text/csv">rtx-5080-llm-throughput.csv&lt;/a>&lt;span>34 rows. Decode, prefill, load time and whole-card memory for each model, context and prompt size on Ollama. Raw capture JSON and the capture script are listed in &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput-raw/MANIFEST.txt">its manifest&lt;/a>.&lt;/span>&lt;/li>
&lt;li>&lt;a class="vc-btn" href="https://techfuelhq.com/data/llm-server-compare-2026-08.csv" download type="text/csv">llm-server-compare-2026-08.csv&lt;/a>&lt;span>6 rows. Ollama beside llama.cpp on three models, with its settings and capture date in the footer notes.&lt;/span>&lt;/li>
&lt;li>&lt;a class="vc-btn" href="https://techfuelhq.com/data/llm-server-compare-2026-08-26-lmstudio.csv" download type="text/csv">llm-server-compare-2026-08-26-lmstudio.csv&lt;/a>&lt;span>12 rows. Ollama beside LM Studio on three models, at default and normalized settings, with the memory reading before each load.&lt;/span>&lt;/li>
&lt;li>&lt;a class="vc-btn" href="https://techfuelhq.com/data/vram-cliff-raw/ollama-256k-slider-3b.json" download type="application/json">ollama-256k-slider-3b.json&lt;/a>&lt;span>One raw capture: the 131,072-context run, its five decode runs and the card's reported total. Described in &lt;a href="https://techfuelhq.com/data/vram-cliff-raw/MANIFEST.txt">its manifest&lt;/a>.&lt;/span>&lt;/li>
&lt;li>&lt;a class="vc-btn" href="https://techfuelhq.com/data/rtx-5080-llm-power-efficiency.csv" download type="text/csv">rtx-5080-llm-power-efficiency.csv&lt;/a>&lt;span>4 rows. Board power, decode rate and joules per token at the stock power limit. The one-per-second telemetry is listed in &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-power-efficiency-raw/MANIFEST.txt">its manifest&lt;/a>.&lt;/span>&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>All of it is &lt;a href="https://creativecommons.org/licenses/by/4.0/" rel="noopener">CC BY 4.0&lt;/a>. Attribute as &amp;ldquo;TechFuelHQ RTX 5080 16 GB VRAM cliff map&amp;rdquo; with a link to this page. To cite one configuration, open its row in the list and copy its link; the address ends in that row&amp;rsquo;s own id.&lt;/p>
&lt;h2 id="correction-log">Correction log&lt;/h2>
&lt;p>No corrections so far. The datasets this page reads keep their own logs: the &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-throughput/#change-log">throughput dataset&lt;/a>, the &lt;a href="https://techfuelhq.com/data/llm-server-compare/">runtime comparison dataset&lt;/a> and the &lt;a href="https://techfuelhq.com/data/rtx-5080-llm-power-efficiency/#change-log">power efficiency dataset&lt;/a>. If a row here is wrong, write to &lt;a href="mailto:contact@techfuelhq.com">contact@techfuelhq.com&lt;/a> and I will log the change in this section with its date.&lt;/p></description></item><item><title>DDR5 RAM Price Index: Dated $/GB at Newegg (Pilot)</title><link>https://techfuelhq.com/data/ram-price-index/</link><pubDate>Wed, 12 Aug 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/data/ram-price-index/</guid><atom:updated>2026-11-17T15:26:27Z</atom:updated><description>&lt;p>By &lt;a href="https://techfuelhq.com/author/lk-wood-iv/">LK Wood IV&lt;/a> · Published 2026-08-12 · ~5 min read · St. Louis County, MO&lt;/p>
&lt;h2 id="the-short-version">The short version&lt;/h2>
&lt;p>DDR5 prices roughly tripled during the 2026 memory supply crisis, and the
numbers that circulate are mostly screenshots without dates or methods. This
page is the start of a dated, checkable record: a $/GB index for mainstream
32GB (2x16GB) DDR5 kits observed &lt;strong>at Newegg&lt;/strong>, with the method, the
acceptance rules, the rejection reasons, and the raw data published alongside
the numbers. Since November 17, 2026 the prices come from Newegg&amp;rsquo;s affiliate
catalogue, which does not say who sells a listing. Rows dated September 26
through October 11, 2026 were confirmed as sold by Newegg on the product
page. Rows dated before September 26, 2026 came from a list of named direct
US retailers.&lt;/p>
&lt;p>That cohort boundary matters. It does not price 8GB DDR4 modules or DDR5 ECC
UDIMMs, and it is not a general DDR4-versus-DDR5 buying verdict. Use the
&lt;a href="https://techfuelhq.com/articles/ddr5-ram-buying-guide-2025/">DDR5 buying guide&lt;/a> for the platform and
workload decision. Use the &lt;a href="https://techfuelhq.com/homelab/ecc-home-server-verify-2026/">ECC home-server
guide&lt;/a> when the question is ECC UDIMM
rather than ordinary consumer DDR5. Each price question still needs the exact
capacity and memory class.&lt;/p>
&lt;p>It is labeled a &lt;strong>pilot&lt;/strong> because the index metric has an activation gate, and
the gate status is printed here verbatim rather than worked around.&lt;/p>
&lt;p>For the single dated number, see &lt;a href="https://techfuelhq.com/data/ddr5-clock/">the DDR5 Clock&lt;/a>: this index&amp;rsquo;s latest median price per GB, with a citation and a frozen page for each capture day. &lt;a href="https://techfuelhq.com/data/deal-or-mirage/">Deal or Mirage&lt;/a> lists every tracked kit beside the graphics cards and SSDs, each with a label worked out from its own price history.&lt;/p>
&lt;h2 id="compare-the-dated-offers">Compare the dated offers&lt;/h2>
&lt;p>A 32GB DDR5-6000 kit can appear under several timings. Compare the full part and CAS latency before treating two prices as the same kit. On October 10 the corrected basket contained four qualifying lines; the next capture used a different matching method. The &lt;a href="https://techfuelhq.com/data/ram-price-correction-2026-10-11.json" download type="application/json">October 11 correction record&lt;/a> explains why some older CL30-labelled rows disappeared.&lt;/p>
&lt;style>.price-capture-compare { margin: 1.25rem 0 2rem; min-width: 0; }
.price-capture-compare > p:first-child { border-inline-start: 3px solid var(--accent); padding-inline-start: .8rem; }
.price-capture-compare .table-wrap { max-width: 100%; overflow-x: auto; }
.price-capture-compare table { width: 100%; font-variant-numeric: tabular-nums; }
.price-capture-compare caption { text-align: left; color: var(--heading); font-weight: 650; }
.price-capture-compare th[scope=row] { min-width: 12rem; text-align: left; }
.price-capture-compare [data-price] { white-space: nowrap; }
.price-part-mismatch { display: block; font-size: .83rem; font-weight: 500; line-height: 1.45; margin: 0 0 .5rem; white-space: normal; }
.price-field-label { display: none; }
.price-capture-compare summary { cursor: pointer; color: var(--accent); min-height: 2.75rem; padding-block: .55rem; }
.price-capture-compare small { display: block; font-weight: normal; line-height: 1.5; overflow-wrap: anywhere; }
.price-capture-compare :is(summary, [tabindex]) { --focus-offset: var(--focus-offset-region); }
.price-capture-evidence { border-block: 1px solid var(--border-strong); padding: .35rem 0; }
.price-capture-evidence > summary { font-weight: 650; }
.price-capture-evidence code { overflow-wrap: anywhere; white-space: normal; }
@media (max-width: 640px) {
.price-capture-compare .price-offers-table { display: block; width: 100%; min-width: 0; }
.price-offers-table caption { display: block; padding: .6rem .75rem; white-space: normal; }
.price-offers-table thead { position: absolute; width: 1px; height: 1px; overflow: hidden; clip-path: inset(50%); }
.price-offers-table tbody { display: block; }
.price-offers-table tbody tr { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); border-top: 1px solid var(--border-strong); }
.price-offers-table tbody tr:has([data-pair]) { grid-template-columns: repeat(3, minmax(0, 1fr)); }
.price-capture-compare .price-offers-table th[scope=row] { grid-column: 1 / -1; display: block; min-width: 0; padding: .2rem .75rem 0; white-space: normal; }
.price-offers-table td { display: block; padding: .25rem .65rem .65rem; border: none; white-space: normal; }
.price-offers-table .price-field-label { display: block; font-size: .75rem; font-weight: 600; color: var(--text-muted); }
}
&lt;/style>&lt;div class="price-capture-compare" data-price-reader="ram">&lt;p id="price-reader-ram-0-note">&lt;strong>November 17, 2026:&lt;/strong> 8 offers in the archived file. Open a model name to read the retailer’s listing title. These are dated observations; check stock and price before buying.&lt;/p>&lt;p data-pair-rule="withheld">The preceding observation date was October 11, 2026. At least one calendar day in between has no published offer. A price change across the gap is withheld.&lt;/p>&lt;div class="table-wrap" tabindex="0" role="region" aria-labelledby="price-reader-ram-0-caption">
&lt;table class="price-offers-table" role="table" aria-describedby="price-reader-ram-0-note">&lt;caption id="price-reader-ram-0-caption">RAM offers, lowest recorded price first · 2026-11-17 UTC&lt;/caption>
&lt;thead role="rowgroup">&lt;tr role="row">&lt;th scope="col" role="columnheader">Model and seller&lt;/th>&lt;th scope="col" role="columnheader">Price (USD)&lt;/th>&lt;th scope="col" role="columnheader">USD per GB&lt;/th>&lt;/tr>&lt;/thead>
&lt;tbody role="rowgroup">&lt;tr role="row" data-product="teamgroup-delta-rgb-6000c30">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>TeamGroup T-Force Delta RGB 32GB (2x16GB) DDR5-6000 CL30 · Newegg listing (seller not stated)&lt;/summary>&lt;small>Team T-Force Delta RGB 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model FF3D532G6000HC30DC01&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$639.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per GB&lt;/span>$20.0&lt;/td>&lt;/tr>&lt;tr role="row" data-product="corsair-vengeance-6000c30">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · Newegg listing (seller not stated)&lt;/summary>&lt;small>CORSAIR Vengeance 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model CMK32GX5M2B6000C30&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$644.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per GB&lt;/span>$20.156&lt;/td>&lt;/tr>&lt;tr role="row" data-product="corsair-vengeance-rgb-6000c30">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · Newegg listing (seller not stated)&lt;/summary>&lt;small>CORSAIR Vengeance RGB 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model CMH32GX5M2N6000Z30&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$654.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per GB&lt;/span>$20.468&lt;/td>&lt;/tr>&lt;tr role="row" data-product="gskill-flare-x5-6000c30">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>G.Skill Flare X5 32GB (2x16GB) DDR5-6000 CL30 · Newegg listing (seller not stated)&lt;/summary>&lt;small>G. SKILL Flare X5 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model F5-6000J3038F16GH2-FX5&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$659.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per GB&lt;/span>$20.625&lt;/td>&lt;/tr>&lt;tr role="row" data-product="gskill-ripjaws-s5-6000c30">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30 · Newegg listing (seller not stated)&lt;/summary>&lt;small>G. SKILL Ripjaws S5 Series 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model F5-6000J3040F16GX2-RS5K&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$679.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per GB&lt;/span>$21.25&lt;/td>&lt;/tr>&lt;tr role="row" data-product="gskill-trident-z5-rgb-6400c32">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · Newegg listing (seller not stated)&lt;/summary>&lt;small>G. SKILL Trident Z5 RGB Series 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6400 (PC5 51200) Desktop Memory Model F5-6400J3239G16GX2-TZ5RK&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$679.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per GB&lt;/span>$21.25&lt;/td>&lt;/tr>&lt;tr role="row" data-product="gskill-trident-z5-neo-6000c30">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30 · Newegg listing (seller not stated)&lt;/summary>&lt;small>G. SKILL Trident Z5 Neo RGB Series AMD EXPO 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model F5-6000J3038F16GX2-TZ5NR&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$709.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per GB&lt;/span>$22.187&lt;/td>&lt;/tr>&lt;tr role="row" data-product="kingston-fury-beast-6000c30">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>Kingston Fury Beast 32GB (2x16GB) DDR5-6000 CL30 · Newegg listing (seller not stated)&lt;/summary>&lt;small>Kingston FURY Beast 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Memory (Desktop Memory) Model KF560C30BBEAK2-32&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$709.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per GB&lt;/span>$22.187&lt;/td>&lt;/tr>&lt;/tbody>&lt;/table>
&lt;/div>&lt;p>&lt;strong>On 2026-10-11 only:&lt;/strong> Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30. No price was carried into the later capture.&lt;/p>&lt;details class="price-capture-evidence">&lt;summary>See coverage, gaps and source files&lt;/summary>
&lt;p>&lt;a href="https://techfuelhq.com/data/ram-price-observations.csv" download>Download all 422 offer rows (CSV)&lt;/a>. They span 37 distinct UTC dates, from 2026-08-12 through 2026-11-17. A missing date means there is no published offer row for that date. The recorded method on 2026-11-17 was &lt;code>ram-usd-per-gb-newegg-affiliate-feed-v1&lt;/code>.&lt;/p>&lt;p>&lt;a href="https://techfuelhq.com/data/ram-price-index.csv" download>Download the 5 recorded index rows (CSV)&lt;/a>. Each median uses the models that qualified on that date. Different membership or a new method can move a median even when no individual listing changed price.&lt;/p>&lt;div class="table-wrap" tabindex="0" role="region" aria-labelledby="price-reader-ram-0-series">&lt;table>&lt;caption id="price-reader-ram-0-series">Published index rows, with their original methods&lt;/caption>&lt;thead>&lt;tr>&lt;th scope="col">UTC date&lt;/th>&lt;th scope="col">Models qualified / queried&lt;/th>&lt;th scope="col">Median USD per GB&lt;/th>&lt;th scope="col">Recorded method&lt;/th>&lt;/tr>&lt;/thead>&lt;tbody>&lt;tr>&lt;th scope="row">2026-08-30&lt;/th>&lt;td>6 / 12&lt;/td>&lt;td>$18.843&lt;/td>&lt;td>&lt;code>ram-usd-per-gb-discovery-v2&amp;#43;cas-exact-v1&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-09-01&lt;/th>&lt;td>6 / 12&lt;/td>&lt;td>$19.297&lt;/td>&lt;td>&lt;code>ram-usd-per-gb-discovery-v2&amp;#43;cas-exact-v1&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-09-02&lt;/th>&lt;td>6 / 12&lt;/td>&lt;td>$19.0&lt;/td>&lt;td>&lt;code>ram-usd-per-gb-discovery-v2&amp;#43;cas-exact-v1&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-11&lt;/th>&lt;td>9 / 12&lt;/td>&lt;td>$19.937&lt;/td>&lt;td>&lt;code>ram-usd-per-gb-newegg-direct-v4&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-11-17&lt;/th>&lt;td>8 / 12&lt;/td>&lt;td>$20.938&lt;/td>&lt;td>&lt;code>ram-usd-per-gb-newegg-affiliate-feed-v1&lt;/code>&lt;/td>&lt;/tr>
&lt;/tbody>&lt;/table>&lt;/div>
&lt;/details>&lt;/div>
&lt;h2 id="recent-qualifying-observations">Recent qualifying observations&lt;/h2>
&lt;p>&lt;strong>Collection status:&lt;/strong> Captures from November 17, 2026 read that day&amp;rsquo;s Newegg affiliate catalogue file. Captures from September 26 through October 11, 2026 read Newegg&amp;rsquo;s product pages. No capture ran between those two periods, and the method differs across the gap. The latest-capture block below names the latest one; check Newegg for current price and stock.&lt;/p>
&lt;!-- auto:capture -->
&lt;p>&lt;strong>Latest capture, November 17, 2026 (UTC), method &lt;code>ram-usd-per-gb-newegg-affiliate-feed-v1&lt;/code>:&lt;/strong> Newegg&amp;rsquo;s affiliate catalogue file for that date had 191 listings naming a tracked model; 22 passed every rule, and 8 of 12 tracked kits have a price. The index metric activates at 6, so the gate is open and an index row was written for this date. Every row carries &lt;code>verification_status: retailer_feed&lt;/code>: the price, title, part number and in-stock flag are the catalogue&amp;rsquo;s own. The catalogue names no seller and no condition, and nothing was checked against the product page.&lt;/p>
&lt;p>Cheapest qualifying listing: &lt;strong>$639.99&lt;/strong> (TeamGroup T-Force Delta RGB 32GB (2x16GB) DDR5-6000 CL30, 20 $/GB).&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Line&lt;/th>
&lt;th scope="col" style="text-align: right">Cheapest qualifying listing&lt;/th>
&lt;th scope="col" style="text-align: right">$/GB&lt;/th>
&lt;th scope="col">Newegg item number&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Line">TeamGroup T-Force Delta RGB 32GB (2x16GB) DDR5-6000 CL30&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$639.99&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">20&lt;/td>
&lt;td data-label="Newegg item number">N82E16820331845&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$644.99&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">20.156&lt;/td>
&lt;td data-label="Newegg item number">N82E16820982007&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$654.99&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">20.468&lt;/td>
&lt;td data-label="Newegg item number">N82E16820982184&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">G.Skill Flare X5 32GB (2x16GB) DDR5-6000 CL30&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$659.99&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">20.625&lt;/td>
&lt;td data-label="Newegg item number">N82E16820374783&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$679.99&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">21.25&lt;/td>
&lt;td data-label="Newegg item number">N82E16820374369&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$679.99&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">21.25&lt;/td>
&lt;td data-label="Newegg item number">N82E16820374358&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$709.99&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">22.187&lt;/td>
&lt;td data-label="Newegg item number">N82E16820374427&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">Kingston Fury Beast 32GB (2x16GB) DDR5-6000 CL30&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$709.99&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">22.187&lt;/td>
&lt;td data-label="Newegg item number">N82E16820242861&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">Kingston Fury Renegade 32GB (2x16GB) DDR5-6400 CL32&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">none: its listings carry other item numbers&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">-&lt;/td>
&lt;td data-label="Newegg item number">-&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">Crucial Pro Overclocking 32GB (2x16GB) DDR5-6000 CL36&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">none: its listings carry other item numbers&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">-&lt;/td>
&lt;td data-label="Newegg item number">-&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">none: nearest listings have a different CAS timing&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">-&lt;/td>
&lt;td data-label="Newegg item number">-&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">G.Skill Flare X5 32GB (2x16GB) DDR5-5600 CL36&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">none: nearest listings carry other item numbers or are not 2x16GB kits or are priced outside the accepted band&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">-&lt;/td>
&lt;td data-label="Newegg item number">-&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>This block is rewritten with every capture; the dated commentary below it is not.&lt;/p>
&lt;!-- /auto:capture -->
&lt;p>The table shows every qualifying offer from the three newest captures, oldest
first, exactly as the collector recorded it — not just the cheapest row per
kit. The complete CSV history remains available below the table.&lt;/p>
&lt;div class="table-wrap csv-table">
&lt;table aria-describedby="csv-table-note-1">
&lt;caption>Recent observations from the latest 3 capture dates, oldest to newest&lt;/caption>
&lt;thead>
&lt;tr>&lt;th scope="col">Capture Date UTC&lt;/th>&lt;th scope="col">Product Label&lt;/th>&lt;th scope="col">Title&lt;/th>&lt;th scope="col">Seller&lt;/th>&lt;th scope="col">Price USD&lt;/th>&lt;th scope="col">USD per GB&lt;/th>&lt;th scope="col">Verification Status&lt;/th>&lt;/tr>
&lt;/thead>
&lt;tbody>&lt;tr>&lt;td>2026-10-10&lt;/td>&lt;td>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>CORSAIR Vengeance 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model CMK32GX5M2B6000Z30&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>529.99&lt;/td>&lt;td>16.562&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-10&lt;/td>&lt;td>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>CORSAIR Vengeance RGB 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model CMH32GX5M2N6000Z30&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>637.99&lt;/td>&lt;td>19.937&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-10&lt;/td>&lt;td>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32&lt;/td>&lt;td>G.SKILL Trident Z5 RGB Series 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6400 (PC5 51200) Desktop Memory Model F5-6400J3239G16GX2-TZ5RK&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>659.99&lt;/td>&lt;td>20.625&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-10&lt;/td>&lt;td>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>CORSAIR Dominator Titanium 32GB (2 x 16GB) DDR5 6000 (PC5 48000) Desktop Memory Model CMP32GX5M2B6000C30&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>674.99&lt;/td>&lt;td>21.093&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>CORSAIR Vengeance 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model CMK32GX5M2B6000Z30&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>529.99&lt;/td>&lt;td>16.562&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>G.Skill Flare X5 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>G.SKILL Flare X5 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model F5-6000J3038F16GH2-FX5&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>629.99&lt;/td>&lt;td>19.687&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>G.SKILL Trident Z5 Neo RGB Series AMD EXPO 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model F5-6000J3038F16GH2-TZ5NR&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>649.99&lt;/td>&lt;td>20.312&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>G.SKILL Ripjaws S5 Series 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model F5-6000J3040F16GX2-RS5W&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>659.99&lt;/td>&lt;td>20.625&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>Kingston Fury Beast 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>Kingston FURY Beast 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Memory (Desktop Memory) Model KF560C30BWEK2-32&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>589.99&lt;/td>&lt;td>18.437&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>TeamGroup T-Force Delta RGB 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>Team T-Force Delta RGB 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model FF3D532G6000HC30DC01&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>539.99&lt;/td>&lt;td>16.875&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>CORSAIR Vengeance RGB 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model CMH32GX5M2N6000Z30&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>637.99&lt;/td>&lt;td>19.937&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32&lt;/td>&lt;td>G.SKILL Trident Z5 RGB Series 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6400 (PC5 51200) Desktop Memory Model F5-6400J3239G16GX2-TZ5RK&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>659.99&lt;/td>&lt;td>20.625&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>CORSAIR Dominator Titanium 32GB (2 x 16GB) DDR5 6000 (PC5 48000) Desktop Memory Model CMP32GX5M2B6000C30&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>674.99&lt;/td>&lt;td>21.093&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>CORSAIR Vengeance 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model CMK32GX5M2B6000C30&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>644.99&lt;/td>&lt;td>20.156&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>G.Skill Flare X5 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>G. SKILL Flare X5 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model F5-6000J3038F16GH2-FX5&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>659.99&lt;/td>&lt;td>20.625&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>G. SKILL Trident Z5 Neo RGB Series AMD EXPO 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model F5-6000J3038F16GX2-TZ5NR&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>709.99&lt;/td>&lt;td>22.187&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>G. SKILL Ripjaws S5 Series 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model F5-6000J3040F16GX2-RS5K&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>679.99&lt;/td>&lt;td>21.25&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>Kingston Fury Beast 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>Kingston FURY Beast 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Memory (Desktop Memory) Model KF560C30BBEAK2-32&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>709.99&lt;/td>&lt;td>22.187&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>TeamGroup T-Force Delta RGB 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>Team T-Force Delta RGB 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model FF3D532G6000HC30DC01&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>639.99&lt;/td>&lt;td>20.0&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30&lt;/td>&lt;td>CORSAIR Vengeance RGB 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000) Desktop Memory Model CMH32GX5M2N6000Z30&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>654.99&lt;/td>&lt;td>20.468&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32&lt;/td>&lt;td>G. SKILL Trident Z5 RGB Series 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6400 (PC5 51200) Desktop Memory Model F5-6400J3239G16GX2-TZ5RK&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>679.99&lt;/td>&lt;td>21.25&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p class="csv-table__note" id="csv-table-note-1">Showing 21 of 422 observations from the latest 3 capture dates. &lt;a href="https://techfuelhq.com/data/ram-price-observations.csv" download>Download the complete CSV history&lt;/a>. The table is rendered from that file at build time.&lt;/p>
&lt;p>On 2026-09-14 the block above began using the successful capture output, while
the commentary below it is dated by hand. The sibling
&lt;a href="https://techfuelhq.com/data/gpu-price-index/">GPU price index&lt;/a> and
&lt;a href="https://techfuelhq.com/data/ssd-price-index/">NVMe SSD price index&lt;/a> launched the same day on the
same collector and the same gate.&lt;/p>
&lt;h2 id="first-capture-2026-08-12">First capture (2026-08-12)&lt;/h2>
&lt;p>&lt;strong>Superseded classification:&lt;/strong> the August 12–24 field notes below preserve what
the original matcher reported. In the corrected file the lowest retained offer
was $529.99 on both August 18 and August 24. On October 11, the public derivatives were rebuilt with
an exact-CAS requirement after looser variants were found inside CL30-labelled
lines. Use the corrected CSVs and the latest-capture block for current
eligibility; the raw capture receipt remains unchanged for audit.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Kit&lt;/th>
&lt;th scope="col" style="text-align: right">Cheapest qualifying offer&lt;/th>
&lt;th scope="col" style="text-align: right">$/GB&lt;/th>
&lt;th scope="col">Retailer&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Kit">Corsair Vengeance 32GB (2x16) DDR5-6000 CL30&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying offer">$449.99&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">$14.06&lt;/td>
&lt;td data-label="Retailer">B&amp;amp;H&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Kit">Corsair Vengeance RGB 32GB (2x16) DDR5-6000 CL30&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying offer">$449.99&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">$14.06&lt;/td>
&lt;td data-label="Retailer">B&amp;amp;H&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Kit">Corsair Dominator Titanium 32GB (2x16) DDR5-6000&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying offer">$649.99&lt;/td>
&lt;td style="text-align: right" data-label="$/GB">$20.31&lt;/td>
&lt;td data-label="Retailer">Newegg&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>21 qualifying offers total across 3 kits, out of 546 listings reviewed. For
historical scale, the Vengeance 6000 CL30 kit was a $95–110 street-price part
through 2024 — the price history lives in
&lt;a href="https://techfuelhq.com/articles/ddr5-ram-buying-guide-2025/">the DDR5 buying guide&lt;/a> — so the first
capture&amp;rsquo;s cheapest accepted observation was roughly &lt;strong>4x&lt;/strong> that older range.&lt;/p>
&lt;p>The next four successful capture dates held the same narrow model coverage.
Two captures ran on August 13. The earlier 07:11 UTC capture reviewed 581
listings and retained 23 qualifying offers across three Corsair kit lines; the
scheduled 14:03 UTC capture reviewed 538 and retained 26 across those same
lines. Both had a $449.99 cheapest qualifying offer. The later run replaced the
date-level evidence directory, but the earlier four-file capture survives in
repository history at commit &lt;code>b9e56c1a&lt;/code>. August 14 produced 24 eligible offers,
August 15 produced 30, and August 16 produced 29. No August 17 capture landed.&lt;/p>
&lt;p>The August 18 capture reviewed &lt;strong>583 listings&lt;/strong> and accepted &lt;strong>25 offers across
the same three models&lt;/strong>. The cheapest qualifying offer moved to &lt;strong>$459.99 at
B&amp;amp;H&lt;/strong>, or &lt;strong>$14.375 per GB&lt;/strong>. That is a real $10 move in the discovery set,
but still not a broad market index: nine of the 12 tracked kit lines produced
no row that cleared the public rules.&lt;/p>
&lt;p>Six more daily captures followed. August 19 reviewed 590 listings and
accepted 24, August 20 reviewed 616 and accepted 24, August 21 reviewed 680
and accepted 21, August 22 reviewed 624 and accepted 17, August 23 reviewed
716 and accepted 16, and August 24 reviewed 706 and accepted 16. The same
three Corsair lines qualified every day. No fourth model line has produced a
single qualifying row. Twelve captures in, that is still the whole story.&lt;/p>
&lt;p>The $459.99 floor held for six days and then ended on August 24, though not
in the way a price chart would suggest. The B&amp;amp;H listing behind that figure
simply left the result set.&lt;/p>
&lt;p>Of the 13 listings present on both August 23 and
August 24, &lt;strong>not one changed price&lt;/strong>. The new cheapest qualifying offer is
&lt;strong>$469.59&lt;/strong> ($14.675/GB), a Corsair Vengeance RGB kit at Best Buy that was
absent from the previous day&amp;rsquo;s set. The shelf changed. No seller repriced
anything.&lt;/p>
&lt;p>Read the preceding $469.59 as the original, superseded result. In the &lt;a href="https://techfuelhq.com/data/ram-price-observations.csv" download type="text/csv">corrected August 24 observations&lt;/a>, the lowest retained kit was a Corsair Vengeance at Central Computers for &lt;strong>$529.99&lt;/strong> ($16.562/GB). There were three distinct kit lines, too few for an index row.&lt;/p>
&lt;p>That original leader carried a flag. Its model number is CMH32GX5M2B6000C38 — a CL38 kit — while the line it
satisfies is labelled CL30. The second-cheapest RGB row is a C36 part. The
line&amp;rsquo;s actual CL30 kits all sit at $619.99.&lt;/p>
&lt;p>So the tracked line is mixing
timings, and as of today the headline figure is set by the loosest of them. This is the same defect class as the RGB contamination corrected on August
21: a listing satisfying a line it should not. It is not corrected here; the
rows stay as captured.&lt;/p>
&lt;p>August 22 was the first capture with the plain Corsair Vengeance line free of
RGB-titled listings, after the collector began rejecting excluded tokens. August 23 repeated it. August 24 made three. All seven of that line&amp;rsquo;s rows
are non-RGB, and its cheapest clean offer has held at $479.99 ($15.00/GB) at
Central Computers on the same listing for all three days.&lt;/p>
&lt;p>That is the figure
the 2026-08-21 correction identified as the line&amp;rsquo;s true non-RGB price. One
capture showed the filter ran. Three show it holds. The lines price
independently now, and no longer share a listing.&lt;/p>
&lt;h2 id="ram-history-0-title">Accepted price history by tracked kit&lt;/h2>
&lt;section class="ram-history" id="ram-history-2" aria-label="Accepted RAM kit price history">
&lt;style>
#ram-history-2 { --rh-blue: var(--cyan,#5db7ff); --rh-grid: color-mix(in srgb, currentColor 20%, transparent); margin: 2rem 0; padding: 1rem; border: 1px solid var(--rh-grid); border-radius: .75rem; }
#ram-history-2 .ram-history__controls { display: grid; min-width: 0; gap: .45rem; margin-bottom: .75rem; overflow-x: clip; overflow-clip-margin: 4px; }
#ram-history-2 label { font-weight: 700; }
#ram-history-2 select { width: 100%; min-width: 0; max-width: 100%; padding: .55rem .65rem; color: inherit; background: inherit; border: 1px solid currentColor; border-radius: .35rem; }
#ram-history-2 .ram-history__plot { overflow-x: auto; }
#ram-history-2 svg { display: block; min-width: 44rem; width: 100%; height: auto; }
#ram-history-2 .ram-history__grid { stroke: var(--rh-grid); stroke-width: 1; }
#ram-history-2 .ram-history__axis { fill: currentColor; font-family: system-ui, sans-serif; }
#ram-history-2 .ram-history__line { fill: none; stroke: var(--rh-blue); stroke-width: 3; stroke-linecap: round; stroke-linejoin: round; }
#ram-history-2 .ram-history__point { fill: var(--rh-blue); stroke: Canvas; stroke-width: 1.5; }
#ram-history-2 [hidden] { display: none; }
#ram-history-2 .ram-history__status { margin: .6rem 0 0; font-weight: 650; }
#ram-history-2 .ram-history__note { margin: .65rem 0; }
#ram-history-2 .ram-history__state--stale { font-weight: 750; }
#ram-history-2 .ram-history__table { min-width: 46rem; table-layout: fixed; }
#ram-history-2 .ram-history__table col:nth-child(1) { width: 34%; }
#ram-history-2 .ram-history__table col:nth-child(2) { width: 16%; }
#ram-history-2 .ram-history__table col:nth-child(3),
#ram-history-2 .ram-history__table col:nth-child(4) { width: 11%; }
#ram-history-2 .ram-history__table col:nth-child(5) { width: 28%; }
#ram-history-2 .ram-history__table th,
#ram-history-2 .ram-history__table td { vertical-align: top; }
#ram-history-2 .ram-history__table time,
#ram-history-2 .ram-history__table [data-column="price"],
#ram-history-2 .ram-history__table [data-column="unit-price"] { white-space: nowrap; }
#ram-history-2 .ram-history__identity { display: block; margin-top: .35rem; font-size: .8rem; font-weight: 400; line-height: 1.35; white-space: normal; overflow-wrap: anywhere; }
&lt;/style>
&lt;p class="ram-history__note">Each point is the cheapest accepted offer for one tracked kit line on that date. The seller or listing can change. Points connect only on consecutive calendar dates with the same recorded method; a gap or unknown method leaves a break.&lt;/p>
&lt;div class="ram-history__controls">
&lt;label for="ram-history-2-select">Tracked kit&lt;/label>
&lt;select id="ram-history-2-select" disabled>&lt;option value="corsair-dominator-titanium-6000c30" data-state="Absent from 1 completed captures" data-last="2026-10-11" data-price="$674.99" selected>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30&lt;/option>&lt;option value="corsair-vengeance-6000c30" data-state="Present in the latest completed capture" data-last="2026-11-17" data-price="$644.99">Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30&lt;/option>&lt;option value="corsair-vengeance-rgb-6000c30" data-state="Present in the latest completed capture" data-last="2026-11-17" data-price="$654.99">Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30&lt;/option>&lt;option value="gskill-flare-x5-6000c30" data-state="Present in the latest completed capture" data-last="2026-11-17" data-price="$659.99">G.Skill Flare X5 32GB (2x16GB) DDR5-6000 CL30&lt;/option>&lt;option value="gskill-ripjaws-s5-6000c30" data-state="Present in the latest completed capture" data-last="2026-11-17" data-price="$679.99">G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30&lt;/option>&lt;option value="gskill-trident-z5-neo-6000c30" data-state="Present in the latest completed capture" data-last="2026-11-17" data-price="$709.99">G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30&lt;/option>&lt;option value="gskill-trident-z5-rgb-6400c32" data-state="Present in the latest completed capture" data-last="2026-11-17" data-price="$679.99">G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32&lt;/option>&lt;option value="kingston-fury-beast-6000c30" data-state="Present in the latest completed capture" data-last="2026-11-17" data-price="$709.99">Kingston Fury Beast 32GB (2x16GB) DDR5-6000 CL30&lt;/option>&lt;option value="teamgroup-delta-rgb-6000c30" data-state="Present in the latest completed capture" data-last="2026-11-17" data-price="$639.99">TeamGroup T-Force Delta RGB 32GB (2x16GB) DDR5-6000 CL30&lt;/option>&lt;/select>
&lt;/div>
&lt;div class="ram-history__plot" tabindex="0" role="region" aria-label="Scrollable RAM price history chart">
&lt;svg viewBox="0 0 820 315" role="img" aria-labelledby="ram-history-2-svg-title ram-history-2-svg-desc">
&lt;title id="ram-history-2-svg-title">Accepted RAM kit prices in US dollars&lt;/title>
&lt;desc id="ram-history-2-svg-desc">One tracked kit line at a time. Calendar spacing preserves missing days. Separate segments distinguish consecutive observations made using the same method.&lt;/desc>
&lt;line class="ram-history__grid" x1="74" y1="24" x2="776" y2="24" />
&lt;line class="ram-history__grid" x1="74" y1="142" x2="776" y2="142" />
&lt;line class="ram-history__grid" x1="74" y1="260" x2="776" y2="260" />
&lt;text class="ram-history__axis" x="6" y="29" font-size="16">$741&lt;/text>
&lt;text class="ram-history__axis" x="6" y="147" font-size="16">$625&lt;/text>
&lt;text class="ram-history__axis" x="6" y="265" font-size="16">$510&lt;/text>
&lt;text class="ram-history__axis" x="74" y="293" font-size="16">2026-08-12&lt;/text>
&lt;text class="ram-history__axis" x="776" y="293" text-anchor="end" font-size="16">2026-11-17&lt;/text>
&lt;text class="ram-history__axis" x="410" y="311" text-anchor="middle" font-size="16">Calendar date · observed price in USD per 32GB kit&lt;/text>&lt;g data-series="corsair-dominator-titanium-6000c30">&lt;polyline class="ram-history__line" points="74.00,116.78 81.23,116.78 88.47,116.78 95.70,116.78 102.94,116.78" />&lt;polyline class="ram-history__line" points="117.40,116.78 124.64,116.78 131.87,116.78 139.11,116.78 146.34,116.78 153.57,116.78 160.81,116.78" />&lt;polyline class="ram-history__line" points="204.21,116.78 211.45,116.78 218.68,116.78 225.91,116.78" />&lt;polyline class="ram-history__line" points="240.38,116.78 247.62,116.78 254.85,116.78 262.08,116.78" />&lt;polyline class="ram-history__line" points="305.49,91.21 312.72,91.21" />&lt;polyline class="ram-history__line" points="414.00,91.21 421.23,91.21 428.47,91.21 435.70,91.21 442.93,91.21 450.17,91.21" />&lt;polyline class="ram-history__line" points="464.64,91.21 471.87,91.21 479.10,91.21 486.34,91.21" />&lt;circle class="ram-history__point" cx="74.00" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-12 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="81.23" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-13 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="88.47" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-14 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="95.70" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-15 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="102.94" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-16 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="117.40" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-18 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="124.64" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-19 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="131.87" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-20 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="139.11" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-21 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="146.34" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-22 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="153.57" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-23 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="160.81" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-24 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="196.98" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-29 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="204.21" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-30 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="211.45" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-31 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="218.68" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-01 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="225.91" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-02 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="240.38" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-04 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="247.62" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-05 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="254.85" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-06 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="262.08" cy="116.78" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-07 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="305.49" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-13 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="312.72" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-14 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="399.53" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-26 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="414.00" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-28 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="421.23" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-29 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="428.47" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-30 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="435.70" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-01 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="442.93" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-02 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="450.17" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-03 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="464.64" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-05 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="471.87" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-06 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="479.10" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-07 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="486.34" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-08 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="500.81" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-10 · $674.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="508.04" cy="91.21" r="4">&lt;title>Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-11 · $674.99&lt;/title>&lt;/circle>
&lt;/g>&lt;g data-series="corsair-vengeance-6000c30" hidden>&lt;polyline class="ram-history__line" points="74.00,239.54 81.23,239.54 88.47,239.54 95.70,260.00 102.94,239.54" />&lt;polyline class="ram-history__line" points="117.40,239.54 124.64,239.54 131.87,239.54 139.11,239.54 146.34,239.54 153.57,239.54 160.81,239.54" />&lt;polyline class="ram-history__line" points="204.21,239.54 211.45,229.31 218.68,260.00 225.91,229.31" />&lt;polyline class="ram-history__line" points="240.38,229.31 247.62,260.00 254.85,229.31 262.08,260.00" />&lt;polyline class="ram-history__line" points="305.49,219.08 312.72,219.08" />&lt;polyline class="ram-history__line" points="414.00,162.82 421.23,208.85 428.47,208.85 435.70,208.85 442.93,208.85 450.17,208.85" />&lt;polyline class="ram-history__line" points="464.64,141.34 471.87,239.54 479.10,239.54 486.34,239.54" />&lt;circle class="ram-history__point" cx="74.00" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-12 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="81.23" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-13 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="88.47" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-14 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="95.70" cy="260.00" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-15 · $509.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="102.94" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-16 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="117.40" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-18 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="124.64" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-19 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="131.87" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-20 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="139.11" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-21 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="146.34" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-22 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="153.57" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-23 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="160.81" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-24 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="196.98" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-29 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="204.21" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-30 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="211.45" cy="229.31" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-31 · $539.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="218.68" cy="260.00" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-01 · $509.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="225.91" cy="229.31" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-02 · $539.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="240.38" cy="229.31" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-04 · $539.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="247.62" cy="260.00" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-05 · $509.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="254.85" cy="229.31" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-06 · $539.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="262.08" cy="260.00" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-07 · $509.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="305.49" cy="219.08" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-13 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="312.72" cy="219.08" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-14 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="399.53" cy="162.82" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-26 · $604.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="414.00" cy="162.82" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-28 · $604.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="421.23" cy="208.85" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-29 · $559.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="428.47" cy="208.85" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-30 · $559.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="435.70" cy="208.85" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-01 · $559.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="442.93" cy="208.85" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-02 · $559.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="450.17" cy="208.85" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-03 · $559.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="464.64" cy="141.34" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-05 · $625.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="471.87" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-06 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="479.10" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-07 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="486.34" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-08 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="500.81" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-10 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="508.04" cy="239.54" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-11 · $529.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="776.00" cy="121.90" r="4">&lt;title>Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30 · 2026-11-17 · $644.99&lt;/title>&lt;/circle>
&lt;/g>&lt;g data-series="corsair-vengeance-rgb-6000c30" hidden>&lt;polyline class="ram-history__line" points="74.00,219.08 81.23,219.08 88.47,219.08 95.70,219.08 102.94,167.93" />&lt;polyline class="ram-history__line" points="117.40,219.08 124.64,219.08 131.87,219.08 139.11,219.08 146.34,219.08 153.57,219.08 160.81,219.08" />&lt;polyline class="ram-history__line" points="204.21,219.08 211.45,219.08 218.68,152.59 225.91,219.08" />&lt;polyline class="ram-history__line" points="240.38,219.08 247.62,152.59 254.85,152.59 262.08,152.59" />&lt;polyline class="ram-history__line" points="305.49,129.06 312.72,129.06" />&lt;polyline class="ram-history__line" points="414.00,152.59 421.23,198.62 428.47,198.62 435.70,198.62 442.93,198.62 450.17,198.62" />&lt;polyline class="ram-history__line" points="464.64,129.06 471.87,129.06 479.10,129.06 486.34,129.06" />&lt;circle class="ram-history__point" cx="74.00" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-12 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="81.23" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-13 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="88.47" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-14 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="95.70" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-15 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="102.94" cy="167.93" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-16 · $599.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="117.40" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-18 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="124.64" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-19 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="131.87" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-20 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="139.11" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-21 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="146.34" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-22 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="153.57" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-23 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="160.81" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-24 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="196.98" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-29 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="204.21" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-30 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="211.45" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-31 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="218.68" cy="152.59" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-01 · $614.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="225.91" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-02 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="240.38" cy="219.08" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-04 · $549.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="247.62" cy="152.59" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-05 · $614.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="254.85" cy="152.59" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-06 · $614.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="262.08" cy="152.59" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-07 · $614.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="305.49" cy="129.06" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-13 · $637.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="312.72" cy="129.06" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-14 · $637.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="399.53" cy="198.62" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-26 · $569.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="414.00" cy="152.59" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-28 · $614.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="421.23" cy="198.62" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-29 · $569.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="428.47" cy="198.62" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-30 · $569.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="435.70" cy="198.62" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-01 · $569.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="442.93" cy="198.62" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-02 · $569.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="450.17" cy="198.62" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-03 · $569.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="464.64" cy="129.06" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-05 · $637.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="471.87" cy="129.06" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-06 · $637.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="479.10" cy="129.06" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-07 · $637.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="486.34" cy="129.06" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-08 · $637.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="500.81" cy="129.06" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-10 · $637.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="508.04" cy="129.06" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-11 · $637.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="776.00" cy="111.67" r="4">&lt;title>Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-11-17 · $654.99&lt;/title>&lt;/circle>
&lt;/g>&lt;g data-series="gskill-flare-x5-6000c30" hidden>&lt;circle class="ram-history__point" cx="508.04" cy="137.24" r="4">&lt;title>G.Skill Flare X5 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-11 · $629.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="776.00" cy="106.55" r="4">&lt;title>G.Skill Flare X5 32GB (2x16GB) DDR5-6000 CL30 · 2026-11-17 · $659.99&lt;/title>&lt;/circle>
&lt;/g>&lt;g data-series="gskill-ripjaws-s5-6000c30" hidden>&lt;polyline class="ram-history__line" points="218.68,49.32 225.91,172.02" />&lt;polyline class="ram-history__line" points="240.38,172.02 247.62,172.02 254.85,172.02 262.08,172.02" />&lt;circle class="ram-history__point" cx="196.98" cy="172.02" r="4">&lt;title>G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-29 · $595.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="204.21" cy="172.02" r="4">&lt;title>G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-30 · $595.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="218.68" cy="49.32" r="4">&lt;title>G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-01 · $715.94&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="225.91" cy="172.02" r="4">&lt;title>G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-02 · $595.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="240.38" cy="172.02" r="4">&lt;title>G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-04 · $595.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="247.62" cy="172.02" r="4">&lt;title>G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-05 · $595.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="254.85" cy="172.02" r="4">&lt;title>G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-06 · $595.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="262.08" cy="172.02" r="4">&lt;title>G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-07 · $595.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="508.04" cy="106.55" r="4">&lt;title>G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-11 · $659.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="776.00" cy="86.09" r="4">&lt;title>G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30 · 2026-11-17 · $679.99&lt;/title>&lt;/circle>
&lt;/g>&lt;g data-series="gskill-trident-z5-neo-6000c30" hidden>&lt;polyline class="ram-history__line" points="204.21,147.47 211.45,147.47 218.68,147.47 225.91,147.47" />&lt;polyline class="ram-history__line" points="414.00,116.78 421.23,116.78 428.47,116.78" />&lt;circle class="ram-history__point" cx="204.21" cy="147.47" r="4">&lt;title>G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-30 · $619.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="211.45" cy="147.47" r="4">&lt;title>G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-08-31 · $619.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="218.68" cy="147.47" r="4">&lt;title>G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-01 · $619.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="225.91" cy="147.47" r="4">&lt;title>G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-02 · $619.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="399.53" cy="116.78" r="4">&lt;title>G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-26 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="414.00" cy="116.78" r="4">&lt;title>G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-28 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="421.23" cy="116.78" r="4">&lt;title>G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-29 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="428.47" cy="116.78" r="4">&lt;title>G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-09-30 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="508.04" cy="116.78" r="4">&lt;title>G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-11 · $649.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="776.00" cy="55.41" r="4">&lt;title>G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-11-17 · $709.99&lt;/title>&lt;/circle>
&lt;/g>&lt;g data-series="gskill-trident-z5-rgb-6400c32" hidden>&lt;polyline class="ram-history__line" points="218.68,157.70 225.91,24.00" />&lt;polyline class="ram-history__line" points="240.38,157.70 247.62,157.70 254.85,157.70 262.08,157.70" />&lt;polyline class="ram-history__line" points="414.00,127.01 421.23,127.01 428.47,127.01 435.70,127.01 442.93,106.55 450.17,106.55" />&lt;polyline class="ram-history__line" points="464.64,106.55 471.87,106.55 479.10,106.55 486.34,106.55" />&lt;circle class="ram-history__point" cx="204.21" cy="157.70" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-08-30 · $609.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="218.68" cy="157.70" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-09-01 · $609.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="225.91" cy="24.00" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-09-02 · $740.69&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="240.38" cy="157.70" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-09-04 · $609.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="247.62" cy="157.70" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-09-05 · $609.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="254.85" cy="157.70" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-09-06 · $609.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="262.08" cy="157.70" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-09-07 · $609.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="399.53" cy="127.01" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-09-26 · $639.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="414.00" cy="127.01" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-09-28 · $639.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="421.23" cy="127.01" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-09-29 · $639.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="428.47" cy="127.01" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-09-30 · $639.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="435.70" cy="127.01" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-10-01 · $639.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="442.93" cy="106.55" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-10-02 · $659.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="450.17" cy="106.55" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-10-03 · $659.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="464.64" cy="106.55" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-10-05 · $659.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="471.87" cy="106.55" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-10-06 · $659.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="479.10" cy="106.55" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-10-07 · $659.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="486.34" cy="106.55" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-10-08 · $659.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="500.81" cy="106.55" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-10-10 · $659.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="508.04" cy="106.55" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-10-11 · $659.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="776.00" cy="86.09" r="4">&lt;title>G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32 · 2026-11-17 · $679.99&lt;/title>&lt;/circle>
&lt;/g>&lt;g data-series="kingston-fury-beast-6000c30" hidden>&lt;circle class="ram-history__point" cx="508.04" cy="178.16" r="4">&lt;title>Kingston Fury Beast 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-11 · $589.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="776.00" cy="55.41" r="4">&lt;title>Kingston Fury Beast 32GB (2x16GB) DDR5-6000 CL30 · 2026-11-17 · $709.99&lt;/title>&lt;/circle>
&lt;/g>&lt;g data-series="teamgroup-delta-rgb-6000c30" hidden>&lt;circle class="ram-history__point" cx="508.04" cy="229.31" r="4">&lt;title>TeamGroup T-Force Delta RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-10-11 · $539.99&lt;/title>&lt;/circle>&lt;circle class="ram-history__point" cx="776.00" cy="127.01" r="4">&lt;title>TeamGroup T-Force Delta RGB 32GB (2x16GB) DDR5-6000 CL30 · 2026-11-17 · $639.99&lt;/title>&lt;/circle>
&lt;/g>&lt;/svg>
&lt;/div>
&lt;p class="ram-history__status" aria-live="polite">&lt;/p>
&lt;div class="table-wrap">
&lt;table class="ram-history__table">
&lt;caption>Latest accepted point and refresh state for every fixed model identity&lt;/caption>
&lt;colgroup>&lt;col>&lt;col>&lt;col>&lt;col>&lt;col>&lt;/colgroup>
&lt;thead>&lt;tr>&lt;th scope="col">Tracked kit and product ID&lt;/th>&lt;th scope="col">Last accepted&lt;/th>&lt;th scope="col">Price&lt;/th>&lt;th scope="col">$/GB&lt;/th>&lt;th scope="col">Refresh state&lt;/th>&lt;/tr>&lt;/thead>
&lt;tbody>&lt;tr>
&lt;th scope="row">Corsair Dominator Titanium 32GB (2x16GB) DDR5-6000 CL30&lt;code class="ram-history__identity">Product ID: corsair-dominator-titanium-6000c30&lt;/code>&lt;/th>&lt;td>&lt;time datetime="2026-10-11">2026-10-11&lt;/time>&lt;/td>&lt;td data-column="price">$674.99&lt;/td>&lt;td data-column="unit-price">$21.093&lt;/td>
&lt;td>Absent from 1 completed captures&lt;/td>
&lt;/tr>&lt;tr>
&lt;th scope="row">Corsair Vengeance 32GB (2x16GB) DDR5-6000 CL30&lt;code class="ram-history__identity">Product ID: corsair-vengeance-6000c30&lt;/code>&lt;/th>&lt;td>&lt;time datetime="2026-11-17">2026-11-17&lt;/time>&lt;/td>&lt;td data-column="price">$644.99&lt;/td>&lt;td data-column="unit-price">$20.156&lt;/td>
&lt;td>Present in latest completed capture&lt;/td>
&lt;/tr>&lt;tr>
&lt;th scope="row">Corsair Vengeance RGB 32GB (2x16GB) DDR5-6000 CL30&lt;code class="ram-history__identity">Product ID: corsair-vengeance-rgb-6000c30&lt;/code>&lt;/th>&lt;td>&lt;time datetime="2026-11-17">2026-11-17&lt;/time>&lt;/td>&lt;td data-column="price">$654.99&lt;/td>&lt;td data-column="unit-price">$20.468&lt;/td>
&lt;td>Present in latest completed capture&lt;/td>
&lt;/tr>&lt;tr>
&lt;th scope="row">G.Skill Flare X5 32GB (2x16GB) DDR5-6000 CL30&lt;code class="ram-history__identity">Product ID: gskill-flare-x5-6000c30&lt;/code>&lt;/th>&lt;td>&lt;time datetime="2026-11-17">2026-11-17&lt;/time>&lt;/td>&lt;td data-column="price">$659.99&lt;/td>&lt;td data-column="unit-price">$20.625&lt;/td>
&lt;td>Present in latest completed capture&lt;/td>
&lt;/tr>&lt;tr>
&lt;th scope="row">G.Skill Ripjaws S5 32GB (2x16GB) DDR5-6000 CL30&lt;code class="ram-history__identity">Product ID: gskill-ripjaws-s5-6000c30&lt;/code>&lt;/th>&lt;td>&lt;time datetime="2026-11-17">2026-11-17&lt;/time>&lt;/td>&lt;td data-column="price">$679.99&lt;/td>&lt;td data-column="unit-price">$21.250&lt;/td>
&lt;td>Present in latest completed capture&lt;/td>
&lt;/tr>&lt;tr>
&lt;th scope="row">G.Skill Trident Z5 Neo RGB 32GB (2x16GB) DDR5-6000 CL30&lt;code class="ram-history__identity">Product ID: gskill-trident-z5-neo-6000c30&lt;/code>&lt;/th>&lt;td>&lt;time datetime="2026-11-17">2026-11-17&lt;/time>&lt;/td>&lt;td data-column="price">$709.99&lt;/td>&lt;td data-column="unit-price">$22.187&lt;/td>
&lt;td>Present in latest completed capture&lt;/td>
&lt;/tr>&lt;tr>
&lt;th scope="row">G.Skill Trident Z5 RGB 32GB (2x16GB) DDR5-6400 CL32&lt;code class="ram-history__identity">Product ID: gskill-trident-z5-rgb-6400c32&lt;/code>&lt;/th>&lt;td>&lt;time datetime="2026-11-17">2026-11-17&lt;/time>&lt;/td>&lt;td data-column="price">$679.99&lt;/td>&lt;td data-column="unit-price">$21.250&lt;/td>
&lt;td>Present in latest completed capture&lt;/td>
&lt;/tr>&lt;tr>
&lt;th scope="row">Kingston Fury Beast 32GB (2x16GB) DDR5-6000 CL30&lt;code class="ram-history__identity">Product ID: kingston-fury-beast-6000c30&lt;/code>&lt;/th>&lt;td>&lt;time datetime="2026-11-17">2026-11-17&lt;/time>&lt;/td>&lt;td data-column="price">$709.99&lt;/td>&lt;td data-column="unit-price">$22.187&lt;/td>
&lt;td>Present in latest completed capture&lt;/td>
&lt;/tr>&lt;tr>
&lt;th scope="row">TeamGroup T-Force Delta RGB 32GB (2x16GB) DDR5-6000 CL30&lt;code class="ram-history__identity">Product ID: teamgroup-delta-rgb-6000c30&lt;/code>&lt;/th>&lt;td>&lt;time datetime="2026-11-17">2026-11-17&lt;/time>&lt;/td>&lt;td data-column="price">$639.99&lt;/td>&lt;td data-column="unit-price">$20.000&lt;/td>
&lt;td>Present in latest completed capture&lt;/td>
&lt;/tr>&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p class="ram-history__note">&lt;a href="https://techfuelhq.com/data/ram-price-observations.csv" download>Download every accepted observation as CSV&lt;/a>. Historical values remain available after a series becomes stale; a later real observation resumes the line after the gap.&lt;/p>
&lt;script>
(() => {
const root = document.currentScript.closest('.ram-history');
const select = root.querySelector('select');
const status = root.querySelector('.ram-history__status');
const update = () => {
const option = select.selectedOptions[0];
root.querySelectorAll('[data-series]').forEach(group => {
group.hidden = group.dataset.series !== select.value;
});
status.textContent = `${option.textContent}: ${option.dataset.state}. Last accepted ${option.dataset.last} at ${option.dataset.price} per 32GB kit.`;
};
select.disabled = false;
select.addEventListener('change', update);
update();
})();
&lt;/script>
&lt;/section>
&lt;h2 id="notes-from-the-september-13-capture">Notes from the September 13 capture&lt;/h2>
&lt;p>These field notes use the matching rules in effect on September 13. Some listings described here did not survive the later exact-timing correction. Use the corrected offer file for a price attributed to a particular kit.&lt;/p>
&lt;p>&lt;strong>Gate status:&lt;/strong> 3 of 12 tracked kits produced qualifying offers on
2026-09-13, from 640 listings reviewed and 23 eligible offers, so the gate was
closed and no sixth index row was written. &lt;code>ram-price-index.csv&lt;/code> still ends at
2026-09-05. No capture ran from September 8 through September 12, so this
reading follows September 7 by six days. Those days stay empty. The cheapest
qualifying offer was $459.99 at Best Buy ($14.375/GB, Corsair Vengeance RGB).&lt;/p>
&lt;p>&lt;strong>The basket is back to three Corsair lines.&lt;/strong> Corsair Vengeance, Vengeance RGB
and Dominator Titanium qualified. Nothing else did. Those are the same three
lines that made up every capture from August 12 to August 24, before the August
29 method change let G.Skill part numbers count toward the module split and
widened the basket to seven.&lt;/p>
&lt;p>Both G.Skill lines still present on September 7
dropped out. Ripjaws S5 had been $595.99 at Newegg and Trident Z5 RGB $609.99
at Newegg. No allowlisted retailer carried a qualifying listing for either. Neither was seen to reprice on the way out.&lt;/p>
&lt;p>&lt;strong>Dominator Titanium moved for the first time in 22 captures.&lt;/strong> It was $649.99
at Newegg on all 21 earlier captures, from August 12 to September 7. On
September 13 it was $674.99 at Newegg, up 3.8 percent. Same seller, same
listing title. Nothing else changed.&lt;/p>
&lt;p>&lt;strong>The floor fell, and the kit under it is slower than its line.&lt;/strong> Vengeance RGB
read $529.00 at B&amp;amp;H on September 7 and $459.99 at Best Buy on September 13. That is 13 percent lower. The new listing carries a &amp;ldquo;14% OFF&amp;rdquo; tag, and its title
states CL38-44-44-96 on a line labelled CL30. We flagged that defect on August 24
and again on September 2.&lt;/p>
&lt;p>Part of the drop is a discount and part is a looser
kit standing in. It is not a market decline. At $14.375 per
GB it matches the floor of August 31 and September 1, and it ends four captures
pinned at $15.312. Plain Vengeance held $489.99 to the cent for a fifth capture,
now at Best Buy, on a C36 kit.&lt;/p>
&lt;p>&lt;strong>One G.Skill listing came close, and it would not have opened the gate.&lt;/strong> Best
Buy listed &amp;ldquo;G.SKILL Ripjaws F5-6000J3238F16GX2-RS5W&amp;rdquo; at $589.99. It was rejected
for missing model tokens because the title never says S5, even though the
&lt;code>RS5W&lt;/code> suffix names the line. The rule read the prose.&lt;/p>
&lt;p>The same part encodes
CL32 (&lt;code>J3238&lt;/code>) on a CL30 line, so accepting it would have added a looser kit and
moved the count to 4 of 12. Six were needed. Trident Z5 RGB had no allowlisted row carrying its part. The
$509.99 Newegg row under its query is a Trident Z5 6000 kit (&lt;code>-TZ5K&lt;/code>), and its
rejection was correct.&lt;/p>
&lt;p>&lt;strong>The excluded counterfactual got cheaper.&lt;/strong> The exact Flare X5 kit
&lt;code>F5-6000J3636F16GX2-FX5&lt;/code> is $439.99 at Jawa.gg, down from $444.99, and $708.87
at MemoryC.com. Neither seller is on the direct-retailer allowlist, and both
rows were rejected for that alone.&lt;/p>
&lt;p>At $439.99 the kit
would be $13.750/GB, below every accepted observation in the downloadable file,
including the $14.062 of August 12. The exclusion is deliberate, and the rule that
keeps marketplace prices out of this index is still holding its floor up.&lt;/p>
&lt;p>&lt;strong>September 6&amp;rsquo;s apparent increase was the September 4 spec substitution running
backwards.&lt;/strong> G.Skill Ripjaws S5 read $499.99 to $595.99, up 19.2 percent, and
no seller raised a price. The part reverted: &lt;code>F5-6000J3636F16GX2-RS5K&lt;/code> (&lt;code>J3636&lt;/code>
= CL36) back to &lt;code>F5-6000J3040F16GX2-RS5W&lt;/code> (&lt;code>J3040&lt;/code> = CL30). The 09-04 entry
recorded the outbound leg of this same swap as a 16.1 percent drop and called it
a spec substitution rather than a discount.&lt;/p>
&lt;p>&lt;strong>It has now round-tripped, to the
cent and to the part number.&lt;/strong> That CL30 part has sat at $595.99 at Newegg on
2026-08-29, 08-30, 09-02, 09-06 and again on 09-07. Nine days, one price. This
is the
second reading this page published in advance and then saw confirmed, after the
Trident Z5 attribution test. On 09-13 that listing was gone.&lt;/p>
&lt;p>Read eight captures together. &lt;strong>On August 31
the median fell while nothing got cheaper. On September 1 it held while a
tracked kit rose 20 percent. On September 2 it rose 7.5 percent while three kits
held flat and one fell 17 percent.&lt;/strong>&lt;/p>
&lt;p>&lt;strong>On September 4 it fell 8.8 percent while both
cheap lines rose and the floor went up. On September 5 every figure held to the
cent while three of the four listings at the floor vanished. On September 6
there was no figure at all and not one surviving line moved.&lt;/strong>&lt;/p>
&lt;p>&lt;strong>On September 7
there was still no figure, the same five lines qualified, and exactly one of
them rose. On September 13 the basket shrank to three, the flattest line in the
file finally moved, and the floor fell on a slower kit.&lt;/strong>
Eight captures, eight different relationships between a headline number and its
own basket.&lt;/p>
&lt;p>September 6&amp;rsquo;s was the cleanest of them: a six-line gate over a
shifting basket will close on
availability alone, with every tracked price standing still. That is the failure
mode this page exists to make visible, and why no row was manufactured to cover
the gap.&lt;/p>
&lt;p>&lt;strong>Why it opened on 2026-08-30: the rule changed, not the market.&lt;/strong> The gate
had failed on all thirteen captures from 2026-08-12 to 2026-08-29, reaching 3
of 12 and then 4 of 12.&lt;/p>
&lt;p>On 2026-08-29 the module-split matcher was corrected
(method &lt;code>ram-usd-per-gb-discovery-v1&lt;/code> to &lt;code>v2&lt;/code>): it had accepted the marketing
phrase &amp;ldquo;dual channel&amp;rdquo; as a statement of the 2x16 split while rejecting
manufacturer part numbers that encode the same fact, such as G.Skill&amp;rsquo;s
&lt;code>F5-6000J3636F16GX2-FX5&lt;/code>, where &lt;code>16GX2&lt;/code> means 16GB x 2. That is the
manufacturer&amp;rsquo;s own encoding and is strictly more authoritative than the title
prose, so refusing it was an inconsistency in what counted as explicit.&lt;/p>
&lt;p>Three
G.Skill lines qualified as a direct result and the model count moved 4 to 7. The bare word &amp;ldquo;Kit&amp;rdquo; was not accepted, because a &amp;ldquo;32GB kit&amp;rdquo; does
not state its module count. Every series row carries its &lt;code>method_version&lt;/code>, so
v1 and v2 days are never silently compared.&lt;/p>
&lt;h2 id="what-gets-rejected-and-why-thats-the-point">What gets rejected, and why that&amp;rsquo;s the point&lt;/h2>
&lt;p>Of 546 listings reviewed in the first capture, 525 were rejected, each with
recorded reasons: marketplace and third-party sellers (the largest bucket),
listings that don&amp;rsquo;t state the 32GB capacity or the 2x16GB split in the title,
wrong speed for the tracked SKU, used/renewed condition, and prices outside a
sanity band. A price index built on listings a script &lt;em>guessed&lt;/em> about would
be smoother — and worthless. The rejection log ships with the dataset.&lt;/p>
&lt;h2 id="method-exactly">Method, exactly&lt;/h2>
&lt;p>&lt;strong>The method changed on November 17, 2026.&lt;/strong> Rows dated from that day come
from Newegg&amp;rsquo;s affiliate product catalogue, the daily file Newegg publishes to
its affiliates through Rakuten Advertising. I read that day&amp;rsquo;s file and, for
each tracked kit, keep the cheapest listing that passes every rule:&lt;/p>
&lt;ul>
&lt;li>it sits in the catalogue&amp;rsquo;s RAM category;&lt;/li>
&lt;li>its title, brand and manufacturer part number match exactly one tracked
kit, state DDR5, 32GB and the 2x16GB split, and carry that kit&amp;rsquo;s CAS timing
in the title or part number;&lt;/li>
&lt;li>the catalogue marks it in stock;&lt;/li>
&lt;li>the title names no used, refurbished, recertified, renewed or open-box
condition, and no bundle, combo or multi-pack;&lt;/li>
&lt;li>it carries one of Newegg&amp;rsquo;s own item numbers, the form &lt;code>N82E168&lt;/code> plus eight
digits;&lt;/li>
&lt;li>the price sits inside the $60–900 band.&lt;/li>
&lt;/ul>
&lt;p>The price is the catalogue&amp;rsquo;s sale price when the listing has one and its
regular price otherwise. No product page is opened.&lt;/p>
&lt;p>The catalogue gives a title, an item number, a part number, a brand, prices,
a shipping amount and one availability word. It names no seller and no
condition. So these rows are not labeled sold by Newegg, and their condition
rests on the title alone. The item-number rule is the nearest thing to a
seller check. Listings numbered &lt;code>9SI&lt;/code> point at the same product page with a
different item, their own price and often a shipping charge, and I leave them
out. I tested that rule on the catalogue file from September 29: the listings
it accepts matched, to the cent, every price my page captures recorded that
day as sold by Newegg, 24 of 24 across the RAM, GPU and SSD trackers. Shipping
is recorded with the capture and not added to the price. New rows carry
&lt;code>verification_status: retailer_feed&lt;/code> and hold one row per kit.&lt;/p>
&lt;p>A change between October 11 and November 17 is not automatically a
like-for-like price move. The two dates are 37 days apart and use different
methods. Compare the listing titles and part numbers before comparing the
prices.&lt;/p>
&lt;p>From September 26 through October 11, 2026 the method queried each tracked
kit on Newegg and confirmed the selected sold-by-Newegg item on its pinned
product page. The row came from &lt;code>ItemDetail&lt;/code>: &lt;code>FinalPrice&lt;/code> less a real
shipping charge, seller, stock, new/refurbished/open-box flags and fetch
time. Marketplace, refurbished, open-box, out-of-stock, wrong-variant and
out-of-band rows were rejected. Newegg&amp;rsquo;s storefront refused those requests
after October 11, and I retired that collector instead of working around the
refusal.&lt;/p>
&lt;p>The archived captures used Google Shopping (US, English) via DataForSEO&amp;rsquo;s
merchant API. That collection route is retired. The historical method used one
exact-model query per tracked kit.&lt;/p>
&lt;p>Under that historical method, an offer qualified only if the
seller matches a named direct-retailer allowlist (Best Buy, Newegg, B&amp;amp;H,
Micro Center, Adorama, Walmart first-party, and peers — marketplace suffixes
excluded), the title states the exact kit line, speed, 32GB capacity, and
2x16GB split (a &amp;ldquo;Dual Channel&amp;rdquo; declaration on a 32GB listing counts as the
split), condition is new, and the USD price sits inside a $60–900 band.&lt;/p>
&lt;p>The
band&amp;rsquo;s ceiling was raised from $500 on day one when real direct-retailer
offers at $469–499 for the &lt;em>cheapest&lt;/em> kit proved the old ceiling was written
for a market that no longer exists — that correction is in the change
log.&lt;/p>
&lt;p>Amazon is excluded by design (see FAQ). The full collector, product basket,
tests, raw responses, and rejection logs are in the site&amp;rsquo;s repository.&lt;/p>
&lt;h2 id="use-the-data-cc-by-40">Use the data (CC BY 4.0)&lt;/h2>
&lt;p>Download the corrected observations:
&lt;a href="https://techfuelhq.com/data/ram-price-observations.csv" download type="text/csv">ram-price-observations.csv&lt;/a> — one row per
qualifying offer, with capture date, kit, price, $/GB, seller, and
verification status. Rows dated from November 17, 2026 read
&lt;code>Newegg listing (seller not stated)&lt;/code> in the seller column and &lt;code>retailer_feed&lt;/code>
as their status. The October 11 exact-CAS correction is reproducible from
the catalog and rebuild script; it removed only rows whose title and
manufacturer part number failed the line&amp;rsquo;s timing requirement. Its
&lt;a href="https://techfuelhq.com/data/ram-price-correction-2026-10-11.json" download type="application/json">machine-readable correction record&lt;/a>
publishes the before-and-after hashes, row counts and manufacturer sources.&lt;/p>
&lt;p>The corrected
daily index series publishes at
&lt;a href="https://techfuelhq.com/data/ram-price-index.csv" download type="text/csv">ram-price-index.csv&lt;/a> (median cheapest $/GB across
kits, one row per UTC day, each row stamped with the &lt;code>method_version&lt;/code> that
produced it). The dates that survive the correction are August 30, September
1 and September 2, each with six exact-CAS lines; October 11 and November 17
follow them. License: &lt;a href="https://creativecommons.org/licenses/by/4.0/" rel="noopener">Creative Commons Attribution 4.0&lt;/a> — attribute
as &amp;ldquo;TechFuelHQ DDR5 RAM Price Index&amp;rdquo; linking to this page.&lt;/p>
&lt;p>Rows through October 11, 2026 are also on
&lt;a href="https://www.kaggle.com/datasets/lowellwoodiblessi/ddr5-ram-price-observations-2026" rel="noopener">Kaggle&lt;/a>
for discovery and reuse. Rows from the catalogue are published on this site
only. This page remains canonical because it carries the gate state, method
changes, and correction history beside the file.&lt;/p>
&lt;p>Context for the crisis itself: the
&lt;a href="https://techfuelhq.com/articles/ram-ssd-price-crisis-2026/">RAM &amp;amp; SSD price crisis explainer&lt;/a> and
the &lt;a href="https://techfuelhq.com/articles/ddr5-ram-buying-guide-2025/">DDR5 buying guide&lt;/a> — the guide&amp;rsquo;s
price-tracking data is what earned this site its first external news citation,
and this index is that work made repeatable.&lt;/p>
&lt;h2 id="weekly-market-context">Outside reference: US prices from Pricify&lt;/h2>
&lt;section aria-labelledby="weekly-market-context" data-external-market-context="ram">
&lt;p>For the week ending &lt;time datetime="2026-11-08">2026-11-08&lt;/time> (US Eastern), &lt;a href="https://pricify.ai/">Pricify&lt;/a> published week-end prices in US dollars. We checked one exact part number in its 100-product sample.&lt;/p>
&lt;div class="table-wrap" role="region" aria-label="Pricify historical item prices" tabindex="0">
&lt;table>
&lt;caption>Selected exact parts in the 2026-W45 release&lt;/caption>
&lt;thead>&lt;tr>&lt;th scope="col">Part / manufacturer number&lt;/th>&lt;th scope="col">Week-end item low&lt;/th>&lt;th scope="col">Venue in the source&lt;/th>&lt;/tr>&lt;/thead>
&lt;tbody>&lt;tr>
&lt;th scope="row">Vengeance RGB 32 GB DDR5-6000 CL30&lt;br>&lt;small>CMH32GX5M2B6000Z30K&lt;/small>&lt;/th>
&lt;td>$599.97&lt;/td>&lt;td>Amazon&lt;/td>
&lt;/tr>&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>These are the publisher’s historical item prices for new products sold by the retailer. Physical stores can count, the source does not give a delivered total with shipping and tax, and a prior reading may carry forward for about three days. A missing part is not evidence that it sold out. These rows do not update TechFuelHQ’s own observations or establish a price you can buy at today.&lt;/p>
&lt;p>Selected and reformatted from &lt;a href="https://raw.githubusercontent.com/pricify-ai/pc-hardware-prices/9507089fec375be2f86d309c8ff37a6190043947/data/2026/W45/json/rams.live.json">Pricify’s original weekly JSON&lt;/a>, &lt;a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0&lt;/a>. Retrieved &lt;time datetime="2026-11-13T23:24:17Z">2026-11-13 UTC&lt;/time>.
&lt;a href="https://techfuelhq.com/data/weekly-market-context/2026-W45-9507089fec375be2f86d309c8ff37a6190043947.csv" download>Download the selected weekly rows (CSV)&lt;/a> ·
&lt;a href="https://techfuelhq.com/data/weekly-market-context/2026-W45-9507089fec375be2f86d309c8ff37a6190043947.json" download>Identifiers, source hashes and dates (JSON)&lt;/a> ·
&lt;a href="https://raw.githubusercontent.com/pricify-ai/pc-hardware-prices/9507089fec375be2f86d309c8ff37a6190043947/METHODOLOGY.md">Publisher’s method&lt;/a>.&lt;/p>
&lt;/section>
&lt;h2 id="change-log">Change log&lt;/h2>
&lt;ul>
&lt;li>
&lt;p>&lt;strong>1.1.0 (2026-11-17)&lt;/strong> — source and method change, and the first capture
since October 11. Rows from this date come from Newegg&amp;rsquo;s affiliate product
catalogue under method &lt;code>ram-usd-per-gb-newegg-affiliate-feed-v1&lt;/code>, with
&lt;code>verification_status: retailer_feed&lt;/code>. The catalogue names no seller, so
these rows do not repeat the sold-by-Newegg statement of the September 26
to October 11 captures; they require one of Newegg&amp;rsquo;s own item numbers
instead. First capture under the new method: 8 of 12 kits have a price and
the index row reads a median of $20.938 per GB and a median cheapest kit of
$669.99. The October 11 row, under the page method, read $19.937 per GB and
$637.99 across nine kits. Kingston Fury Renegade 6400 CL32 and Crucial Pro
6000 CL36 are listed only under other item numbers, and no listing of the
tracked Corsair Dominator Titanium 6000 CL30 or G.Skill Flare X5 5600 CL36
kit qualified. The two G.Skill RGB lines (Trident Z5 Neo RGB and Trident Z5
RGB) now require the RGB family name in the listing: the catalogue lists
their non-RGB siblings beside them, and the shorter rule would have put a
non-RGB kit under an RGB label. No earlier row was changed. The Kaggle copy
ends at October 11.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>1.0.9 (2026-10-11)&lt;/strong> — exact-CAS correction. Manufacturer specifications
identify October 10&amp;rsquo;s Kingston &lt;code>KF560C36BBE2K2-32&lt;/code> as CL36 and TeamGroup
&lt;code>FF3D532G6000HC38JDC01&lt;/code> as CL38. The catalog now requires a maker-documented
timing signature for every line. A tested deterministic rebuild filtered the
public observations from 621 to 405 rows and the gated index from 17 to 3
rows. October 10 now has 4 of 12 exact-CAS lines, so the gate is closed. Raw
capture receipts were not modified; older entries below describe the
superseded classifier.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>1.0.8 (2026-09-13)&lt;/strong> — twenty-second capture, six days after the last,
since no capture ran from 2026-09-08 through 2026-09-12. 640 listings
reviewed, 23 eligible offers, 3 of 12 model lines, &lt;strong>gate closed&lt;/strong> for a third
straight capture and now at half the minimum. No sixth index row was written
and &lt;code>ram-price-index.csv&lt;/code> still ends at 2026-09-05. Both G.Skill lines left,
which returns the basket to the three Corsair lines of mid-August.&lt;/p>
&lt;p>Dominator
Titanium rose from $649.99 to $674.99 at Newegg, its first move in 22
captures. The floor fell to $459.99 / $14.375 per GB on a Vengeance RGB
listing whose title states CL38 on a CL30-labelled line. The excluded Flare
X5 part fell to $439.99 at Jawa.gg.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>1.0.7 (2026-09-07)&lt;/strong> — twenty-first capture: 640 listings reviewed, 20
eligible offers, 5 of 12 model lines, &lt;strong>gate closed&lt;/strong> for a second straight
capture one kit short of the minimum. No sixth index row was written and
&lt;code>ram-price-index.csv&lt;/code> still ends at 2026-09-05. The same five lines qualified
as on 09-06. Four held to the cent and one rose.&lt;/p>
&lt;p>Corsair Vengeance RGB went
$499.99 to $529.00, up 5.8 percent, ending the streak in which nothing in the
basket got more expensive. The floor stayed $489.99 / $15.312 per GB for
a fourth capture while the cheapest seller alternated between B&amp;amp;H and Central
Computers. G.Skill Flare X5 was absent a second capture and still has not
repriced; the $504.99 rows returned under its query were Trident Z5 parts
(&lt;code>-TZ5K&lt;/code>) and were rejected correctly.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>1.0.6 (2026-09-06)&lt;/strong> — twentieth capture: 600 listings reviewed, 21
eligible offers, 5 of 12 model lines, &lt;strong>gate closed&lt;/strong> one kit short of the
minimum after two captures sitting exactly on it. No sixth index row was
written and &lt;code>ram-price-index.csv&lt;/code> still ends at 2026-09-05. Four of the five
surviving lines held their cheapest price to the cent, and nothing in the
basket got more expensive.&lt;/p>
&lt;p>Availability closed this gate; no price did. The
line that left, G.Skill Flare X5, had held $499.99 to the cent for six
straight captures and never repriced — no allowlisted retailer listed the 32GB
kit at all. That exact part sold at $444.99 at Jawa.gg, off the allowlist and
excluded by design, which would have been $13.906 per GB and a new series low.
The lone apparent increase, Ripjaws S5 up 19.2 percent, is the 09-04 spec
substitution round-tripping back to its CL30 part. &lt;code>publish_ready&lt;/code> stays False.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>1.0.5 (2026-09-05)&lt;/strong> — nineteenth capture: 596 listings reviewed, 21
eligible offers, 6 of 12 model lines, gate open at exactly the minimum for a
second capture. Fifth index row: median $15.625 per GB, min $15.312, max
$20.312, median cheapest kit $499.99 — every field identical to the 09-04 row,
a first for this series.&lt;/p>
&lt;p>All six lines held their cheapest price to the cent,
so for once the headline is not disguising movement underneath. What moved is
depth: eligible offers fell 24 to 21, and the four listings tied at $489.99 on
09-04 became one. Trident Z5 RGB made the same Newegg-to-Best Buy swap that
registered a 21.4 percent jump on 09-02 and held $609.99 to the cent, testing
and confirming the shopfront-attribution reading. The floor is again set by a
CL36 part on a CL30-labelled line, whose true CL30 part sits $60 dearer at the
same retailer the same day. &lt;code>publish_ready&lt;/code> stays False.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>1.0.4 (2026-09-04)&lt;/strong> — eighteenth capture: 560 listings reviewed, 24
eligible offers, 6 of 12 model lines, gate open at exactly the minimum. Fourth
index row: median $15.625 per GB, min $15.312, max $20.312, median cheapest
kit $499.99. No capture ran on 2026-09-03, so this row follows 09-02 by two
days, and nothing is interpolated across the gap. The median fell 8.8 percent
while the floor rose.&lt;/p>
&lt;p>Trident Z5 RGB round-tripped to $609.99 at Newegg on the
identical part, confirming the 09-02 entry&amp;rsquo;s shopfront-attribution reading.
The largest apparent drop, Ripjaws S5 down 16.1 percent, is a CL30-to-CL36
part substitution rather than a discount. Both cheap lines rose. Two lines left the
pool and three of the remaining six sit at exactly $499.99, so the median is a
three-way tie. &lt;code>publish_ready&lt;/code> stays False.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>1.0.3 (2026-09-02)&lt;/strong> — seventeenth capture: 560 listings reviewed, 24
eligible offers, 8 of 12 model lines, gate open a second day. Third index row:
median $17.125 per GB, min $14.675, max $23.147, median cheapest kit $547.99.
The median rose 7.5 percent while three lines held flat to the cent, one fell
16.8 percent and a new cheaper eighth line joined; without that new line the
median would have been $18.625.&lt;/p>
&lt;p>Two G.Skill parts swapped retailers in
opposite directions at a spread of roughly 20 percent. The floor rose to
$469.59 on the CL38-in-a-CL30-line listing first flagged on 2026-08-24.
&lt;code>publish_ready&lt;/code> stays False.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>1.0.2 (2026-09-01)&lt;/strong> — sixteenth capture: 718 listings reviewed, 25 eligible
offers, 7 of 12 model lines, gate reopened. Second index row: median $15.937
per GB, min $14.375, max $22.373, median cheapest kit $509.99. Median, minimum
and median kit price all returned to the cent to their 2026-08-30 values while
G.Skill Ripjaws S5 rose 20.1 percent on the identical part — the move sat at
the top of the distribution, where the median could not see it.&lt;/p>
&lt;p>This entry was
written on 2026-09-02; the 09-01 commit bumped &lt;code>dataset_version&lt;/code> to 1.0.2
without recording the release here, the same omission corrected for 1.0.0 one
day earlier.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>1.0.1 (2026-08-31)&lt;/strong> — fifteenth capture: 680 listings reviewed, 21 eligible
offers, 5 of 12 model lines. The activation gate closed again one day after
opening, and no index row was written. Same method (v2) on both days, so the
rule-change caveat that framed the opening does not apply here. Two lines left
the set and none joined, both of them the most expensive (Ripjaws S5 $595.99,
Trident Z5 RGB 6400 $609.99, both Newegg).&lt;/p>
&lt;p>Four of the five surviving lines
held price to the cent. The fifth changed seller at a steady price. Cheapest
qualifying offer unchanged at $459.99 / $14.375 per GB, Vengeance RGB at B&amp;amp;H.
The median $/GB fell from $15.937 to $15.625 with no kit getting cheaper. That
is a basket-composition artefact, and the page does not present it as a move
in price.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>1.0.0 (2026-08-30)&lt;/strong> — fourteenth capture and the first published index row:
680 listings reviewed, 21 eligible offers, 7 of 12 model lines against a
minimum of 6, so the activation gate opened for the first time. Median
cheapest $15.937 per GB, min $14.375, max $20.312, median cheapest kit
$509.99, method &lt;code>ram-usd-per-gb-discovery-v2&lt;/code>.&lt;/p>
&lt;p>It opened because the
acceptance rule changed rather than because supply improved: the module-split
matcher was widened on 2026-08-29 to read manufacturer part numbers such as
&lt;code>F5-6000J3636F16GX2-FX5&lt;/code>, which qualified three G.Skill lines and moved the
count from 4 to 7. &lt;code>publish_ready&lt;/code> stays False, because direct-retailer stock
is still unconfirmed. This entry was written on 2026-08-31; the 08-30 commit
bumped &lt;code>dataset_version&lt;/code> to 1.0.0 without recording the release here.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>0.9.7 (2026-08-24)&lt;/strong> — twelfth capture: 706 listings reviewed, 16 eligible
offers, the same 3 of 12 model lines. The $459.99 run ended after six days
when its B&amp;amp;H listing left the result set. Nothing was repriced. Zero of the
13 listings common to Aug 23 and Aug 24 changed price.
New cheapest qualifying offer $469.59 / $14.675 per GB, Vengeance RGB at
Best Buy.&lt;/p>
&lt;p>New flag, recorded not corrected: that listing is a CL38 part
(CMH32GX5M2B6000C38) satisfying a line labelled CL30, whose true CL30 kits
sit at $619.99. Plain Vengeance clean for a third capture, flat at $479.99 /
$15.00 per GB. The activation gate stays closed at 3 of 6 required lines.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>0.9.6 (2026-08-23)&lt;/strong> — eleventh capture: 716 listings reviewed, 16
eligible offers, the same 3 of 12 model lines, cheapest qualifying offer
flat at $459.99 / $14.375 per GB for a sixth day since Aug 18. The RGB
exclusion reproduced on the plain Vengeance line: 0 of 7 rows RGB-titled,
holding independently at $479.99 / $15.00 per GB on the same Central
Computers listing as Aug 22. The activation gate stays closed at 3 of 6
required model lines.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>0.9.5 (2026-08-22)&lt;/strong> — tenth capture: 624 listings reviewed, 17 eligible
offers, the same 3 of 12 model lines, cheapest qualifying offer flat at
$459.99 / $14.375 per GB since Aug 18. First capture with the RGB exclusion
active on the plain Vengeance line: 0 of its 9 rows are RGB-titled (5 of 13
were on Aug 21), and it now prices independently at $479.99 / $15.00 per GB.
The activation gate stays closed at 3 of 6 required model lines.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>0.9.4 (2026-08-21)&lt;/strong> — captures seven through nine (Aug 19: 590 reviewed /
24 eligible; Aug 20: 616 / 24; Aug 21: 680 / 21), the same 3 of 12 model
lines, cheapest qualifying offer flat at $459.99 / $14.375 per GB since
Aug 18. Correction: the page prose was resynced to the capture the rendered
table serves. The drift class the 0.9.2 entry named had recurred, because
the daily collector updates the CSV but not this page.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>0.9.3 (2026-08-18)&lt;/strong> — sixth successful capture: 583 listings reviewed,
25 eligible offers, the same 3 of 12 qualifying model lines, and a new
discovery-stage floor of $459.99 / $14.375 per GB at B&amp;amp;H. The activation
gate remains closed; no &lt;code>ram-price-index.csv&lt;/code> row was manufactured.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>0.9.2 (2026-08-14)&lt;/strong> — day-three capture (24 qualifying offers, same 3
Corsair kits, cheapest unchanged at $449.99). Correction: the rendered
observation table had advanced to the 2026-08-14 capture while the prose
above it still described only days one and two, so a reader met a table
dated later than anything the page acknowledged. The prose now names the
capture the table actually serves.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>0.9.1 (2026-08-13)&lt;/strong> — earlier of two day-two captures: 581 listings
reviewed, 23 qualifying offers across 3 kits, cheapest unchanged. A later
scheduled capture reviewed 538 and retained 26 qualifying offers; that later
run replaced the date-level evidence directory and is reported above. The
earlier four-file capture remains in repository history at commit &lt;code>b9e56c1a&lt;/code>.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>0.9.0 (2026-08-12)&lt;/strong> — pilot capture and method publication. Four method
corrections made against measured evidence on day one, all recorded: price
ceiling $500 → $900 (285 real listings died on the stale band); &amp;ldquo;Dual
Channel&amp;rdquo; accepted as an explicit module-split marker (Newegg writes Trident
Z5 Neo kits this way); per-product offer de-duplication (a Corsair offer
was being consumed and mis-rejected under another kit&amp;rsquo;s query); basket v1.1
swapped two kits with zero direct-retailer presence (ADATA XPG Lancer,
Patriot Viper Venom) for Dominator Titanium 6000 and Flare X5 5600.&lt;/p>
&lt;/li>
&lt;/ul></description></item><item><title>NVMe SSD Price Index: Dated $/TB for 2TB Drives at Newegg (Pilot)</title><link>https://techfuelhq.com/data/ssd-price-index/</link><pubDate>Mon, 14 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/data/ssd-price-index/</guid><atom:updated>2026-11-17T15:25:34Z</atom:updated><description>&lt;p>By &lt;a href="https://techfuelhq.com/author/lk-wood-iv/">LK Wood IV&lt;/a> · Published 2026-09-14 · ~4 min read · St. Louis County, MO&lt;/p>
&lt;h2 id="the-short-version">The short version&lt;/h2>
&lt;p>NAND pricing turned upward through 2026 alongside DRAM, and the $/TB figures
that circulate are mostly undated deal posts. This page is a dated, checkable
record: the cheapest qualifying listing price for twelve 2TB NVMe drives
&lt;strong>at Newegg&lt;/strong>, with the method, the acceptance rules, the rejection reasons
and the raw data published beside the numbers. Since November 17, 2026 the
prices come from Newegg&amp;rsquo;s affiliate catalogue, which does not say who sells a
listing. Rows dated September 26 through October 11, 2026 were confirmed as
sold by Newegg on the product page. Rows dated before September 26, 2026 came
from a list of named direct US retailers.&lt;/p>
&lt;p>It is labeled a &lt;strong>pilot&lt;/strong> because the index metric has an activation gate,
and the gate status is printed here verbatim rather than worked around.&lt;/p>
&lt;p>&lt;a href="https://techfuelhq.com/data/deal-or-mirage/">Deal or Mirage&lt;/a> puts these drives in one table with the tracked graphics cards and DDR5 kits, each with a label worked out from its own dated prices.&lt;/p>
&lt;h2 id="compare-the-dated-offers">Compare the dated offers&lt;/h2>
&lt;p>These drives have the same marketed capacity: 2 TB. The lower dollar price is also the lower price per TB, but a 2 TB label alone does not make a heatsink model the same listing as a bare drive. Use the full retailer title when comparing captures. A drive absent from the later table has no recorded price on that date.&lt;/p>
&lt;style>.price-capture-compare { margin: 1.25rem 0 2rem; min-width: 0; }
.price-capture-compare > p:first-child { border-inline-start: 3px solid var(--accent); padding-inline-start: .8rem; }
.price-capture-compare .table-wrap { max-width: 100%; overflow-x: auto; }
.price-capture-compare table { width: 100%; font-variant-numeric: tabular-nums; }
.price-capture-compare caption { text-align: left; color: var(--heading); font-weight: 650; }
.price-capture-compare th[scope=row] { min-width: 12rem; text-align: left; }
.price-capture-compare [data-price] { white-space: nowrap; }
.price-part-mismatch { display: block; font-size: .83rem; font-weight: 500; line-height: 1.45; margin: 0 0 .5rem; white-space: normal; }
.price-field-label { display: none; }
.price-capture-compare summary { cursor: pointer; color: var(--accent); min-height: 2.75rem; padding-block: .55rem; }
.price-capture-compare small { display: block; font-weight: normal; line-height: 1.5; overflow-wrap: anywhere; }
.price-capture-compare :is(summary, [tabindex]) { --focus-offset: var(--focus-offset-region); }
.price-capture-evidence { border-block: 1px solid var(--border-strong); padding: .35rem 0; }
.price-capture-evidence > summary { font-weight: 650; }
.price-capture-evidence code { overflow-wrap: anywhere; white-space: normal; }
@media (max-width: 640px) {
.price-capture-compare .price-offers-table { display: block; width: 100%; min-width: 0; }
.price-offers-table caption { display: block; padding: .6rem .75rem; white-space: normal; }
.price-offers-table thead { position: absolute; width: 1px; height: 1px; overflow: hidden; clip-path: inset(50%); }
.price-offers-table tbody { display: block; }
.price-offers-table tbody tr { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); border-top: 1px solid var(--border-strong); }
.price-offers-table tbody tr:has([data-pair]) { grid-template-columns: repeat(3, minmax(0, 1fr)); }
.price-capture-compare .price-offers-table th[scope=row] { grid-column: 1 / -1; display: block; min-width: 0; padding: .2rem .75rem 0; white-space: normal; }
.price-offers-table td { display: block; padding: .25rem .65rem .65rem; border: none; white-space: normal; }
.price-offers-table .price-field-label { display: block; font-size: .75rem; font-weight: 600; color: var(--text-muted); }
}
&lt;/style>&lt;div class="price-capture-compare" data-price-reader="ssd">&lt;p id="price-reader-ssd-0-note">&lt;strong>November 17, 2026:&lt;/strong> 8 offers in the archived file. Open a model name to read the retailer’s listing title. These are dated observations; check stock and price before buying.&lt;/p>&lt;p data-pair-rule="withheld">The preceding observation date was October 11, 2026. At least one calendar day in between has no published offer. A price change across the gap is withheld.&lt;/p>&lt;div class="table-wrap" tabindex="0" role="region" aria-labelledby="price-reader-ssd-0-caption">
&lt;table class="price-offers-table" role="table" aria-describedby="price-reader-ssd-0-note">&lt;caption id="price-reader-ssd-0-caption">SSD offers, lowest recorded price first · 2026-11-17 UTC&lt;/caption>
&lt;thead role="rowgroup">&lt;tr role="row">&lt;th scope="col" role="columnheader">Model and seller&lt;/th>&lt;th scope="col" role="columnheader">Price (USD)&lt;/th>&lt;th scope="col" role="columnheader">USD per TB&lt;/th>&lt;/tr>&lt;/thead>
&lt;tbody role="rowgroup">&lt;tr role="row" data-product="wd-blue-sn5100-2tb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>WD Blue SN5100 2TB · Newegg listing (seller not stated)&lt;/summary>&lt;small>SanDisk WD_Blue SN5100 2TB NVMe SSD - M.2 2280, PCIe Gen 4.0, Internal Solid State Drive - Read Speeds Up to 7,100MB/s, Upgrade Storage for...&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$279.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per TB&lt;/span>$140.0&lt;/td>&lt;/tr>&lt;tr role="row" data-product="kingston-nv3-2tb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>Kingston NV3 2TB · Newegg listing (seller not stated)&lt;/summary>&lt;small>Kingston NV3 M.2 2280 2TB PCIe 4.0 x4 NVMe Internal Solid State Drive (SSD) SNV3S/2000G Up to 6000 MB/s&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$294.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per TB&lt;/span>$147.5&lt;/td>&lt;/tr>&lt;tr role="row" data-product="teamgroup-mp44-2tb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>TEAMGROUP MP44 2TB · Newegg listing (seller not stated)&lt;/summary>&lt;small>Team Group MP44 M.2 2280 2TB PCIe 4.0 x4 with NVMe TLC Laptop &amp;amp; Desktop &amp;amp; NUC &amp;amp; NAS, PS5 Compatible, Internal Solid State Drive (SSD), (R/W Speed...&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$319.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per TB&lt;/span>$160.0&lt;/td>&lt;/tr>&lt;tr role="row" data-product="teamgroup-t-force-g50-2tb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>TEAMGROUP T-FORCE G50 2TB · Newegg listing (seller not stated)&lt;/summary>&lt;small>Team Group T-FORCE G50 M.2 2280 2TB PCIe 4.0 x4 with NVMe 1.4 TLC Internal Solid State Drive (SSD) TM8FFE002T0C129&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$319.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per TB&lt;/span>$160.0&lt;/td>&lt;/tr>&lt;tr role="row" data-product="wd-black-sn7100-2tb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>WD_BLACK SN7100 2TB · Newegg listing (seller not stated)&lt;/summary>&lt;small>WD_Black SN7100 2TB NVMe SSD - Gen4 PCIe, M.2 2280, Up to 7,250 MB/s Read Speed, Up to 6,900 MB/s Write Speed, Next Gen TLC 3D NAND, for Laptops,...&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$339.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per TB&lt;/span>$170.0&lt;/td>&lt;/tr>&lt;tr role="row" data-product="teamgroup-cardea-a440-2tb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>TEAMGROUP T-FORCE CARDEA A440 2TB · Newegg listing (seller not stated)&lt;/summary>&lt;small>Team Group T-FORCE CARDEA A440 M.2 2280 2TB PCIe Gen 4.0 x4 NVMe 1.4 TLC with Dram cache, PS5 Compatible, Internal Solid State Drive (SSD)...&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$341.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per TB&lt;/span>$171.0&lt;/td>&lt;/tr>&lt;tr role="row" data-product="samsung-990-pro-2tb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>Samsung 990 PRO 2TB · Newegg listing (seller not stated)&lt;/summary>&lt;small>SAMSUNG 990 PRO 2TB SSD, PCIe Gen4 M.2 2280, Seq. Read Speeds Up-to 7,450MB/s for High End Computing, Gaming, and Heavy Duty Workstations...&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$389.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per TB&lt;/span>$195.0&lt;/td>&lt;/tr>&lt;tr role="row" data-product="samsung-9100-pro-2tb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>Samsung 9100 PRO 2TB · Newegg listing (seller not stated)&lt;/summary>&lt;small>SAMSUNG SSD 9100 PRO 2TB, PCIe 5.0x4 M.2 2280, Seq. Read Speeds Up to 14,700MB/s, Best for AI Computing, Gaming, and Heavy Duty Workstations...&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$399.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">USD per TB&lt;/span>$200.0&lt;/td>&lt;/tr>&lt;/tbody>&lt;/table>
&lt;/div>&lt;p>&lt;strong>On 2026-10-11 only:&lt;/strong> Crucial P310 2TB; Kingston KC3000 2TB; Samsung 990 EVO Plus 2TB; WD_BLACK SN850X 2TB. No price was carried into the later capture.&lt;/p>&lt;details class="price-capture-evidence">&lt;summary>See coverage, gaps and source files&lt;/summary>
&lt;p>&lt;a href="https://techfuelhq.com/data/ssd-price-observations.csv" download>Download all 145 offer rows (CSV)&lt;/a>. They span 15 distinct UTC dates, from 2026-09-14 through 2026-11-17. A missing date means there is no published offer row for that date. The recorded method on 2026-11-17 was &lt;code>ssd-usd-per-tb-newegg-affiliate-feed-v1&lt;/code>.&lt;/p>&lt;p>&lt;a href="https://techfuelhq.com/data/ssd-price-index.csv" download>Download the 12 recorded index rows (CSV)&lt;/a>. Each median uses the models that qualified on that date. Different membership or a new method can move a median even when no individual listing changed price.&lt;/p>&lt;div class="table-wrap" tabindex="0" role="region" aria-labelledby="price-reader-ssd-0-series">&lt;table>&lt;caption id="price-reader-ssd-0-series">Published index rows, with their original methods&lt;/caption>&lt;thead>&lt;tr>&lt;th scope="col">UTC date&lt;/th>&lt;th scope="col">Models qualified / queried&lt;/th>&lt;th scope="col">Median USD per TB&lt;/th>&lt;th scope="col">Recorded method&lt;/th>&lt;/tr>&lt;/thead>&lt;tbody>&lt;tr>&lt;th scope="row">2026-09-29&lt;/th>&lt;td>12 / 12&lt;/td>&lt;td>$180.5&lt;/td>&lt;td>&lt;code>ssd-usd-per-tb-newegg-direct-v3&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-09-30&lt;/th>&lt;td>12 / 12&lt;/td>&lt;td>$180.5&lt;/td>&lt;td>&lt;code>ssd-usd-per-tb-newegg-direct-v3&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-01&lt;/th>&lt;td>12 / 12&lt;/td>&lt;td>$180.5&lt;/td>&lt;td>&lt;code>ssd-usd-per-tb-newegg-direct-v3&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-02&lt;/th>&lt;td>12 / 12&lt;/td>&lt;td>$169.5&lt;/td>&lt;td>&lt;code>ssd-usd-per-tb-newegg-direct-v3&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-03&lt;/th>&lt;td>12 / 12&lt;/td>&lt;td>$169.5&lt;/td>&lt;td>&lt;code>ssd-usd-per-tb-newegg-direct-v3&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-05&lt;/th>&lt;td>12 / 12&lt;/td>&lt;td>$169.5&lt;/td>&lt;td>&lt;code>ssd-usd-per-tb-newegg-direct-v3&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-06&lt;/th>&lt;td>12 / 12&lt;/td>&lt;td>$169.5&lt;/td>&lt;td>&lt;code>ssd-usd-per-tb-newegg-direct-v3&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-07&lt;/th>&lt;td>12 / 12&lt;/td>&lt;td>$169.0&lt;/td>&lt;td>&lt;code>ssd-usd-per-tb-newegg-direct-v3&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-08&lt;/th>&lt;td>12 / 12&lt;/td>&lt;td>$169.5&lt;/td>&lt;td>&lt;code>ssd-usd-per-tb-newegg-direct-v3&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-10&lt;/th>&lt;td>12 / 12&lt;/td>&lt;td>$169.5&lt;/td>&lt;td>&lt;code>ssd-usd-per-tb-newegg-direct-v3&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-11&lt;/th>&lt;td>12 / 12&lt;/td>&lt;td>$169.5&lt;/td>&lt;td>&lt;code>ssd-usd-per-tb-newegg-direct-v3&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-11-17&lt;/th>&lt;td>8 / 12&lt;/td>&lt;td>$165.0&lt;/td>&lt;td>&lt;code>ssd-usd-per-tb-newegg-affiliate-feed-v1&lt;/code>&lt;/td>&lt;/tr>
&lt;/tbody>&lt;/table>&lt;/div>
&lt;/details>&lt;/div>
&lt;h2 id="latest-capture">Latest capture&lt;/h2>
&lt;p>&lt;strong>Collection status:&lt;/strong> Captures from November 17, 2026 read that day&amp;rsquo;s Newegg affiliate catalogue file. Captures from September 26 through October 11, 2026 read Newegg&amp;rsquo;s product pages. No capture ran between those two periods, and the method differs across the gap. While fewer than six of the twelve tracked drives qualify, the gate stays closed and no index row is written. The basket grew from eight drives to twelve on September 28, 2026, so a capture made before that change counts against eight. The block below names the latest capture; check Newegg for current price and stock.&lt;/p>
&lt;!-- auto:capture -->
&lt;p>&lt;strong>Latest capture, November 17, 2026 (UTC), method &lt;code>ssd-usd-per-tb-newegg-affiliate-feed-v1&lt;/code>:&lt;/strong> Newegg&amp;rsquo;s affiliate catalogue file for that date had 351 listings naming a tracked model; 8 passed every rule, and 8 of 12 tracked drives have a price. The index metric activates at 6, so the gate is open and an index row was written for this date. Every row carries &lt;code>verification_status: retailer_feed&lt;/code>: the price, title, part number and in-stock flag are the catalogue&amp;rsquo;s own. The catalogue names no seller and no condition, and nothing was checked against the product page.&lt;/p>
&lt;p>Cheapest qualifying listing: &lt;strong>$279.99&lt;/strong> (WD Blue SN5100 2TB, 140 $/TB).&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Line&lt;/th>
&lt;th scope="col" style="text-align: right">Cheapest qualifying listing&lt;/th>
&lt;th scope="col" style="text-align: right">$/TB&lt;/th>
&lt;th scope="col">Newegg item number&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Line">WD Blue SN5100 2TB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$279.99&lt;/td>
&lt;td style="text-align: right" data-label="$/TB">140&lt;/td>
&lt;td data-label="Newegg item number">N82E16820173681&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">Kingston NV3 2TB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$294.99&lt;/td>
&lt;td style="text-align: right" data-label="$/TB">147.5&lt;/td>
&lt;td data-label="Newegg item number">N82E16820242903&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">TEAMGROUP MP44 2TB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$319.99&lt;/td>
&lt;td style="text-align: right" data-label="$/TB">160&lt;/td>
&lt;td data-label="Newegg item number">N82E16820985037&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">TEAMGROUP T-FORCE G50 2TB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$319.99&lt;/td>
&lt;td style="text-align: right" data-label="$/TB">160&lt;/td>
&lt;td data-label="Newegg item number">N82E16820985144&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">WD_BLACK SN7100 2TB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$339.99&lt;/td>
&lt;td style="text-align: right" data-label="$/TB">170&lt;/td>
&lt;td data-label="Newegg item number">N82E16820250275&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">TEAMGROUP T-FORCE CARDEA A440 2TB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$341.99&lt;/td>
&lt;td style="text-align: right" data-label="$/TB">171&lt;/td>
&lt;td data-label="Newegg item number">N82E16820331727&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">Samsung 990 PRO 2TB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$389.99&lt;/td>
&lt;td style="text-align: right" data-label="$/TB">195&lt;/td>
&lt;td data-label="Newegg item number">N82E16820147861&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">Samsung 9100 PRO 2TB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$399.99&lt;/td>
&lt;td style="text-align: right" data-label="$/TB">200&lt;/td>
&lt;td data-label="Newegg item number">N82E16820147903&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">WD_BLACK SN850X 2TB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">none: its listings carry other item numbers&lt;/td>
&lt;td style="text-align: right" data-label="$/TB">-&lt;/td>
&lt;td data-label="Newegg item number">-&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">Kingston KC3000 2TB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">none: its listings carry other item numbers&lt;/td>
&lt;td style="text-align: right" data-label="$/TB">-&lt;/td>
&lt;td data-label="Newegg item number">-&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">Samsung 990 EVO Plus 2TB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">none: its listings carry other item numbers&lt;/td>
&lt;td style="text-align: right" data-label="$/TB">-&lt;/td>
&lt;td data-label="Newegg item number">-&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">Crucial P310 2TB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">none: its listings carry other item numbers&lt;/td>
&lt;td style="text-align: right" data-label="$/TB">-&lt;/td>
&lt;td data-label="Newegg item number">-&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>This block is rewritten with every capture; the dated commentary below it is not.&lt;/p>
&lt;!-- /auto:capture -->
&lt;p>This is a 2TB internal M.2 NVMe basket. It can answer a broad SSD-cost question
as a dated 2TB benchmark and can compare price per gigabyte or terabyte within
that scope. It does not establish a 1TB, 4TB, 8TB, SATA, external-drive, or
live-deal price. Those need a matching capacity and form factor from a dated
retailer-owned capture. Hardware class and role belong in the &lt;a href="https://techfuelhq.com/articles/ssd-tier-list/">SSD tier
list&lt;/a> and &lt;a href="https://techfuelhq.com/articles/best-nvme-ssd-homelab-2026/">role-based NVMe
guide&lt;/a>.&lt;/p>
&lt;h2 id="recent-qualifying-observations">Recent qualifying observations&lt;/h2>
&lt;p>The file below accumulates one row per qualifying offer for each capture
date. The table below shows the two latest capture dates so current rows are
easy to find. Download the complete CSV history below it for all earlier rows.
Both views use the same raw file at build time.&lt;/p>
&lt;div class="table-wrap csv-table">
&lt;table aria-describedby="csv-table-note-1">
&lt;caption>Recent observations from the latest 2 capture dates, oldest to newest&lt;/caption>
&lt;thead>
&lt;tr>&lt;th scope="col">Capture Date UTC&lt;/th>&lt;th scope="col">Product Label&lt;/th>&lt;th scope="col">Title&lt;/th>&lt;th scope="col">Seller&lt;/th>&lt;th scope="col">Price USD&lt;/th>&lt;th scope="col">USD per Tb&lt;/th>&lt;th scope="col">Verification Status&lt;/th>&lt;/tr>
&lt;/thead>
&lt;tbody>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>Samsung 990 PRO 2TB&lt;/td>&lt;td>SAMSUNG 990 PRO 2TB SSD, PCIe Gen4 M.2 2280, Seq. Read Speeds Up-to 7,450MB/s for High End Computing, Gaming, and Heavy Duty Workstations (MZ-V9P2T0B/AM) Non-Heatsink&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>389.99&lt;/td>&lt;td>195.0&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>WD_BLACK SN850X 2TB&lt;/td>&lt;td>WD_BLACK 2TB SN850X NVMe Internal Gaming SSD Solid State Drive - Gen4 PCIe, M.2 2280, Up to 7,300 MB/s - WDS200T2X0E&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>429.99&lt;/td>&lt;td>215.0&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>Kingston KC3000 2TB&lt;/td>&lt;td>Kingston KC3000 M.2 2280 2TB PCI-Express 4.0 x4 3D TLC Internal Solid State Drive (SSD) SKC3000D/2048G&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>499.99&lt;/td>&lt;td>250.0&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>TEAMGROUP MP44 2TB&lt;/td>&lt;td>Team Group MP44 M.2 2280 2TB PCIe 4.0 x4 with NVMe TLC Laptop &amp;amp; Desktop &amp;amp; NUC &amp;amp; NAS, PS5 Compatible, Internal Solid State Drive (SSD), (R/W Speed up to 7,400/7,000MB/s) TM8FPW002T0C101&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>325.99&lt;/td>&lt;td>163.0&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>Samsung 990 EVO Plus 2TB&lt;/td>&lt;td>SAMSUNG 990 EVO PLUS SSD 2TB, PCIe Gen 4x4 | Gen 5x2 M.2 2280, Speeds Up-to 7,250 MB/s, Upgrade Storage for PC/Laptops, HMB Technology and Intelligent Turbowrite 2.0 (MZ-V9S2T0B/AM)&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>369.99&lt;/td>&lt;td>185.0&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>WD_BLACK SN7100 2TB&lt;/td>&lt;td>WD_BLACK SN7100 M.2 2280 2TB PCI-Express 4.0 x4 TLC 3D NAND Internal Solid State Drive (SSD) WDS200T4X0E&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>319.99&lt;/td>&lt;td>160.0&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>TEAMGROUP T-FORCE CARDEA A440 2TB&lt;/td>&lt;td>Team Group T-FORCE CARDEA A440 M.2 2280 2TB PCIe Gen 4.0 x4 NVMe 1.4 TLC with Dram cache, PS5 Compatible, Internal Solid State Drive (SSD) TM8FPZ002T0C327&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>351.99&lt;/td>&lt;td>176.0&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>WD Blue SN5100 2TB&lt;/td>&lt;td>WD Blue SN5100 2TB NVMe SSD, PCIe Gen 4.0, up to 7,100 MB/s read speeds&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>279.99&lt;/td>&lt;td>140.0&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>Crucial P310 2TB&lt;/td>&lt;td>Crucial P310 2TB 2280 PCIe Gen4 3D NAND NVMe M.2 SSD - Up to 7,100 MB/s - Shift up to Gen4, with Acronis Offer, Internal Solid State Drive (PC)&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>309.99&lt;/td>&lt;td>155.0&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>Kingston NV3 2TB&lt;/td>&lt;td>Kingston NV3 M.2 2280 2TB PCIe 4.0 x4 NVMe Internal Solid State Drive (SSD) SNV3S/2000G Up to 6000 MB/s&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>294.99&lt;/td>&lt;td>147.5&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>TEAMGROUP T-FORCE G50 2TB&lt;/td>&lt;td>Team Group T-FORCE G50 M.2 2280 2TB PCIe 4.0 x4 with NVMe 1.4 TLC Internal Solid State Drive (SSD) TM8FFE002T0C129&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>324.99&lt;/td>&lt;td>162.5&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>Samsung 9100 PRO 2TB&lt;/td>&lt;td>SAMSUNG SSD 9100 PRO 2TB, PCIe 5.0x4 M.2 2280, Seq. Read Speeds Up to 14,700MB/s, Best for AI Computing, Gaming, and Heavy Duty Workstations (MZ-VAP2T0B/AM)&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>399.99&lt;/td>&lt;td>200.0&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>Samsung 990 PRO 2TB&lt;/td>&lt;td>SAMSUNG 990 PRO 2TB SSD, PCIe Gen4 M.2 2280, Seq. Read Speeds Up-to 7,450MB/s for High End Computing, Gaming, and Heavy Duty Workstations...&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>389.99&lt;/td>&lt;td>195.0&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>TEAMGROUP MP44 2TB&lt;/td>&lt;td>Team Group MP44 M.2 2280 2TB PCIe 4.0 x4 with NVMe TLC Laptop &amp;amp; Desktop &amp;amp; NUC &amp;amp; NAS, PS5 Compatible, Internal Solid State Drive (SSD), (R/W Speed...&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>319.99&lt;/td>&lt;td>160.0&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>WD_BLACK SN7100 2TB&lt;/td>&lt;td>WD_Black SN7100 2TB NVMe SSD - Gen4 PCIe, M.2 2280, Up to 7,250 MB/s Read Speed, Up to 6,900 MB/s Write Speed, Next Gen TLC 3D NAND, for Laptops,...&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>339.99&lt;/td>&lt;td>170.0&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>TEAMGROUP T-FORCE CARDEA A440 2TB&lt;/td>&lt;td>Team Group T-FORCE CARDEA A440 M.2 2280 2TB PCIe Gen 4.0 x4 NVMe 1.4 TLC with Dram cache, PS5 Compatible, Internal Solid State Drive (SSD)...&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>341.99&lt;/td>&lt;td>171.0&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>WD Blue SN5100 2TB&lt;/td>&lt;td>SanDisk WD_Blue SN5100 2TB NVMe SSD - M.2 2280, PCIe Gen 4.0, Internal Solid State Drive - Read Speeds Up to 7,100MB/s, Upgrade Storage for...&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>279.99&lt;/td>&lt;td>140.0&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>Kingston NV3 2TB&lt;/td>&lt;td>Kingston NV3 M.2 2280 2TB PCIe 4.0 x4 NVMe Internal Solid State Drive (SSD) SNV3S/2000G Up to 6000 MB/s&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>294.99&lt;/td>&lt;td>147.5&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>TEAMGROUP T-FORCE G50 2TB&lt;/td>&lt;td>Team Group T-FORCE G50 M.2 2280 2TB PCIe 4.0 x4 with NVMe 1.4 TLC Internal Solid State Drive (SSD) TM8FFE002T0C129&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>319.99&lt;/td>&lt;td>160.0&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>Samsung 9100 PRO 2TB&lt;/td>&lt;td>SAMSUNG SSD 9100 PRO 2TB, PCIe 5.0x4 M.2 2280, Seq. Read Speeds Up to 14,700MB/s, Best for AI Computing, Gaming, and Heavy Duty Workstations...&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>399.99&lt;/td>&lt;td>200.0&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p class="csv-table__note" id="csv-table-note-1">Showing 20 of 145 observations from the latest 2 capture dates. &lt;a href="https://techfuelhq.com/data/ssd-price-observations.csv" download>Download the complete CSV history&lt;/a>. The table is rendered from that file at build time.&lt;/p>
&lt;h2 id="method-exactly">Method, exactly&lt;/h2>
&lt;p>&lt;strong>The method changed on November 17, 2026.&lt;/strong> Rows dated from that day come
from Newegg&amp;rsquo;s affiliate product catalogue, the daily file Newegg publishes to
its affiliates through Rakuten Advertising. I read that day&amp;rsquo;s file and, for
each tracked drive, keep the cheapest listing that passes every rule:&lt;/p>
&lt;ul>
&lt;li>it sits in the catalogue&amp;rsquo;s storage-device category;&lt;/li>
&lt;li>its title, brand and manufacturer part number name exactly one tracked
drive, state 2TB and no other capacity, and describe an internal NVMe SSD
that is not a heatsink version;&lt;/li>
&lt;li>the catalogue marks it in stock;&lt;/li>
&lt;li>the title names no used, refurbished, recertified, renewed or open-box
condition, and no bundle, combo or multi-pack;&lt;/li>
&lt;li>it carries one of Newegg&amp;rsquo;s own item numbers, the form &lt;code>N82E168&lt;/code> plus eight
digits;&lt;/li>
&lt;li>the price sits between $40 and $1,200.&lt;/li>
&lt;/ul>
&lt;p>The price is the catalogue&amp;rsquo;s sale price when the listing has one and its
regular price otherwise. No product page is opened.&lt;/p>
&lt;p>The catalogue gives a title, an item number, a part number, a brand, prices,
a shipping amount and one availability word. It names no seller and no
condition. So these rows are not labeled sold by Newegg, and their condition
rests on the title alone. The item-number rule is the nearest thing to a
seller check. Listings numbered &lt;code>9SI&lt;/code> point at the same product page with a
different item, their own price and often a shipping charge, and I leave them
out. I tested that rule on the catalogue file from September 29: the listings
it accepts matched, to the cent, every price my page captures recorded that
day as sold by Newegg, 24 of 24 across the SSD, GPU and RAM trackers. Shipping
is recorded with the capture and not added to the price. New rows carry
&lt;code>verification_status: retailer_feed&lt;/code> and hold one row per drive.&lt;/p>
&lt;p>A change between October 11 and November 17 is not automatically a
like-for-like price move. The two dates are 37 days apart and use different
methods. A drive with a price on October 11 and none on November 17 was
listed that day only under other item numbers; it did not necessarily leave
Newegg.&lt;/p>
&lt;p>From September 26 through October 11, 2026 the method queried each tracked
drive on Newegg and confirmed the selected sold-by-Newegg item on its pinned
product page. The row came from &lt;code>ItemDetail&lt;/code>: &lt;code>FinalPrice&lt;/code> less a real
shipping charge, seller, stock, new/refurbished/open-box flags and fetch
time. Marketplace, refurbished, open-box, out-of-stock, wrong-model and
out-of-band rows were rejected. Newegg&amp;rsquo;s storefront refused those requests
after October 11, and I retired that collector instead of working around the
refusal.&lt;/p>
&lt;p>&lt;strong>The basket changed on September 28, 2026.&lt;/strong> I track twelve 2TB M.2 2280
drives: Samsung 990 PRO, Samsung 990 EVO Plus, Samsung 9100 PRO, WD_BLACK
SN850X, WD_BLACK SN7100, WD Blue SN5100, Kingston KC3000, Kingston NV3, Crucial
P310, TEAMGROUP MP44, TEAMGROUP T-FORCE G50 and TEAMGROUP T-FORCE CARDEA A440.
Ten are PCIe 4.0. The 990 EVO Plus runs at PCIe 4.0 x4 or 5.0 x2
(&lt;a href="https://www.samsung.com/us/business/memory-storage/nvme-ssd/990-evo-plus-gen4-nvme-ssd-2tb-sku-mz-v9s2t0b-am/" rel="noopener">Samsung&amp;rsquo;s specification&lt;/a>).
The 9100 PRO is &lt;a href="https://download.semiconductor.samsung.com/resources/data-sheet/Samsung_NVMe_SSD_9100_PRO_Datasheet_Rev.1.0.pdf" rel="noopener">PCIe 5.0&lt;/a>. I picked the earlier basket of
eight for results across retailers. At Newegg alone, two of the eight
qualified and the gate never opened.&lt;/p>
&lt;p>Four drives left because Newegg itself does not sell them: Crucial T500, Lexar
NM790, Solidigm P44 Pro and SK hynix Platinum P41. A search of Newegg&amp;rsquo;s own
listings for each model name returned nothing that day.&lt;/p>
&lt;p>Two drives this page showed with no Newegg listing were on sale from Newegg
itself. The TEAMGROUP MP44 was in the September 26 and September 28 captures
at $325.99, rejected because my title rule required &amp;ldquo;teamgroup&amp;rdquo; where the
listing says &amp;ldquo;Team Group&amp;rdquo;. The Kingston KC3000 never came back from the
search. My query named &amp;ldquo;NVMe&amp;rdquo;, a word its listing does not use. Both rules are
fixed. Both drives stay, and queries now name the model and nothing else.&lt;/p>
&lt;p>Eight drives joined, chosen from the 41 Newegg-sold 2TB M.2 2280 listings I
found that day: two more Samsung lines, two more from WD, the Kingston NV3, the
Crucial P310 and two TEAMGROUP T-FORCE drives. Each tracked drive is the bare
M.2 2280 version. A heatsink version, another capacity, an M.2 2230 version or
a sibling model such as the MP44Q is rejected by title. The method name moved
to &lt;code>ssd-usd-per-tb-newegg-direct-v3&lt;/code> with the basket, so every series row says
which basket produced it.&lt;/p>
&lt;p>The archived captures used Google Shopping (US, English) via DataForSEO&amp;rsquo;s
merchant API. That collection route is retired. The historical method used one
exact-model query per tracked drive. Under that historical method, an offer
qualified only if the
seller matches a named direct-retailer allowlist (Best Buy, Newegg, B&amp;amp;H,
Micro Center, Adorama, Walmart first-party, and peers — marketplace suffixes
excluded), the title names the exact model line and the 2TB capacity and
identifies an internal NVMe or M.2 drive, condition is new, and the USD price
sits inside a sanity band. Dollars per terabyte is the price divided by two.&lt;/p>
&lt;p>The index metric (median cheapest $/TB across drives) activates at six of
twelve qualifying drives on the same day. Below that, the observations still
publish; the index row does not. The minimum was six before the basket
changed. I left it there.&lt;/p>
&lt;h2 id="use-the-data-cc-by-40">Use the data (CC BY 4.0)&lt;/h2>
&lt;p>Download every observation:
&lt;a href="https://techfuelhq.com/data/ssd-price-observations.csv" download type="text/csv">ssd-price-observations.csv&lt;/a> — one row per
qualifying offer with capture date, drive, price, $/TB, seller and
verification status. Rows dated from November 17, 2026 read
&lt;code>Newegg listing (seller not stated)&lt;/code> in the seller column and &lt;code>retailer_feed&lt;/code>
as their status. When at least six of the twelve drives qualify,
that day&amp;rsquo;s row is added to &lt;code>/data/ssd-price-index.csv&lt;/code>. License:
&lt;a href="https://creativecommons.org/licenses/by/4.0/" rel="noopener">Creative Commons Attribution 4.0&lt;/a>
— attribute as &amp;ldquo;TechFuelHQ NVMe SSD Price Index&amp;rdquo; linking to this page.&lt;/p>
&lt;p>Sizing a drive for its write life? The
&lt;a href="https://techfuelhq.com/tools/ssd-endurance-calculator/">SSD endurance calculator&lt;/a> turns TBW into
years. For hardware class rather than price, the
&lt;a href="https://techfuelhq.com/articles/ssd-tier-list/">SSD tier list&lt;/a> tiers NVMe drives by PCIe
generation, NAND type and cache, and it covers seven of the twelve tracked
here. For why the prices look like this, the
&lt;a href="https://techfuelhq.com/articles/ram-ssd-price-crisis-2026/">RAM and SSD price crisis explainer&lt;/a> is
this dataset&amp;rsquo;s narrative companion, and the
&lt;a href="https://techfuelhq.com/data/ram-price-index/">DDR5 RAM price index&lt;/a> is its sibling.&lt;/p>
&lt;h2 id="weekly-market-context">Outside reference: US prices from Pricify&lt;/h2>
&lt;section aria-labelledby="weekly-market-context" data-external-market-context="ssd">
&lt;p>For the week ending &lt;time datetime="2026-11-08">2026-11-08&lt;/time> (US Eastern), &lt;a href="https://pricify.ai/">Pricify&lt;/a> published week-end prices in US dollars. We checked one exact part number in its 100-product sample.&lt;/p>
&lt;div class="table-wrap" role="region" aria-label="Pricify historical item prices" tabindex="0">
&lt;table>
&lt;caption>Selected exact parts in the 2026-W45 release&lt;/caption>
&lt;thead>&lt;tr>&lt;th scope="col">Part / manufacturer number&lt;/th>&lt;th scope="col">Week-end item low&lt;/th>&lt;th scope="col">Venue in the source&lt;/th>&lt;/tr>&lt;/thead>
&lt;tbody>&lt;tr>
&lt;th scope="row">990 PRO 2 TB, non-heatsink US model&lt;br>&lt;small>MZ-V9P2T0B/AM&lt;/small>&lt;/th>
&lt;td>$389.99&lt;/td>&lt;td>Micro Center (in store)&lt;/td>
&lt;/tr>&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>These are the publisher’s historical item prices for new products sold by the retailer. Physical stores can count, the source does not give a delivered total with shipping and tax, and a prior reading may carry forward for about three days. A missing part is not evidence that it sold out. These rows do not update TechFuelHQ’s own observations or establish a price you can buy at today.&lt;/p>
&lt;p>Selected and reformatted from &lt;a href="https://raw.githubusercontent.com/pricify-ai/pc-hardware-prices/9507089fec375be2f86d309c8ff37a6190043947/data/2026/W45/json/ssd.live.json">Pricify’s original weekly JSON&lt;/a>, &lt;a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0&lt;/a>. Retrieved &lt;time datetime="2026-11-13T23:24:17Z">2026-11-13 UTC&lt;/time>.
&lt;a href="https://techfuelhq.com/data/weekly-market-context/2026-W45-9507089fec375be2f86d309c8ff37a6190043947.csv" download>Download the selected weekly rows (CSV)&lt;/a> ·
&lt;a href="https://techfuelhq.com/data/weekly-market-context/2026-W45-9507089fec375be2f86d309c8ff37a6190043947.json" download>Identifiers, source hashes and dates (JSON)&lt;/a> ·
&lt;a href="https://raw.githubusercontent.com/pricify-ai/pc-hardware-prices/9507089fec375be2f86d309c8ff37a6190043947/METHODOLOGY.md">Publisher’s method&lt;/a>.&lt;/p>
&lt;/section>
&lt;h2 id="change-log">Change log&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>0.11.0 (2026-11-17)&lt;/strong> — source and method change, and the first capture
since October 11. Rows from this date come from Newegg&amp;rsquo;s affiliate product
catalogue under method &lt;code>ssd-usd-per-tb-newegg-affiliate-feed-v1&lt;/code>, with
&lt;code>verification_status: retailer_feed&lt;/code>. The catalogue names no seller, so
these rows do not repeat the sold-by-Newegg statement of the September 26
to October 11 captures; they require one of Newegg&amp;rsquo;s own item numbers
instead. First capture under the new method: 8 of 12 drives have a price
and the index row reads a median of $165.00 per TB and a median cheapest
price of $329.99. The October 11 row, under the page method, read $169.50
per TB and $338.99 across all twelve. WD_BLACK SN850X, Kingston KC3000,
Samsung 990 EVO Plus and Crucial P310 have no row for this date: the file
lists them only under other item numbers. The basket did not change and no
earlier row was changed.&lt;/li>
&lt;li>&lt;strong>0.10.0 (2026-09-28)&lt;/strong> — basket re-baselined to drives Newegg sells itself.
Twelve drives are tracked, up from eight; the six-drive minimum is unchanged;
the method is &lt;code>ssd-usd-per-tb-newegg-direct-v3&lt;/code>. Left: Crucial T500, Lexar
NM790, Solidigm P44 Pro and SK hynix Platinum P41, none of which Newegg
itself sells. Kept: Samsung 990 PRO and WD_BLACK SN850X, the two that
qualified on September 26 and 28, and Kingston KC3000 and TEAMGROUP MP44,
which Newegg sells and my query and title rule had missed. Joined:
Samsung 990 EVO Plus, WD_BLACK SN7100, TEAMGROUP T-FORCE CARDEA A440, WD Blue
SN5100, Crucial P310, Kingston NV3, TEAMGROUP T-FORCE G50 and Samsung 9100
PRO, the basket&amp;rsquo;s one PCIe 5.0 x4 drive. Rows already in the observations file
are unchanged, and no index row existed to restate. This is the first entry
since the source moved from Google Shopping results to Newegg&amp;rsquo;s own listings
on September 26 (method &lt;code>ssd-usd-per-tb-newegg-direct-v2&lt;/code>).&lt;/li>
&lt;li>&lt;strong>0.9.0 (2026-09-14)&lt;/strong> — pilot publication and first published capture. A
single unpublished pilot capture from 2026-08-11 is retained in the
evidence archive and is not part of the observations file.&lt;/li>
&lt;/ul></description></item><item><title>GPU Price Index: Dated Street Price vs MSRP at Newegg (Pilot)</title><link>https://techfuelhq.com/data/gpu-price-index/</link><pubDate>Mon, 14 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/data/gpu-price-index/</guid><atom:updated>2026-11-17T15:25:02Z</atom:updated><description>&lt;p>By &lt;a href="https://techfuelhq.com/author/lk-wood-iv/">LK Wood IV&lt;/a> · Published 2026-09-14 · ~4 min read · St. Louis County, MO&lt;/p>
&lt;h2 id="the-short-version">The short version&lt;/h2>
&lt;p>Graphics card prices spent the whole RTX 50 and RX 9000 generation above
MSRP, and most of the numbers that circulate are undated screenshots. This
page is a dated, checkable record: the cheapest qualifying listing price for
eight current cards &lt;strong>at Newegg&lt;/strong>, each scored against its launch MSRP, with
the method, the acceptance rules, the rejection reasons and the raw data
published beside the numbers. Since November 17, 2026 the prices come from
Newegg&amp;rsquo;s affiliate catalogue, which does not say who sells a listing. The
method section says exactly what that changes. Rows dated before September
26, 2026 came from a list of named direct US retailers.&lt;/p>
&lt;p>It is labeled a &lt;strong>pilot&lt;/strong> because the index metric has an activation gate,
and the gate status is printed here verbatim rather than worked around.&lt;/p>
&lt;p>&lt;a href="https://techfuelhq.com/tools/keep-it-or-upgrade/">Keep It or Upgrade&lt;/a> uses the latest capture below to price an upgrade against the card you own. &lt;a href="https://techfuelhq.com/data/deal-or-mirage/">Deal or Mirage&lt;/a> puts these cards in one table with the tracked DDR5 kits and SSDs, each with its percent over launch price and a label worked out from its own dated prices.&lt;/p>
&lt;h2 id="compare-the-dated-offers">Compare the dated offers&lt;/h2>
&lt;p>The cheapest card and the smallest premium over launch price can be different cards. The first is a dollar comparison; the second compares each card with its own launch MSRP or SEP. A board partner, memory size or factory-overclock variant can change even under the same chip name. Open the listing titles before comparing two offers.&lt;/p>
&lt;style>.price-capture-compare { margin: 1.25rem 0 2rem; min-width: 0; }
.price-capture-compare > p:first-child { border-inline-start: 3px solid var(--accent); padding-inline-start: .8rem; }
.price-capture-compare .table-wrap { max-width: 100%; overflow-x: auto; }
.price-capture-compare table { width: 100%; font-variant-numeric: tabular-nums; }
.price-capture-compare caption { text-align: left; color: var(--heading); font-weight: 650; }
.price-capture-compare th[scope=row] { min-width: 12rem; text-align: left; }
.price-capture-compare [data-price] { white-space: nowrap; }
.price-part-mismatch { display: block; font-size: .83rem; font-weight: 500; line-height: 1.45; margin: 0 0 .5rem; white-space: normal; }
.price-field-label { display: none; }
.price-capture-compare summary { cursor: pointer; color: var(--accent); min-height: 2.75rem; padding-block: .55rem; }
.price-capture-compare small { display: block; font-weight: normal; line-height: 1.5; overflow-wrap: anywhere; }
.price-capture-compare :is(summary, [tabindex]) { --focus-offset: var(--focus-offset-region); }
.price-capture-evidence { border-block: 1px solid var(--border-strong); padding: .35rem 0; }
.price-capture-evidence > summary { font-weight: 650; }
.price-capture-evidence code { overflow-wrap: anywhere; white-space: normal; }
@media (max-width: 640px) {
.price-capture-compare .price-offers-table { display: block; width: 100%; min-width: 0; }
.price-offers-table caption { display: block; padding: .6rem .75rem; white-space: normal; }
.price-offers-table thead { position: absolute; width: 1px; height: 1px; overflow: hidden; clip-path: inset(50%); }
.price-offers-table tbody { display: block; }
.price-offers-table tbody tr { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); border-top: 1px solid var(--border-strong); }
.price-offers-table tbody tr:has([data-pair]) { grid-template-columns: repeat(3, minmax(0, 1fr)); }
.price-capture-compare .price-offers-table th[scope=row] { grid-column: 1 / -1; display: block; min-width: 0; padding: .2rem .75rem 0; white-space: normal; }
.price-offers-table td { display: block; padding: .25rem .65rem .65rem; border: none; white-space: normal; }
.price-offers-table .price-field-label { display: block; font-size: .75rem; font-weight: 600; color: var(--text-muted); }
}
&lt;/style>&lt;div class="price-capture-compare" data-price-reader="gpu">&lt;p id="price-reader-gpu-0-note">&lt;strong>November 17, 2026:&lt;/strong> 7 offers in the archived file. Open a model name to read the retailer’s listing title. These are dated observations; check stock and price before buying.&lt;/p>&lt;p data-pair-rule="withheld">The preceding observation date was October 11, 2026. At least one calendar day in between has no published offer. A price change across the gap is withheld.&lt;/p>&lt;div class="table-wrap" tabindex="0" role="region" aria-labelledby="price-reader-gpu-0-caption">
&lt;table class="price-offers-table" role="table" aria-describedby="price-reader-gpu-0-note">&lt;caption id="price-reader-gpu-0-caption">GPU offers, lowest recorded price first · 2026-11-17 UTC&lt;/caption>
&lt;thead role="rowgroup">&lt;tr role="row">&lt;th scope="col" role="columnheader">Model and seller&lt;/th>&lt;th scope="col" role="columnheader">Price (USD)&lt;/th>&lt;th scope="col" role="columnheader">Vs. launch price&lt;/th>&lt;/tr>&lt;/thead>
&lt;tbody role="rowgroup">&lt;tr role="row" data-product="radeon-rx-9060-xt-16gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>AMD Radeon RX 9060 XT 16GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>ASUS Dual Radeon RX 9060 XT Graphics Card DUAL-RX9060XT-16G&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$789.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:100%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;126.4%&lt;/span>&lt;/span>&lt;/td>&lt;/tr>&lt;tr role="row" data-product="geforce-rtx-5060-ti-16gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>NVIDIA GeForce RTX 5060 Ti 16GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>PNY DUAL FAN OC GeForce RTX 5060 Ti 16GB 128-Bit GDDR7 PCI Express 5.0 x8 DLSS 4.0 Graphics Card RTX 5060 Ti 16GB DUAL FAN OC VCG5060T16DFXPB1-O&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$799.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:86%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;86.5%&lt;/span>&lt;/span>&lt;/td>&lt;/tr>&lt;tr role="row" data-product="geforce-rtx-5070-12gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>NVIDIA GeForce RTX 5070 12GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>MSI Ventus GeForce RTX 5070 Graphics Card RTX 5070 12G VENTUS 3X OC&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$919.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:68%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;67.6%&lt;/span>&lt;/span>&lt;/td>&lt;/tr>&lt;tr role="row" data-product="radeon-rx-9070-xt-16gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>AMD Radeon RX 9070 XT 16GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>ASRock Steel Legend Radeon RX 9070 XT Graphics Card RX9070XT SL 16G&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$999.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:67%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;66.9%&lt;/span>&lt;/span>&lt;/td>&lt;/tr>&lt;tr role="row" data-product="radeon-rx-9070-16gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>AMD Radeon RX 9070 16GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>ASUS PRIME Radeon RX 907016GB 256-Bit GDDR6 PCI Express 5.0 RDNA 4 Graphics Card PRIME-RX9070-O16G&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$1019.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:86%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;85.8%&lt;/span>&lt;/span>&lt;/td>&lt;/tr>&lt;tr role="row" data-product="geforce-rtx-5070-ti-16gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>NVIDIA GeForce RTX 5070 Ti 16GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>MSI SHADOW GeForce RTX 5070 Ti Graphics Card RTX 5070 TI 16G SHADOW 3X OC&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$1409.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:88%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;88.2%&lt;/span>&lt;/span>&lt;/td>&lt;/tr>&lt;tr role="row" data-product="geforce-rtx-5080-16gb">&lt;th scope="row" role="rowheader">&lt;details>&lt;summary>NVIDIA GeForce RTX 5080 16GB · Newegg listing (seller not stated)&lt;/summary>&lt;small>PNY ARGB OC GeForce RTX 5080 16GB 256-Bit GDDR7 DLSS 4.0 PCI Express 5.0 x16 Graphics Card VCG508016TFXXPB1-O&lt;/small>&lt;/details>&lt;/th>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Price (USD)&lt;/span>&lt;span data-price>$2499.99&lt;/span>&lt;/td>&lt;td role="cell">&lt;span class="price-field-label" aria-hidden="true">Vs. launch price&lt;/span>&lt;span class="v3-price-delta v3-price-delta--over">&lt;span class="v3-price-delta__track">&lt;span class="v3-price-delta__fill" style="--v3-bar-pct:100%">&lt;/span>&lt;/span>&lt;span class="v3-price-delta__val">&amp;#43;150.2%&lt;/span>&lt;/span>&lt;/td>&lt;/tr>&lt;/tbody>&lt;/table>
&lt;/div>&lt;details class="price-capture-evidence">&lt;summary>See coverage, gaps and source files&lt;/summary>
&lt;p>&lt;a href="https://techfuelhq.com/data/gpu-price-observations.csv" download>Download all 122 offer rows (CSV)&lt;/a>. They span 15 distinct UTC dates, from 2026-09-14 through 2026-11-17. A missing date means there is no published offer row for that date. The recorded method on 2026-11-17 was &lt;code>gpu-street-price-newegg-affiliate-feed-v1&lt;/code>.&lt;/p>&lt;p>&lt;a href="https://techfuelhq.com/data/gpu-price-index.csv" download>Download the 15 recorded index rows (CSV)&lt;/a>. Each median uses the models that qualified on that date. Different membership or a new method can move a median even when no individual listing changed price.&lt;/p>&lt;div class="table-wrap" tabindex="0" role="region" aria-labelledby="price-reader-gpu-0-series">&lt;table>&lt;caption id="price-reader-gpu-0-series">Published index rows, with their original methods&lt;/caption>&lt;thead>&lt;tr>&lt;th scope="col">UTC date&lt;/th>&lt;th scope="col">Models qualified / queried&lt;/th>&lt;th scope="col">Median premium vs. launch&lt;/th>&lt;th scope="col">Recorded method&lt;/th>&lt;/tr>&lt;/thead>&lt;tbody>&lt;tr>&lt;th scope="row">2026-09-14&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;53.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-discovery-v1&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-09-26&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;53.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-09-28&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;53.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-09-29&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;53.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-09-30&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;53.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-01&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;53.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-02&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-03&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-05&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-06&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-07&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-08&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;51.9%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-10&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-10-11&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;57.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-direct-v2&lt;/code>&lt;/td>&lt;/tr>&lt;tr>&lt;th scope="row">2026-11-17&lt;/th>&lt;td>7 / 8&lt;/td>&lt;td>&amp;#43;86.5%&lt;/td>&lt;td>&lt;code>gpu-street-price-newegg-affiliate-feed-v1&lt;/code>&lt;/td>&lt;/tr>
&lt;/tbody>&lt;/table>&lt;/div>
&lt;/details>&lt;/div>
&lt;h2 id="latest-capture">Latest capture&lt;/h2>
&lt;p>&lt;strong>Collection status:&lt;/strong> Captures from November 17, 2026 read that day&amp;rsquo;s Newegg affiliate catalogue file. Captures from September 26 through October 11, 2026 read Newegg&amp;rsquo;s product pages. No capture ran between those two periods, and the method differs across the gap. The block below names the latest capture; check Newegg for current price and stock.&lt;/p>
&lt;!-- auto:capture -->
&lt;p>&lt;strong>Latest capture, November 17, 2026 (UTC), method &lt;code>gpu-street-price-newegg-affiliate-feed-v1&lt;/code>:&lt;/strong> Newegg&amp;rsquo;s affiliate catalogue file for that date had 87 listings naming a tracked model; 28 passed every rule, and 7 of 8 tracked cards have a price. The index metric activates at 6, so the gate is open and an index row was written for this date. Every row carries &lt;code>verification_status: retailer_feed&lt;/code>: the price, title, part number and in-stock flag are the catalogue&amp;rsquo;s own. The catalogue names no seller and no condition, and nothing was checked against the product page.&lt;/p>
&lt;p>Cheapest qualifying listing: &lt;strong>$789.99&lt;/strong> (AMD Radeon RX 9060 XT 16GB, +126.4% vs MSRP).&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Line&lt;/th>
&lt;th scope="col" style="text-align: right">Cheapest qualifying listing&lt;/th>
&lt;th scope="col" style="text-align: right">vs MSRP&lt;/th>
&lt;th scope="col">Newegg item number&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Line">AMD Radeon RX 9060 XT 16GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$789.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+126.4%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814126817&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">NVIDIA GeForce RTX 5060 Ti 16GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$799.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+86.5%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814133993&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">NVIDIA GeForce RTX 5070 12GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$919.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+67.6%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814137940&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">AMD Radeon RX 9070 XT 16GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$999.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+66.9%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814930136&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">AMD Radeon RX 9070 16GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$1,019.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+85.8%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814126748&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">NVIDIA GeForce RTX 5070 Ti 16GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$1,409.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+88.2%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814137935&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">NVIDIA GeForce RTX 5080 16GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">$2,499.99&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">+150.2%&lt;/td>
&lt;td data-label="Newegg item number">N82E16814133898&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Line">NVIDIA GeForce RTX 5090 32GB&lt;/td>
&lt;td style="text-align: right" data-label="Cheapest qualifying listing">none: its listings are priced outside the accepted band&lt;/td>
&lt;td style="text-align: right" data-label="vs MSRP">-&lt;/td>
&lt;td data-label="Newegg item number">-&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>This block is rewritten with every capture; the dated commentary below it is not.&lt;/p>
&lt;!-- /auto:capture -->
&lt;h2 id="recent-qualifying-observations">Recent qualifying observations&lt;/h2>
&lt;p>The file below accumulates one row per qualifying offer for each capture
date. The table below shows the two latest capture dates so current rows are
easy to find. Download the complete CSV history below it for all earlier rows.
Both views use the same raw file at build time.&lt;/p>
&lt;p>&lt;strong>Correction, September 15, 2026.&lt;/strong> The first version of this table counted
eight September 14 listings as new, standalone cards. Five were recertified
PNY cards at Newegg. One was Gigabyte&amp;rsquo;s AORUS AI BOX, an external GPU
enclosure. Two sold a card with another product: a Best Buy package that
included a Samsung SSD, and a Newegg listing that included an ASRock power
supply. I removed those eight rows, fixed the two rules that let them in, and
re-ran the corrected rules over the stored September 14 search response. No
new prices were collected. Three cheapest offers changed. The RTX 5060 Ti
moved from $739.99 to $799.99, the RTX 5070 from $800.99 to $869.99 (now at
Best Buy), and the RTX 5070 Ti from $1,119.99 to $1,149.99. The day&amp;rsquo;s median
premium to MSRP moved from +48.1% to +53.5%.&lt;/p>
&lt;div class="table-wrap csv-table">
&lt;table aria-describedby="csv-table-note-1">
&lt;caption>Recent observations from the latest 2 capture dates, oldest to newest&lt;/caption>
&lt;thead>
&lt;tr>&lt;th scope="col">Capture Date UTC&lt;/th>&lt;th scope="col">Product Label&lt;/th>&lt;th scope="col">Vram GB&lt;/th>&lt;th scope="col">Msrp USD&lt;/th>&lt;th scope="col">Title&lt;/th>&lt;th scope="col">Seller&lt;/th>&lt;th scope="col">Price USD&lt;/th>&lt;th scope="col">Premium Pct&lt;/th>&lt;th scope="col">Verification Status&lt;/th>&lt;/tr>
&lt;/thead>
&lt;tbody>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>NVIDIA GeForce RTX 5080 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>999.0&lt;/td>&lt;td>ASUS PRIME GeForce RTX 5080 16GB 256-Bit GDDR7 PCI-Express 5.0 DLSS 4.0 Graphics Card PRIME-RTX5080-16G&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>1599.99&lt;/td>&lt;td>60.2&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>NVIDIA GeForce RTX 5070 Ti 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>749.0&lt;/td>&lt;td>MSI FRIEREN EDITION GeForce RTX 5070 Ti Video Card RTX 5070 Ti 16G FRIEREN EDITION OC&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>1179.99&lt;/td>&lt;td>57.5&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>NVIDIA GeForce RTX 5070 12GB&lt;/td>&lt;td>12&lt;/td>&lt;td>549.0&lt;/td>&lt;td>ASUS PRIME GeForce RTX 5070 12GB 192-Bit GDDR7 PCI Express 5.0 DLSS 4.0 Graphics Card PRIME-RTX5070-12G&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>869.99&lt;/td>&lt;td>58.5&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>NVIDIA GeForce RTX 5060 Ti 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>429.0&lt;/td>&lt;td>MSI Ventus GeForce RTX 5060 Ti Graphics Card RTX 5060 Ti 16G VENTUS 3X OC&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>799.99&lt;/td>&lt;td>86.5&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>AMD Radeon RX 9070 XT 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>599.0&lt;/td>&lt;td>ASUS PRIME Radeon RX 9070 XT 16GB 256-Bit GDDR6 PCI Express 5.0 RDNA 4 Graphics Card PRIME-RX9070XT-O16G&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>829.0&lt;/td>&lt;td>38.4&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>AMD Radeon RX 9070 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>549.0&lt;/td>&lt;td>ASRock Challenger Radeon RX 9070 Graphics Card RX9070 CL 16G&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>699.99&lt;/td>&lt;td>27.5&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-10-11&lt;/td>&lt;td>AMD Radeon RX 9060 XT 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>349.0&lt;/td>&lt;td>ASUS Dual Radeon RX 9060 XT Graphics Card DUAL-RX9060XT-16G&lt;/td>&lt;td>Newegg&lt;/td>&lt;td>529.99&lt;/td>&lt;td>51.9&lt;/td>&lt;td>discovery_only&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>NVIDIA GeForce RTX 5080 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>999.0&lt;/td>&lt;td>PNY ARGB OC GeForce RTX 5080 16GB 256-Bit GDDR7 DLSS 4.0 PCI Express 5.0 x16 Graphics Card VCG508016TFXXPB1-O&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>2499.99&lt;/td>&lt;td>150.2&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>NVIDIA GeForce RTX 5070 Ti 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>749.0&lt;/td>&lt;td>MSI SHADOW GeForce RTX 5070 Ti Graphics Card RTX 5070 TI 16G SHADOW 3X OC&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>1409.99&lt;/td>&lt;td>88.2&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>NVIDIA GeForce RTX 5070 12GB&lt;/td>&lt;td>12&lt;/td>&lt;td>549.0&lt;/td>&lt;td>MSI Ventus GeForce RTX 5070 Graphics Card RTX 5070 12G VENTUS 3X OC&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>919.99&lt;/td>&lt;td>67.6&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>NVIDIA GeForce RTX 5060 Ti 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>429.0&lt;/td>&lt;td>PNY DUAL FAN OC GeForce RTX 5060 Ti 16GB 128-Bit GDDR7 PCI Express 5.0 x8 DLSS 4.0 Graphics Card RTX 5060 Ti 16GB DUAL FAN OC VCG5060T16DFXPB1-O&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>799.99&lt;/td>&lt;td>86.5&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>AMD Radeon RX 9070 XT 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>599.0&lt;/td>&lt;td>ASRock Steel Legend Radeon RX 9070 XT Graphics Card RX9070XT SL 16G&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>999.99&lt;/td>&lt;td>66.9&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>AMD Radeon RX 9070 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>549.0&lt;/td>&lt;td>ASUS PRIME Radeon RX 907016GB 256-Bit GDDR6 PCI Express 5.0 RDNA 4 Graphics Card PRIME-RX9070-O16G&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>1019.99&lt;/td>&lt;td>85.8&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>&lt;tr>&lt;td>2026-11-17&lt;/td>&lt;td>AMD Radeon RX 9060 XT 16GB&lt;/td>&lt;td>16&lt;/td>&lt;td>349.0&lt;/td>&lt;td>ASUS Dual Radeon RX 9060 XT Graphics Card DUAL-RX9060XT-16G&lt;/td>&lt;td>Newegg listing (seller not stated)&lt;/td>&lt;td>789.99&lt;/td>&lt;td>126.4&lt;/td>&lt;td>retailer_feed&lt;/td>&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p class="csv-table__note" id="csv-table-note-1">Showing 14 of 122 observations from the latest 2 capture dates. &lt;a href="https://techfuelhq.com/data/gpu-price-observations.csv" download>Download the complete CSV history&lt;/a>. The table is rendered from that file at build time.&lt;/p>
&lt;h2 id="method-exactly">Method, exactly&lt;/h2>
&lt;p>&lt;strong>The method changed on November 17, 2026.&lt;/strong> Rows dated from that day come
from Newegg&amp;rsquo;s affiliate product catalogue, the daily file Newegg publishes to
its affiliates through Rakuten Advertising. I read that day&amp;rsquo;s file and, for
each tracked card, keep the cheapest listing that passes every rule:&lt;/p>
&lt;ul>
&lt;li>it sits in the catalogue&amp;rsquo;s graphics-card category;&lt;/li>
&lt;li>its title, brand and manufacturer part number match exactly one tracked
card and state that card&amp;rsquo;s VRAM;&lt;/li>
&lt;li>the catalogue marks it in stock;&lt;/li>
&lt;li>the title names no used, refurbished, recertified, renewed or open-box
condition, and no bundle, combo or multi-pack;&lt;/li>
&lt;li>it carries one of Newegg&amp;rsquo;s own item numbers, the form &lt;code>N82E168&lt;/code> plus eight
digits;&lt;/li>
&lt;li>the price sits between 0.5x and 3.0x the card&amp;rsquo;s MSRP.&lt;/li>
&lt;/ul>
&lt;p>The price is the catalogue&amp;rsquo;s sale price when the listing has one and its
regular price otherwise. No product page is opened.&lt;/p>
&lt;p>The catalogue gives a title, an item number, a part number, a brand, prices,
a shipping amount and one availability word. It names no seller and no
condition. So these rows are not labeled sold by Newegg, and their condition
rests on the title alone. The item-number rule is the nearest thing to a
seller check. Listings numbered &lt;code>9SI&lt;/code> point at the same product page with a
different item, their own price and often a shipping charge, and I leave them
out. I tested that rule on the catalogue file from September 29: the listings
it accepts matched, to the cent, every price my page captures recorded that
day as sold by Newegg, 24 of 24 across the GPU, SSD and RAM trackers. Shipping
is recorded with the capture and not added to the price. New rows carry
&lt;code>verification_status: retailer_feed&lt;/code> and hold one row per card.&lt;/p>
&lt;p>A change between October 11 and November 17 is not automatically a
like-for-like price move. The two dates are 37 days apart and use different
methods, and the cheapest qualifying listing for a card can be a different
board on each date. Compare the listing titles before comparing the prices.&lt;/p>
&lt;p>From September 26 through October 11, 2026 the method queried each tracked
card on Newegg and confirmed the selected sold-by-Newegg item on its pinned
product page. The row came from &lt;code>ItemDetail&lt;/code>: &lt;code>FinalPrice&lt;/code> less a real
shipping charge, seller, stock, new/refurbished/open-box flags and fetch
time. Marketplace, used, refurbished, open-box, out-of-stock, wrong-model,
non-card and out-of-band rows were rejected. Newegg&amp;rsquo;s storefront refused
those requests after October 11, and I retired that collector instead of
working around the refusal.&lt;/p>
&lt;p>The archived captures used Google Shopping (US, English) via DataForSEO&amp;rsquo;s
merchant API. That collection route is retired. The historical method used one
exact-model query per tracked card. Under that historical method, an offer
qualified only if the
seller matches a named direct-retailer allowlist (Best Buy, Newegg, B&amp;amp;H,
Micro Center, Adorama, Walmart first-party, and peers — marketplace suffixes
excluded), the title names the exact model and states its VRAM, the listing
is a single discrete card rather than a laptop, prebuilt, external enclosure,
bundle, or multi-product package, condition is new (not used, refurbished,
recertified, or open-box), and the USD price sits between 0.5x and 3.0x the
card&amp;rsquo;s MSRP. Each accepted row records its premium or discount to MSRP to one
decimal.&lt;/p>
&lt;p>The tracked cards: RTX 5090, 5080, 5070 Ti, 5070 and 5060 Ti 16GB, and RX
9070 XT, 9070 and 9060 XT 16GB. Their MSRPs were verified against NVIDIA and
AMD press releases on 2026-09-05; the verbatim passages are in the basket
file in the site&amp;rsquo;s repository, alongside the collector, its tests, and every
capture&amp;rsquo;s raw response.&lt;/p>
&lt;p>The index metric (median cheapest premium across cards) activates at six of
eight qualifying cards on the same day. Below that, the observations still
publish; the index row does not.&lt;/p>
&lt;h2 id="what-this-price-index-does-not-cover">What this price index does not cover&lt;/h2>
&lt;p>This basket answers dated price and MSRP questions for eight new,
current-generation cards. It does not price used cards, older RTX 3070 or RTX
3080 stock, or today&amp;rsquo;s deals outside the recorded capture. Use the &lt;a href="https://techfuelhq.com/articles/gpu-hierarchy-2026/">GPU
hierarchy&lt;/a> for performance ranks and Intel&amp;rsquo;s
place in the field, and the &lt;a href="https://techfuelhq.com/articles/best-gpu-plex-jellyfin-transcode-2026/">Plex and Jellyfin GPU
guide&lt;/a> for hardware-
acceleration support. Those are different questions from street price.&lt;/p>
&lt;h2 id="use-the-data-cc-by-40">Use the data (CC BY 4.0)&lt;/h2>
&lt;p>Download every observation:
&lt;a href="https://techfuelhq.com/data/gpu-price-observations.csv" download type="text/csv">gpu-price-observations.csv&lt;/a> — one row per
qualifying offer with capture date, card, MSRP, street price, premium,
seller and verification status. Rows dated from November 17, 2026 read
&lt;code>Newegg listing (seller not stated)&lt;/code> in the seller column and &lt;code>retailer_feed&lt;/code>
as their status. When at least six of eight cards qualify,
that day&amp;rsquo;s row is added to &lt;a href="https://techfuelhq.com/data/gpu-price-index.csv" download type="text/csv">gpu-price-index.csv&lt;/a>. License:
&lt;a href="https://creativecommons.org/licenses/by/4.0/" rel="noopener">Creative Commons Attribution 4.0&lt;/a>
— attribute as &amp;ldquo;TechFuelHQ GPU Price Index&amp;rdquo; linking to this page.&lt;/p>
&lt;p>Choosing between these cards? The &lt;a href="https://techfuelhq.com/tools/gpu-comparison/">GPU comparison tool&lt;/a>
holds the specs, and the &lt;a href="https://techfuelhq.com/gpu-reviews/">GPU reviews&lt;/a> hold the measured
results. The sibling &lt;a href="https://techfuelhq.com/data/ram-price-index/">DDR5 RAM price index&lt;/a> uses the
same collector and the same gate.&lt;/p>
&lt;h2 id="weekly-market-context">Outside reference: US prices from Pricify&lt;/h2>
&lt;section aria-labelledby="weekly-market-context" data-external-market-context="gpu">
&lt;p>For the week ending &lt;time datetime="2026-11-08">2026-11-08&lt;/time> (US Eastern), &lt;a href="https://pricify.ai/">Pricify&lt;/a> published week-end prices in US dollars. We checked one exact part number in its 98-product sample.&lt;/p>
&lt;div class="table-wrap" role="region" aria-label="Pricify historical item prices" tabindex="0">
&lt;table>
&lt;caption>Selected exact parts in the 2026-W45 release&lt;/caption>
&lt;thead>&lt;tr>&lt;th scope="col">Part / manufacturer number&lt;/th>&lt;th scope="col">Week-end item low&lt;/th>&lt;th scope="col">Venue in the source&lt;/th>&lt;/tr>&lt;/thead>
&lt;tbody>&lt;tr>
&lt;th scope="row">Reaper Radeon RX 9070 XT 16 GB&lt;br>&lt;small>RX9070XT 16G-A&lt;/small>&lt;/th>
&lt;td>$919.99&lt;/td>&lt;td>Micro Center (in store)&lt;/td>
&lt;/tr>&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>These are the publisher’s historical item prices for new products sold by the retailer. Physical stores can count, the source does not give a delivered total with shipping and tax, and a prior reading may carry forward for about three days. A missing part is not evidence that it sold out. These rows do not update TechFuelHQ’s own observations or establish a price you can buy at today.&lt;/p>
&lt;p>Selected and reformatted from &lt;a href="https://raw.githubusercontent.com/pricify-ai/pc-hardware-prices/9507089fec375be2f86d309c8ff37a6190043947/data/2026/W45/json/vga.live.json">Pricify’s original weekly JSON&lt;/a>, &lt;a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0&lt;/a>. Retrieved &lt;time datetime="2026-11-13T23:24:17Z">2026-11-13 UTC&lt;/time>.
&lt;a href="https://techfuelhq.com/data/weekly-market-context/2026-W45-9507089fec375be2f86d309c8ff37a6190043947.csv" download>Download the selected weekly rows (CSV)&lt;/a> ·
&lt;a href="https://techfuelhq.com/data/weekly-market-context/2026-W45-9507089fec375be2f86d309c8ff37a6190043947.json" download>Identifiers, source hashes and dates (JSON)&lt;/a> ·
&lt;a href="https://raw.githubusercontent.com/pricify-ai/pc-hardware-prices/9507089fec375be2f86d309c8ff37a6190043947/METHODOLOGY.md">Publisher’s method&lt;/a>.&lt;/p>
&lt;/section>
&lt;h2 id="change-log">Change log&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>0.10.0 (2026-11-17)&lt;/strong> — source and method change, and the first capture
since October 11. Rows from this date come from Newegg&amp;rsquo;s affiliate product
catalogue under method &lt;code>gpu-street-price-newegg-affiliate-feed-v1&lt;/code>, with
&lt;code>verification_status: retailer_feed&lt;/code>. The catalogue names no seller, so
these rows do not repeat the sold-by-Newegg statement of the September 26
to October 11 captures; they require one of Newegg&amp;rsquo;s own item numbers
instead. First capture under the new method: 7 of 8 cards have a price and
the index row reads a median premium of +86.5% and a median cheapest price
of $999.99. The October 11 row, under the page method, read +57.5% and
$829.00. The RTX 5090 has no row because every catalogue listing sits above
the 3.0x MSRP ceiling. No earlier row was changed.&lt;/li>
&lt;li>&lt;strong>0.9.1 (2026-09-15)&lt;/strong> — correction to the September 14 capture, with no
new capture taken. Eight rows that break the rules on this page were removed
from &lt;code>gpu-price-observations.csv&lt;/code>. Five were &amp;ldquo;Recertified - PNY&amp;rdquo; cards at
Newegg (RTX 5060 Ti $739.99, RTX 5070 $800.99, RTX 5070 Ti $1,119.99, and
two RTX 5080 listings at $1,599.99). The other three were the Gigabyte RTX
5060 Ti AORUS AI BOX external enclosure ($899.99, Newegg), a Best Buy
package pairing an ASUS RTX 5070 with a Samsung 990 EVO Plus SSD
($1,289.98), and a Newegg listing pairing a ZOTAC RTX 5070 Ti with an ASRock
750W power supply ($1,374.98). The collector&amp;rsquo;s condition rule did not
recognize &amp;ldquo;recertified&amp;rdquo;, and its card rule did not recognize &amp;ldquo;External
Graphics&amp;rdquo;, Best Buy&amp;rsquo;s &amp;ldquo;Package&amp;rdquo; listings, or a power supply in the title. I
fixed both rules, added regression tests built from these listings, and
re-ran the rules over the stored response. Eligible offers for the day fall
from 32 to 24, and 7 of 8 cards still qualify. The 2026-09-14 row in
&lt;code>gpu-price-index.csv&lt;/code> is restated in place. Its median premium moves from
+48.1% to +53.5% and its median cheapest price from $800.99 to $869.99; the
minimum and maximum are unchanged. The method name stays
&lt;code>gpu-street-price-discovery-v1&lt;/code> because this page already excluded these
listings and the collector had not enforced that. Until this entry, the FAQ
answer saying refurbished listings are rejected was false for that capture.&lt;/li>
&lt;li>&lt;strong>0.9.0 (2026-09-14)&lt;/strong> — pilot publication and first live capture. The
collector and its tests predate this page (2026-09-05); the page ships the
day the daily runner first exercised them against the live API.&lt;/li>
&lt;/ul></description></item><item><title>How to Enable XMP or EXPO and Prove It's Stable (2026)</title><link>https://techfuelhq.com/tutorials/how-to-enable-xmp-expo-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/how-to-enable-xmp-expo-2026/</guid><atom:updated>2026-11-17T15:00:07Z</atom:updated><description>&lt;p>You paid for 6000 MT/s and your machine is running at 4800. Nothing is broken. The kit is sitting on its JEDEC default speed, which is the safe configuration every board can boot, and the rated number on the box is an overclock profile the module vendor validated and stored in the DIMM&amp;rsquo;s SPD chip. Corsair publishes both numbers side by side for its Vengeance 6000 CL30 kit: 4800MHz at CL40 and 1.1V by default, 6000 MT/s at CL30 and 1.40V on the tested profile. G.Skill lists the same split.&lt;/p>
&lt;p>Turning the profile on takes about ninety seconds in UEFI. Proving the machine is actually stable at that speed takes longer, and it is the half of the job most people skip. Here is the full sequence, including what to do when the board refuses to boot.&lt;/p>
&lt;h2 id="1-why-your-ddr5-kit-boots-at-jedec-speed">1. Why your DDR5 kit boots at JEDEC speed&lt;/h2>
&lt;p>A DDR5 module carries two sets of numbers. The SPD default is what the memory presents to any board with no configuration: a conservative speed, loose timings and 1.1V. The overclock profile is what the vendor tested and certified, and both Intel XMP and AMD EXPO are just standardized containers for it. ASUS describes the job plainly on its support page: the board loads the preset overclock file and DRAM timing from the memory SPD chip.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Specification&lt;/th>
&lt;th scope="col">Corsair Vengeance CMK32GX5M2B6000Z30&lt;/th>
&lt;th scope="col">G.Skill Flare X5 F5-6000J3038F16GX2-FX5&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Specification">Default (SPD) speed&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">4800MHz&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">4800 MT/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Default SPD latency&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">CL40&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">not published as a CL value&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Default SPD voltage&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">1.1V&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">1.10V&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Tested profile speed&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">6000 MT/s&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">6000 MT/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Tested profile timings&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">CL30&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">30-38-38-96&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Tested profile voltage&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">1.40V&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">1.35V&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Profile standard&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">AMD EXPO and Intel XMP&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">Intel XMP 3.0 and AMD EXPO&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Those two kits are not slow hardware. They are hardware waiting for a setting. AMD&amp;rsquo;s EXPO page describes the profiles as a way to get easy DDR5 overclocking on socket AM5 with Ryzen-optimized settings, which is the same bargain Intel&amp;rsquo;s XMP makes on its platforms: one menu choice instead of hand-entering timings.&lt;/p>
&lt;p>One caution belongs up front, because AMD is explicit about it. AMD&amp;rsquo;s own footnotes state that overclocking processors and memory outside AMD&amp;rsquo;s published specifications, including altering memory timing or voltage, will void any applicable AMD product warranty, even when it is enabled through AMD hardware or software. Enabling EXPO is that kind of change. If the machine has to stay inside a support contract, that is a decision to make deliberately.&lt;/p>
&lt;h2 id="2-step-1-confirm-the-rated-profile-and-the-slot-pair">2. Step 1: Confirm the rated profile and the slot pair&lt;/h2>
&lt;p>Before you open UEFI, establish three facts.&lt;/p>
&lt;p>&lt;strong>The exact kit.&lt;/strong> Read the part number from the module label or from the memory details in Windows, then look it up on the vendor&amp;rsquo;s own specification page. You want the tested speed, the tested primary timings and the tested voltage. If the page lists only an Intel XMP 3.0 profile and your board is AM5, the board may still accept it as DOCP, but you are now outside the kit&amp;rsquo;s documented path.&lt;/p>
&lt;p>&lt;strong>Whether the pair is a matched kit.&lt;/strong> G.Skill&amp;rsquo;s specification page for the Flare X5 states it directly: do not mix memory kits, because kits are sold as matched sets designed to run together. Two separately purchased pairs are not the same thing as one four-module kit, even when the part numbers match.&lt;/p>
&lt;p>&lt;strong>The slot pair.&lt;/strong> ASUS&amp;rsquo;s failure checklist starts with using modules from its qualified vendors list, keeping a kit together rather than mixing modules, and testing a single module in the recommended slot. That is the practical version of the rule: two DIMMs in the pair your manual calls out, not two in whichever slots were easiest to reach. The &lt;a href="https://techfuelhq.com/articles/ddr5-ram-buying-guide-2025/">DDR5 buying guide&lt;/a> covers why pairs behave this way, and the live &lt;a href="https://techfuelhq.com/data/ram-price-index/">RAM price index&lt;/a> is the place to check kit pricing before buying a second pair you do not need.&lt;/p>
&lt;p>AMD also publishes a tested-memory list that flags each kit as EXPO-certified, certified with Ultra Low Latency, or merely XMP-compatible. Worth checking when a profile keeps failing.&lt;/p>
&lt;h2 id="3-step-2-load-xmp-or-expo-in-uefi">3. Step 2: Load XMP or EXPO in UEFI&lt;/h2>
&lt;p>The menu sequence below is ASUS&amp;rsquo;s documented path, because that is the vendor documentation I can point you at line by line. On MSI, Gigabyte and ASRock boards the same toggle lives in that vendor&amp;rsquo;s overclocking or tweaker section under its own label, so follow your board manual rather than assuming the ASUS wording appears on your screen.&lt;/p>
&lt;ol>
&lt;li>Restart the machine and tap &lt;code>Del&lt;/code> or &lt;code>F2&lt;/code> during POST to enter BIOS setup. Most boards land in an EZ Mode summary screen.&lt;/li>
&lt;li>Press &lt;code>F7&lt;/code> to switch to Advanced Mode. If the board boots straight into Advanced Mode, skip this.&lt;/li>
&lt;li>Open the &lt;strong>Ai Tweaker&lt;/strong> page. Some boards label this tab &lt;strong>Extreme Tweaker&lt;/strong>.&lt;/li>
&lt;li>Select &lt;strong>Ai Overclock Tuner&lt;/strong>. On an Intel board with an XMP kit, ASUS&amp;rsquo;s walkthrough has you choose &lt;strong>XMP I&lt;/strong>. On an AMD AM5 board with an EXPO kit, it has you choose &lt;strong>EXPO I&lt;/strong>. On an AMD board with an XMP kit, ASUS uses &lt;strong>DOCP&lt;/strong> to apply the XMP timings.&lt;/li>
&lt;li>Press &lt;code>F10&lt;/code> and confirm to save and exit. The board reboots on its own.&lt;/li>
&lt;/ol>
&lt;p>Two checks are worth making before you leave UEFI. The EZ Mode memory information panel shows the DRAM frequency the board intends to run, and &lt;strong>Tool → SPD Information&lt;/strong> shows whether the installed module reports an XMP profile or an EXPO profile at all. A kit with no visible profile is a kit that will not accept one.&lt;/p>
&lt;p>What changes after the reboot: the board retrains memory against the new timings. That first POST after enabling a profile routinely takes longer than a normal boot, sometimes with a dark screen or a pause on the memory LED, and cutting power during that window is how people turn a two-minute setting into a CMOS clear. Let it finish. Once Windows loads, open Task Manager, go to &lt;strong>Performance → Memory&lt;/strong>, and read the &lt;strong>Speed&lt;/strong> figure. ASUS documents exactly this check. If it says 6000 MT/s, the profile is live; if it still says 4800, the profile did not take, and the next section is for you.&lt;/p>
&lt;h2 id="4-step-3-recover-a-failed-boot-without-guessing">4. Step 3: Recover a failed boot without guessing&lt;/h2>
&lt;p>A board that cannot train the profile generally does not sit there blinking at you forever; most fall back to defaults and boot. Do not read a successful desktop as proof the profile applied. Check the speed.&lt;/p>
&lt;p>If the machine genuinely will not come back, clear CMOS. ASUS documents three methods on its boards, and many other boards offer similar ones:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Method&lt;/th>
&lt;th scope="col">What you do&lt;/th>
&lt;th scope="col">Notes&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Method">Clear CMOS button&lt;/td>
&lt;td data-label="What you do">Power off, unplug the cord, hold the button about 5-10 seconds&lt;/td>
&lt;td data-label="Notes">Present on many mid-range and high-end boards&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Method">CLRTC pins&lt;/td>
&lt;td data-label="What you do">Power off, unplug, short the two pins about 5-10 seconds with a jumper cap (ASUS also lists a metal object)&lt;/td>
&lt;td data-label="Notes">Most common on boards without a button&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Method">CMOS battery&lt;/td>
&lt;td data-label="What you do">Power off, unplug, remove the battery, then clear with the pin or button&lt;/td>
&lt;td data-label="Notes">Needed when the other two are inaccessible&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>After restoring power, the board announces that BIOS settings were reset. Press &lt;code>F1&lt;/code> to enter setup, &lt;code>F5&lt;/code> to load optimized defaults, &lt;code>F10&lt;/code> to save and exit. Your fan curves, boot order and memory profile are all gone at that point, so plan to set them again.&lt;/p>
&lt;p>If the board posts but stays at JEDEC speed after you enabled the profile, work the list in order: confirm the two DIMMs are in the recommended pair, pull one module and try again, check whether the profile is one the kit actually carries, and look at the firmware version. An older BIOS with a stale memory-training routine is a real cause of profiles that refuse to train, and our &lt;a href="https://techfuelhq.com/tutorials/how-to-update-bios-2026/">BIOS update walkthrough&lt;/a> covers how to flash one safely. If the machine never reaches the point of training memory at all, the &lt;a href="https://techfuelhq.com/articles/computer-wont-turn-on-2026/">no-power checklist&lt;/a> and the &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">diagnostic workbench&lt;/a> separate a memory problem from a power or board problem.&lt;/p>
&lt;h2 id="5-step-4-prove-the-profile-is-stable">5. Step 4: Prove the profile is stable&lt;/h2>
&lt;p>A machine that boots and games for an hour is not the same as a machine that stores data correctly. HCI Design&amp;rsquo;s MemTest manual is blunt about the consequence: an unstable system gets worse over time as corrupted data is written to the hard disk. That is the failure mode worth spending an afternoon to avoid, because it looks like a filesystem problem or a bad game install long before it looks like memory.&lt;/p>
&lt;p>Two tools do the job, and I use them for different stages.&lt;/p>
&lt;p>&lt;strong>MemTest86, booted from USB, is the check that counts.&lt;/strong> PassMark&amp;rsquo;s technical documentation lists DDR5 SPD reporting, including kits that carry Intel XMP 3.0 or AMD EXPO profiles, plus per-module error tracking and a running count of uncorrected and corrected errors. Because it runs before any operating system, nothing else is occupying the memory it is testing. I start it, leave it overnight, and treat any error as a failed profile. There is no pass count that turns a reported error into an acceptable one.&lt;/p>
&lt;p>&lt;strong>HCI MemTest, run inside Windows, is the faster sanity check.&lt;/strong> Its manual gives concrete numbers: 100 percent coverage is a very thorough test that catches all but the most intermittent problems, running to 400 percent is what catches the rare ones, and 60 percent of bad RAM is detected after just 10 percent coverage. On a multi-core machine it recommends one instance per core with the RAM divided between them. I use it when I want a quick answer before committing to an overnight run.&lt;/p>
&lt;p>Alongside the memory test, check the two places Windows reports what actually happened:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Task Manager → Performance → Memory → Speed&lt;/strong> should show the rated figure, not 4800.&lt;/li>
&lt;li>&lt;strong>Event Viewer → Windows Logs → System&lt;/strong>, scanned for new WHEA entries after a test run. Microsoft describes WHEA as the architecture Windows uses for hardware error reporting and recovery, so a fresh WHEA entry during a stress run is a signal that something in the platform, not just the memory test, objected.&lt;/li>
&lt;/ul>
&lt;p>A profile that passes an overnight bootable run, shows the rated speed in Windows, and logs no new hardware errors is a profile I will leave enabled. A profile that passes only the quick test gets re-run overnight before I trust it.&lt;/p>
&lt;h2 id="6-xmp-and-expo-are-not-manual-tuning">6. XMP and EXPO are not manual tuning&lt;/h2>
&lt;p>The profile is a starting point the module vendor validated, and it changes a defined set of values: the data rate, the primary timings, and the voltage. On the Corsair kit in the table, that is 1.40V against a 1.1V default; on the G.Skill kit, 1.35V against 1.10V. Everything the profile sets, the vendor tested as a combination.&lt;/p>
&lt;p>Manual tuning is a different activity. You set the voltage yourself, you change the primary timings yourself, and you take on the secondary and tertiary timings and the refresh interval as well. That is where enthusiasts find the last few percent, and it is also where a machine that passes a short test can start corrupting files a month later. Motherboard &amp;ldquo;try it&amp;rdquo; presets are not the same thing, because nobody certified them against your specific modules.&lt;/p>
&lt;p>My rule: enable the profile, prove it, and stop there. Manual tuning only makes sense against a specific problem you can measure, and it needs a longer stability proof than the profile does.&lt;/p>
&lt;h2 id="7-when-to-leave-the-profile-at-jedec">7. When to leave the profile at JEDEC&lt;/h2>
&lt;p>Some machines are better off at the default speed, and I would rather say so than pretend every kit should be overclocked.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Four modules or a mixed set.&lt;/strong> Matching the kit matters more than the headline speed. If you need the capacity, buy one larger matched pair instead of adding a second pair.&lt;/li>
&lt;li>&lt;strong>A profile that fails a bootable memory test.&lt;/strong> The gap between 4800 and 6000 is worth less than the files a corrupted write can destroy.&lt;/li>
&lt;li>&lt;strong>A compact build with no airflow over the DIMMs.&lt;/strong> Voltage headroom and module temperature are related, and a sealed small-form-factor case is not the place to discover that.&lt;/li>
&lt;li>&lt;strong>A machine under a support contract.&lt;/strong> AMD&amp;rsquo;s own warranty language treats memory overclocking as outside its published specifications. That decision is yours, not the profile&amp;rsquo;s.&lt;/li>
&lt;/ul>
&lt;p>For everyone else, the sequence is the same: enable the profile, confirm the speed in Task Manager, run the bootable test until it has earned your trust, and check again after every BIOS update, because a flash can put the kit back on its default. If you are still choosing a kit, the &lt;a href="https://techfuelhq.com/articles/ddr5-6000-cl30-explained-2026/">DDR5-6000 CL30 explainer&lt;/a> covers why that speed and timing combination became the AM5 default recommendation, and the &lt;a href="https://techfuelhq.com/tools/pc-builder/">PC Builder&lt;/a> will check the kit against the rest of a parts list.&lt;/p></description></item><item><title>How to Clean a PC Without Damaging It (2026 Guide)</title><link>https://techfuelhq.com/tutorials/how-to-clean-pc-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/how-to-clean-pc-2026/</guid><atom:updated>2026-11-17T15:00:07Z</atom:updated><description>&lt;p>Dust is not cosmetic. It mats the fins, slows the fans that have to push through it, and raises every temperature in the case at once, which is why a machine that ran quiet in January sounds like a leaf blower by July. Cleaning it is a short job with a fixed order and a short list of things you must not do.&lt;/p>
&lt;p>The order matters more than the tools. Filters first, because that is where most of the dust is and because you do not want to blow it deeper into the case. Heatsinks and fans second. The area around the power supply third. Anything involving liquid is a separate, much narrower job.&lt;/p>
&lt;h2 id="step-1-power-off-unplug-and-drain-the-rails">Step 1: Power off, unplug, and drain the rails&lt;/h2>
&lt;p>Corsair&amp;rsquo;s guide is specific here: power the PC down and set the power supply switch to the off position before you start. I go one step further out of habit. After the PSU switch is off, I hold the case power button for a few seconds to drain whatever charge is left, so nothing is live when a fan cable comes loose under my hand.&lt;/p>
&lt;p>Then unplug the machine from the wall, which HP&amp;rsquo;s cleaning guide also lists as a first step. Not because the switch is unreliable, but because a cable you have not touched cannot be knocked back on by someone else in the room.&lt;/p>
&lt;p>Work where dust can land somewhere other than the carpet you sleep on. A garage, a patio, or a well-ventilated room with the machine on a hard surface is fine. The point is that you will be blowing a season&amp;rsquo;s worth of particulate into the air, and you would rather it not settle back into the case you just cleaned.&lt;/p>
&lt;h2 id="step-2-clean-filters-and-mesh-before-anything-inside">Step 2: Clean filters and mesh before anything inside&lt;/h2>
&lt;p>Corsair calls the dust filters the easiest step and the place to start, and it is right for a practical reason: every filter you clear is dust that never reaches a heatsink. Slide them out or pry off the magnetic ones, then clean them with a damp cloth or under running water.&lt;/p>
&lt;p>The one rule that matters is drying them completely before they go back on the case. A damp filter sitting against a metal front panel is a worse idea than a dusty one.&lt;/p>
&lt;p>While the filters are off, look at the intake mesh and the top exhaust mesh if your case has them. They clog the same way and they are the reason a machine can run hot with clean heatsinks. This is also the moment to notice whether the front intake is blocked by a drive cage, a cable bundle, or the desk cabinet the case is pushed into, because no amount of cleaning fixes an intake that has nowhere to draw from.&lt;/p>
&lt;h2 id="step-3-heatsinks-fans-and-the-psu-shroud-area">Step 3: Heatsinks, fans, and the PSU shroud area&lt;/h2>
&lt;p>Open the side panel and work from the top of the case downward, which is what Corsair recommends and what keeps dislodged dust from settling on parts you already cleaned.&lt;/p>
&lt;p>Three techniques carry the whole job:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Hold the fan blades still.&lt;/strong> Corsair&amp;rsquo;s guidance is to hold the fan still while hitting it with compressed air, and HP&amp;rsquo;s guide gives the reason as preventing over-spinning. Use a finger or a plastic tool, never a screwdriver.&lt;/li>
&lt;li>&lt;strong>Use short bursts, and hold the can upright.&lt;/strong> Corsair specifies an upright canister and short bursts. Upright keeps the liquid propellant in the can instead of spotting the PCB, and short bursts keep you from parking a jet of cold propellant on one component.&lt;/li>
&lt;li>&lt;strong>Keep the nozzle back.&lt;/strong> You want moving air, not a pressure washer. Blasting a heatsink at contact distance drives dust into the fin stack and can knock a fan connector or a jumper loose. Back the nozzle off until you can see the dust leaving rather than feel the jet landing.&lt;/li>
&lt;/ol>
&lt;p>Work the CPU cooler fins, then the GPU cooler and its fans, then the case fans, then the nooks around the drive bays. On the motherboard and the RAM, Corsair&amp;rsquo;s caution is worth following exactly: short bursts only, and no brush on those parts, because a brush catches on a capacitor or a latch and takes it with it. For the fan blades themselves, Corsair&amp;rsquo;s fan guide suggests wiping them with a clean microfiber cloth first, then using cotton swabs with a small amount of isopropyl alcohol for the gap between the blades and the inner frame, and finishing with compressed air for the loose dust that is left.&lt;/p>
&lt;p>The power supply gets air, not disassembly. Corsair lists the PSU as something you can clean with compressed air. That means blowing through the fan grille and the vents from outside the unit. Do not open a power supply to clean it; the capacitors hold a charge after the unit is unplugged, and there is nothing inside that user cleaning improves.&lt;/p>
&lt;p>If the machine sits in a case with a PSU shroud, clean the shroud&amp;rsquo;s vents and the floor filter under it. That is where the intakes for the power supply and often the bottom case fans live, and it is the area people forget because it is at floor level and out of sight.&lt;/p>
&lt;h2 id="step-4-isopropyl-alcohol-belongs-on-a-cloth-not-the-board">Step 4: Isopropyl alcohol belongs on a cloth, not the board&lt;/h2>
&lt;p>Isopropyl alcohol has exactly one job in a PC: removing thermal paste from a CPU heat spreader and a cooler cold plate. Corsair&amp;rsquo;s thermal paste instructions say to clean both surfaces with a paper towel lightly moistened with isopropyl alcohol before applying new paste. Damp, not wet. The cloth does the work.&lt;/p>
&lt;p>The concentration is where the guidance stops agreeing with itself. Corsair specifies isopropyl alcohol without naming a percentage, while HP&amp;rsquo;s cleaning guide lists 99 percent isopropyl alcohol in its tools list. So I will not give you a number of my own. Follow the instructions that came with your cooler or your paste, and if they conflict, follow the cooler&amp;rsquo;s, because it is the part with a warranty on the surface you are wiping.&lt;/p>
&lt;p>What alcohol is not for: the motherboard, the GPU board, connectors, fan hubs, or anything you would describe as &amp;ldquo;wiping down.&amp;rdquo; Do not pour it on the board, do not spray it at the board, and do not use it to chase dust into a socket. Alcohol on a cotton swab for a fan&amp;rsquo;s inner frame, as Corsair&amp;rsquo;s fan guide describes, is a different and much smaller operation than wetting down a PCB.&lt;/p>
&lt;h2 id="what-not-to-do-and-why">What not to do, and why&lt;/h2>
&lt;p>Most cleaning damage is not subtle. It is a specific mistake that seemed reasonable at the time.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Do not&lt;/th>
&lt;th scope="col">Why&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Do not">Put a vacuum nozzle on the board&lt;/td>
&lt;td data-label="Why">HP warns that vacuum cleaners can generate static electricity that may damage sensitive components, and a plastic nozzle dragged across components is the wrong combination to introduce into a live-adjacent machine&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Do not">Use water inside the case&lt;/td>
&lt;td data-label="Why">Water is for removable filters, which then have to be fully dry; nothing inside the case is meant to get wet&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Do not">Spray canned air at an angle so it spits&lt;/td>
&lt;td data-label="Why">Holding the can upright and using short bursts is what keeps liquid propellant off the PCB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Do not">Let fans freewheel under air&lt;/td>
&lt;td data-label="Why">Over-spinning, which is why Corsair and HP both say to hold the blades&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Do not">Brush the motherboard and RAM&lt;/td>
&lt;td data-label="Why">Corsair&amp;rsquo;s caution is explicit: short bursts of air only on those parts&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Do not">Repaste because you are already in there&lt;/td>
&lt;td data-label="Why">A remount changes mounting pressure and paste spread; without a temperature baseline you cannot tell whether you improved anything&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Do not">Open the power supply&lt;/td>
&lt;td data-label="Why">Stored charge, no user-serviceable parts, and nothing to gain&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The repaste line is the one I get asked about most. If the cooler is working, a cleaning session should end with the cooler exactly as it was. If temperatures are the reason you opened the case, diagnose that first with the &lt;a href="https://techfuelhq.com/articles/how-to-check-cpu-temp-2026/">CPU temperature check&lt;/a> and the &lt;a href="https://techfuelhq.com/articles/safe-cpu-temp-2026/">safe temperature ranges&lt;/a>, then decide whether the thermal interface is implicated. Cleaning dust out of a cooler and remounting it are two different jobs with two different risk profiles.&lt;/p>
&lt;h2 id="how-often-to-clean-read-the-dust-not-the-calendar">How often to clean: read the dust, not the calendar&lt;/h2>
&lt;p>Corsair&amp;rsquo;s general rule of thumb is every three to six months. It shortens that to two to three months for a dusty area, a home with pets, or indoor smoking, and considers a twice-yearly clean adequate in a relatively dust-free environment.&lt;/p>
&lt;p>I use those numbers as a range and let the machine set the interval. Once a month, look at the front intake filter without opening anything. If it is visibly matted, that machine needs a shorter cycle than the calendar suggests; if it is barely hazy after two months, the six-month end of the range is fine. A machine on a carpeted floor next to a shedding dog and a machine on a hard floor in a closed office are not on the same schedule, and pretending they are is how people either waste an afternoon or cook a GPU.&lt;/p>
&lt;p>Season is a reasonable proxy in most homes. It is a worse proxy than the filter in front of you.&lt;/p>
&lt;h2 id="what-to-check-after-reassembly">What to check after reassembly&lt;/h2>
&lt;p>Before the side panel goes back on:&lt;/p>
&lt;ul>
&lt;li>Every fan header is seated on the header it came off, and no cable is resting where a blade will hit it.&lt;/li>
&lt;li>The filters are dry and fully seated.&lt;/li>
&lt;li>Nothing is resting on the top of the power supply shroud or blocking a front intake.&lt;/li>
&lt;/ul>
&lt;p>Then power on and check the machine, not the panel:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Every fan spins.&lt;/strong> Open the board&amp;rsquo;s hardware monitor screen in UEFI, or watch the fans at first POST. A fan that does not spin after a cleaning is usually a header you missed, and occasionally a cable you strained.&lt;/li>
&lt;li>&lt;strong>Temperatures return to baseline.&lt;/strong> Idle first, then the same load you used before cleaning. A number that is worse than it was before you opened the case is a reason to stop and look, not a reason to close the panel.&lt;/li>
&lt;li>&lt;strong>Nothing new is audible.&lt;/strong> A tick or a scrape is a cable in a blade or a fan that is not seated flat.&lt;/li>
&lt;/ol>
&lt;p>If a fan will not spin at all, work through the &lt;a href="https://techfuelhq.com/articles/cpu-fan-not-spinning-2026/">fan fault check&lt;/a> before replacing it. If temperatures are still high with clean filters and spinning fans, the problem is airflow, mounting, or the cooler itself rather than dust, and the &lt;a href="https://techfuelhq.com/articles/cpu-gpu-thermal-throttling-fix-2026/">thermal throttling walkthrough&lt;/a> and the &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">diagnostic workbench&lt;/a> are the next stops. For a GPU that stays hot after a clean, the &lt;a href="https://techfuelhq.com/articles/gpu-overheating-2026/">GPU overheating guide&lt;/a> covers what the sensors can and cannot tell you before you consider opening the card.&lt;/p></description></item><item><title>ZFS vs Btrfs (2026): Which Should Your NAS Run?</title><link>https://techfuelhq.com/homelab/zfs-vs-btrfs-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/zfs-vs-btrfs-2026/</guid><atom:updated>2026-11-17T15:00:07Z</atom:updated><description>&lt;p>Two filesystems get recommended for the same job, and they are not the same tool. ZFS is a storage stack that happens to ship a filesystem inside it. Btrfs is a filesystem that learned to manage more than one device. On a NAS, a Proxmox datastore, or a backup target, the decision collapses to one question: do you need parity RAID you can trust with data you cannot rebuild?&lt;/p>
&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · ZFS vs Btrfs&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Parity array of three or more drives:&lt;/strong> ZFS RAIDZ. Checksummed, no RAID-5 write hole.&lt;/li>
&lt;li>&lt;strong>Two-drive mirror or single disk:&lt;/strong> Btrfs. Cheap snapshots, subvolumes, and no ARC budget.&lt;/li>
&lt;li>&lt;strong>Proxmox VM datastore:&lt;/strong> mirrors on either filesystem rather than RAIDZ, because IOPS matter more than bandwidth.&lt;/li>
&lt;li>&lt;strong>Small ARM board or 4 GB NAS:&lt;/strong> Btrfs. Proxmox's ZFS rule of thumb is 2 GiB plus 1 GiB per TiB.&lt;/li>
&lt;li>&lt;strong>Never:&lt;/strong> Btrfs RAID5 or RAID6 for data you care about.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;h2 id="what-both-filesystems-actually-guarantee">What both filesystems actually guarantee&lt;/h2>
&lt;p>Both are copy-on-write. New data lands in free space, the checksum is written, and only then does the tree pointer move to the new block. An interrupted write leaves the old tree intact.&lt;/p>
&lt;p>Both checksum. ZFS states plainly that all metadata and data is checksummed, and that it automatically repairs bad data from a good copy when corruption is detected (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/7/zpoolconcepts.7.html" rel="noopener">OpenZFS zpoolconcepts&lt;/a>). Btrfs checksums data and metadata by default and verifies those checksums after reading, using crc32c unless you switch to xxhash, sha256, or blake2 (&lt;a href="https://btrfs.readthedocs.io/en/latest/Checksumming.html" rel="noopener">Btrfs Checksumming&lt;/a>).&lt;/p>
&lt;p>Both snapshot, both scrub, and both have a send stream. The divergence is not in the feature list. It is in how much verification each one performs without being asked, and in which RAID profiles are actually finished.&lt;/p>
&lt;h2 id="where-zfs-wins-raidz-the-write-hole-and-repair-on-read">Where ZFS wins: RAIDZ, the write hole, and repair on read&lt;/h2>
&lt;p>The single most important line in the OpenZFS manual is that raidz does not suffer from the RAID-5/6 write hole, the window after a power loss where data and parity can be left inconsistent (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/7/zpoolconcepts.7.html" rel="noopener">zpoolconcepts&lt;/a>). That is the property that makes parity RAID defensible on a home array at all.&lt;/p>
&lt;p>Capacity follows the usual arithmetic. A mirror of N disks each holding X bytes stores X bytes and survives N-1 failures. A raidz vdev holds roughly (N minus parity) times X, raidz1 has one parity disk, raidz2 has two, raidz3 has three, and the manual recommends keeping a raidz vdev between three and nine disks (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/7/zpoolconcepts.7.html" rel="noopener">zpoolconcepts&lt;/a>). A four-drive raidz1 gives you three drives of usable space. The same four drives as two mirrors give you two, but Proxmox&amp;rsquo;s ZFS wiki says that layout writes like two single disks and reads like four, while a raidz vdev behaves approximately like a single disk for IOPS (&lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">Proxmox ZFS wiki&lt;/a>).&lt;/p>
&lt;p>Expansion used to be the fatal flaw. It is not anymore, as of OpenZFS 2.3.0. &lt;code>zpool attach&lt;/code> can add a device to an existing raidz vdev while maintaining redundancy, and the documentation is explicit that expansion does not change the number of failures a vdev tolerates, so a RAID-Z2 stays a RAID-Z2 afterwards (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/8/zpool-attach.8.html" rel="noopener">zpool-attach&lt;/a>). Two footnotes matter: each expansion uses the 3.5 MiB boot area ZFS reserves near the start of every disk as scratch space, which caps a raidz vdev at 56 disks with ashift=16, and blocks written before the expansion keep their old data-to-parity ratio until they are rewritten (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/8/zpool-attach.8.html" rel="noopener">zpool-attach&lt;/a>). Proxmox documents raidz expansion as available from Proxmox VE 9 on ZFS 2.3.3 (&lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">Proxmox ZFS wiki&lt;/a>).&lt;/p>
&lt;p>Self-healing is the second win, and it is subtler than the marketing suggests. ZFS repairs bad data from a good copy as corruption is detected, not only during a scrub (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/7/zpoolconcepts.7.html" rel="noopener">zpoolconcepts&lt;/a>). The &lt;code>zpool scrub&lt;/code> command exists to force a full sweep of every block (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/8/zpool-scrub.8.html" rel="noopener">zpool-scrub&lt;/a>), but a verified read of a damaged block already triggers repair. That difference shows up years later, when a drive starts returning bad sectors silently.&lt;/p>
&lt;h2 id="where-btrfs-wins-flexible-devices-cheap-snapshots-small-hardware">Where Btrfs wins: flexible devices, cheap snapshots, small hardware&lt;/h2>
&lt;p>Btrfs treats a pool as a set of devices you can add, remove, or replace on demand, and it lets you change the RAID profile of existing data with &lt;code>btrfs balance&lt;/code> rather than rebuilding the filesystem (&lt;a href="https://btrfs.readthedocs.io/en/latest/Volume-management.html" rel="noopener">Volume-management&lt;/a>). If you started with two drives as RAID1 and later want RAID0 for scratch space, you convert in place. ZFS has no equivalent; you plan the vdev layout up front.&lt;/p>
&lt;p>Subvolumes are the other practical advantage. One pool can hold many independently snapshot-able subvolumes, and Proxmox&amp;rsquo;s BTRFS storage type places disk images in subvolumes so it can take snapshots (&lt;a href="https://pve.proxmox.com/wiki/Storage:_BTRFS" rel="noopener">Proxmox BTRFS storage&lt;/a>). Btrfs send and receive carry those subvolumes to another host as full or incremental streams, with each command protected by CRC32C (&lt;a href="https://btrfs.readthedocs.io/en/latest/Send-receive.html" rel="noopener">Send-receive&lt;/a>). ZFS does the same thing with &lt;code>zfs send&lt;/code> (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/8/zfs-send.8.html" rel="noopener">zfs-send&lt;/a>).&lt;/p>
&lt;p>Memory is where Btrfs quietly wins the small-hardware argument. ZFS runs an Adaptive Replacement Cache in RAM, and Proxmox recommends budgeting at least 2 GiB of base memory plus 1 GiB per TiB of stored data, with the ARC enforcing a hard 64 MiB minimum (&lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">Proxmox ZFS wiki&lt;/a>). On a 4 GB ARM NAS or a mini PC you also use as a media server, that budget can be most of the machine once the pool passes a couple of TiB. Btrfs has no ARC and uses the kernel page cache, so there is no cache budget to plan for.&lt;/p>
&lt;h2 id="the-decision-table">The decision table&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Requirement&lt;/th>
&lt;th scope="col">ZFS&lt;/th>
&lt;th scope="col">Btrfs&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Requirement">Parity RAID in production&lt;/td>
&lt;td data-label="ZFS">RAIDZ1/2/3&lt;/td>
&lt;td data-label="Btrfs">RAID5/6 unstable, evaluation only&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">RAID-5/6 write hole&lt;/td>
&lt;td data-label="ZFS">Not present in raidz&lt;/td>
&lt;td data-label="Btrfs">Documented, journal not implemented&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Two-drive mirror with snapshots&lt;/td>
&lt;td data-label="ZFS">Works, needs ARC budget&lt;/td>
&lt;td data-label="Btrfs">Works, minimal overhead&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Single disk with rollback&lt;/td>
&lt;td data-label="ZFS">Possible, heavier&lt;/td>
&lt;td data-label="Btrfs">Native subvolume snapshots&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">VM datastore IOPS&lt;/td>
&lt;td data-label="ZFS">Mirrors only, raidz is one disk of IOPS&lt;/td>
&lt;td data-label="Btrfs">Mirrors only, same logic&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Add a disk to existing parity set&lt;/td>
&lt;td data-label="ZFS">&lt;code>zpool attach&lt;/code>, OpenZFS 2.3+&lt;/td>
&lt;td data-label="Btrfs">Not applicable, no stable parity&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Change RAID profile in place&lt;/td>
&lt;td data-label="ZFS">No, plan the layout first&lt;/td>
&lt;td data-label="Btrfs">&lt;code>btrfs balance&lt;/code> convert&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Metadata checksums&lt;/td>
&lt;td data-label="ZFS">Always&lt;/td>
&lt;td data-label="Btrfs">Default, crc32c unless changed&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Repair on a normal read&lt;/td>
&lt;td data-label="ZFS">Yes, from a good copy&lt;/td>
&lt;td data-label="Btrfs">Verifies, but needs a scrub to find all copies&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Send/receive to remote&lt;/td>
&lt;td data-label="ZFS">&lt;code>zfs send&lt;/code>/&lt;code>zfs receive&lt;/code>&lt;/td>
&lt;td data-label="Btrfs">&lt;code>btrfs send&lt;/code>/&lt;code>btrfs receive&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Memory guidance&lt;/td>
&lt;td data-label="ZFS">2 GiB base + 1 GiB/TiB (Proxmox rule of thumb)&lt;/td>
&lt;td data-label="Btrfs">No dedicated cache&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Per-vdev disk guidance&lt;/td>
&lt;td data-label="ZFS">3-9 disks for raidz&lt;/td>
&lt;td data-label="Btrfs">Profile-dependent&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="recovery-and-the-operational-caveats-that-bite">Recovery and the operational caveats that bite&lt;/h2>
&lt;p>The Btrfs RAID56 warning is not a legacy footnote. The project&amp;rsquo;s own manual says RAID5 and RAID6 should not be used in production, only for evaluation or testing, that power-failure safety for metadata with RAID56 is not complete, and that you should not use raid5 or raid6 for metadata at all, using raid1 or raid1c3 instead (&lt;a href="https://btrfs.readthedocs.io/en/latest/btrfs-man5.html" rel="noopener">btrfs(5)&lt;/a>). The status page still lists RAID56 as unstable (&lt;a href="https://btrfs.readthedocs.io/en/latest/Status.html" rel="noopener">Btrfs Status&lt;/a>). Anyone selling you a four-bay Btrfs NAS on the promise of RAID5 is selling you a test rig.&lt;/p>
&lt;p>Btrfs auto-repair is real but conditional. It salvages data from another valid copy when the profile has redundancy, and the documentation notes that other damaged copies are not detected unless a scrub runs (&lt;a href="https://btrfs.readthedocs.io/en/latest/Auto-repair.html" rel="noopener">Auto-repair&lt;/a>). So your scrub schedule is not optional housekeeping on Btrfs; it is the only mechanism that finds the second bad copy.&lt;/p>
&lt;p>Device replacement has a sharp edge on Btrfs: replace and delete insist on being able to read or reconstruct all data, and the operation aborts if a read fails with an input/output error (&lt;a href="https://btrfs.readthedocs.io/en/latest/Status.html" rel="noopener">Status&lt;/a>). A source disk that is dying slowly can stall the rebuild you started because it was dying. Replace at the first sign of failure rather than waiting for the disk to drop out, and never treat a rebuild as a backup.&lt;/p>
&lt;p>On the ZFS side, the caveats are about planning rather than corruption. A raidz vdev behaves approximately like a single disk for IOPS while providing a lot of bandwidth, and Proxmox is direct that IOPS is the more important metric for running virtual machines (&lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">Proxmox ZFS wiki&lt;/a>). This is why a six-drive RAIDZ2 pool gives you roughly one disk of IOPS for VMs, while a three-mirror pool on the same disks writes like three disks and reads like six. If your workload is databases, virtual machines, or anything with small random reads, mirrors beat parity on both filesystems.&lt;/p>
&lt;p>The OpenZFS FAQ strongly recommends ECC memory where the strongest integrity guarantees are required, and the reason is narrow: without ECC, a random bit flip can go undetected and OpenZFS, like any other filesystem, will write the damaged data to disk. The same FAQ says home users have to weigh that against the cost (&lt;a href="https://openzfs.github.io/openzfs-docs/Project%20and%20Community/FAQ.html" rel="noopener">OpenZFS FAQ&lt;/a>). I cover which failure modes ECC actually prevents in &lt;a href="https://techfuelhq.com/homelab/ecc-home-server-verify-2026/">what breaks without ECC on a home server&lt;/a>, and it is a more honest treatment than the usual blanket warning.&lt;/p>
&lt;h2 id="which-one-should-you-pick">Which one should you pick&lt;/h2>
&lt;p>If you are building a parity array, run ZFS. Three to nine drives in raidz1 or raidz2, checksums on everything, no write hole, and a scrub that actually finds silent corruption. Use the &lt;a href="https://techfuelhq.com/tools/nas-storage-calculator/">NAS storage calculator&lt;/a> to size usable capacity before you buy, because raidz overhead is not intuitive.&lt;/p>
&lt;p>If you are building a two-drive mirror, a single-disk boot volume, or anything on a small ARM board, run Btrfs. You give up nothing that matters at that scale, and you keep your RAM.&lt;/p>
&lt;p>If you are virtualizing, the filesystem is the second decision. The first is mirrors versus parity, and it decides everything downstream. The &lt;a href="https://techfuelhq.com/tools/proxmox-capacity-planner/">Proxmox capacity planner&lt;/a> will tell you how much usable space a given layout leaves you, but the IOPS answer is already settled by the word RAIDZ.&lt;/p>
&lt;p>For the wider stack decision, including whether ZFS should live on the hypervisor at all, read &lt;a href="https://techfuelhq.com/homelab/proxmox-truenas-unraid-storage-backend-2026/">Proxmox vs TrueNAS vs Unraid as a storage backend&lt;/a> and the &lt;a href="https://techfuelhq.com/storage/unraid-vs-truenas-vs-omv-vs-proxmox-2026/">four-way NAS OS comparison&lt;/a>. If you have already committed to a ZFS pool, the &lt;a href="https://techfuelhq.com/tutorials/zfs-proxmox-pool-setup-arc-tuning-2026/">pool setup and ARC tuning walkthrough&lt;/a> covers the commands, and drive selection is covered in &lt;a href="https://techfuelhq.com/homelab/best-nas-hard-drives-2026/">best NAS hard drives&lt;/a>.&lt;/p></description></item></channel></rss>