<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="https://www.jain.com/assets/img/6adafce5-1.1"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MLPerf &#8211; Jain.com</title>
	<atom:link href="/tag/mlperf/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Data centers, connectivity, and security — news and analysis</description>
	<lastBuildDate>Thu, 17 Sep 2026 20:08:55 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>/wp-content/uploads/2026/08/jain-com-icon-512-150x150.png</url>
	<title>MLPerf &#8211; Jain.com</title>
	<link></link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Everyone&#8217;s Watching New AI Silicon. CoreWeave Found 19.8% in Racks It Already Had.</title>
		<link>/coreweave-mlperf-inference-v6-1-results-gb300-nvl72-per-gpu-throughput/</link>
		
		<dc:creator><![CDATA[Deepak Jain]]></dc:creator>
		<pubDate>Wed, 16 Sep 2026 16:00:00 +0000</pubDate>
				<category><![CDATA[AI Infrastructure]]></category>
		<category><![CDATA[AI inference]]></category>
		<category><![CDATA[convertible notes]]></category>
		<category><![CDATA[CoreWeave]]></category>
		<category><![CDATA[GB300 NVL72]]></category>
		<category><![CDATA[GPU economics]]></category>
		<category><![CDATA[MLPerf]]></category>
		<category><![CDATA[NVIDIA Blackwell]]></category>
		<guid isPermaLink="false">/coreweave-mlperf-inference-v6-1-results-gb300-nvl72-per-gpu-throughput/</guid>

					<description><![CDATA[CoreWeave published MLPerf Inference v6.1 results on four NVIDIA Blackwell platforms, including 16,635 tokens per second per GPU on GPT-OSS-120B. The more consequential figure is a 19.8% per-GPU gain booked in five months on hardware already in the field — and a $3.0 billion convertible note filed the next day.]]></description>
										<content:encoded><![CDATA[<div class="jain-post-grid">
<div class="jain-post-main">
<section class="jain-tldr" aria-label="Plain-English summary">
<p class="jain-tldr-kicker">TL;DR · 30-second read</p>
<h2>The Short Version</h2>
<p>CoreWeave rents out computers that run artificial intelligence. On September 16 it published results from an independent industry test and said its machines handled AI requests faster than those of rival rental companies.</p>
<p>The more interesting result is quieter: on machines it installed months ago, it got about 20 percent more work out of each chip purely by improving its own software. No new hardware.</p>
<p>That matters because those chips cost a fortune. Squeezing more out of the ones you own, instead of buying more, is where the profit in this business actually sits.</p>
</section>
<p>CoreWeave on September 16, 2026 published its submissions to MLPerf Inference v6.1, the industry benchmark round released the same day by MLCommons. Writing on the company blog, Shadi Saba said CoreWeave entered the Datacenter Closed division&#8217;s Available category across four NVIDIA platforms — HGX B200, HGX B300, GB200 NVL72 and GB300 NVL72 — and four model families: Qwen3-VL-235B-A22B, DeepSeek-R1-671B, GPT-OSS-120B and Llama 2 70B. Headline figures include 16,635 tokens per second per GPU on GPT-OSS-120B in the offline scenario, more than 1.19 million tokens per second from a single GB300 NVL72 rack, and 944,902 tokens per second on Llama 2 70B in the server scenario. NVIDIA, in a blog post of its own, announced that its next-generation Vera Rubin NVL72 made its MLPerf debut in the same round.</p>
<p>One day later, on September 17, CoreWeave filed an 8-K disclosing a proposed $3.0 billion offering of convertible senior notes due 2033, with an option for a further $500 million, alongside an Equity Distribution Agreement covering at-the-market share sales and collared forward sales through eleven banks. The two disclosures, a day apart, describe the same business from opposite ends: what the fleet produces, and what it costs to keep building.</p>
<h2>Executive Summary</h2>
<p>CoreWeave&#8217;s MLPerf claims break into two categories, and they are not equally interesting. The absolute throughput records — 1,196 queries per second on the multimodal Qwen3-VL model, over 1.16 million tokens per second on GPT-OSS-120B from one rack — are a function of running NVIDIA&#8217;s newest shipping silicon, GB300 NVL72, at scale. Any operator with the same racks and the same power envelope is in that fight.</p>
<p>The second category is harder to replicate. CoreWeave says that comparing its 72-GPU v6.1 submission against its 64-GPU v6.0 submission on GB200 NVL72, derived per-GPU server throughput on DeepSeek-R1-671B rose 19.8% in the five months between rounds. That gain came from serving-stack tuning, scheduling and operations, not from a new chip. If it holds in production, it changes the revenue a depreciating asset can generate across its life — which is the number that underwrites everything else.</p>
<p>That includes the financing. The 8-K filed September 17 shows CoreWeave raising $3.0 billion in converts on top of an existing stack of senior notes carrying coupons from 8.500% to 9.750%. Capital that expensive is serviced by output per installed accelerator, and software gains on hardware already paid for are the cheapest output there is.</p>
<h2>The 19.8% That Didn&#8217;t Require a New Chip</h2>
<p>Strip the benchmark round down and one number does real work. CoreWeave reports that its DeepSeek-R1-671B per-GPU server throughput on NVIDIA GB200 NVL72 rose 19.8% between MLPerf Inference v6.0 and v6.1 — five months apart — through changes to its serving stack, scheduling and operations rather than new hardware. The mechanisms it names are specific: topology-aware scheduling through SUNK, which pins an inference workload inside a single high-bandwidth NVLink domain so that tokens moving between accelerators never leave the fastest interconnect in the rack, and fleet-level health monitoring through Mission Control. For a mixture-of-experts model like DeepSeek-R1 — an architecture that routes each token through a subset of specialised sub-networks, so traffic between chips is constant — placement is not a detail. It is the workload.</p>
<p>Who this affects is everyone financing GPUs on a multi-year schedule. An accelerator bought in early 2026 has a fixed capital cost and a depreciation clock that does not care how efficiently it runs. If per-GPU output rises roughly a fifth without capex, the cost per token served falls by a comparable amount across the remaining life of that asset, and the residual economics of the installed base improve rather than decay. That is a materially different asset story from the one where value arrives only with the next generation of silicon.</p>
<p>The claim deserves its caveats stated plainly, and CoreWeave states some of them itself. Per-GPU throughput is a derived metric — total system throughput divided by accelerator count — and the company notes it is not verified by MLCommons. The comparison also spans two differently sized submissions, 64 accelerators in v6.0 against 72 in v6.1, so scaling behaviour and configuration changes are folded into the same percentage as the software work. The direction is credible and the mechanism is named; the precision of the figure is CoreWeave&#8217;s own arithmetic, not the benchmark&#8217;s finding.</p>
<h2>The Unit of Account Moved From the Chip to the Rack</h2>
<p>The GB300 NVL72 is not a server. It is a rack in which 72 accelerators share one NVLink domain, meaning they address each other at memory-like speeds rather than over conventional networking. CoreWeave&#8217;s results read accordingly: over 1.16 million tokens per second in the server scenario and over 1.19 million offline on GPT-OSS-120B from a single rack, 944,902 and 1,136,100 tokens per second on Llama 2 70B, and 1,196 queries per second on Qwen3-VL-235B-A22B. The company&#8217;s GB200 NVL72 submission reached 901,058 tokens per second on GPT-OSS-120B in the server scenario — the same architecture, one generation back, and a visible step down.</p>
<p>The consequence lands on the people who build and power facilities rather than the people who buy models. When the smallest sensible deployment unit is a rack drawing far more than a legacy hall was designed for, throughput per rack becomes a proxy for how much revenue a given square metre and a given megawatt can carry. Operators comparing a rack-scale NVL72 deployment against clusters of HGX B200 or B300 servers — which CoreWeave also submitted, and which it says led all HGX entries from cloud providers — are really comparing two different power-density and liquid-cooling commitments, not two spec sheets.</p>
<h2>Available Is the Word Doing the Most Work</h2>
<p>CoreWeave&#8217;s submissions sit in the Datacenter Closed division&#8217;s Available category. Closed means every entrant runs the same reference implementation, so results are comparable rather than a contest in custom optimisation; Available means the system can actually be obtained. That second qualifier matters this round, because NVIDIA used the same release to announce that its next-generation Vera Rubin NVL72 made its MLPerf debut. A benchmark headline generated by a platform that is debuting is not a price a buyer can procure against today; CoreWeave&#8217;s four platforms are all Blackwell and Blackwell Ultra, the generations in production now.</p>
<p>For anyone running a procurement process, the practical read is to check three fields before treating any v6.1 result as a quote: which silicon generation produced it, whether the entry sits in the Available category, and whether the metric quoted is a submitted number or a derived per-GPU figure. CoreWeave also stresses that it ran on the same production clusters and images customers get rather than a benchmark-tuned rig — a genuinely meaningful distinction, though one the benchmark itself does not audit.</p>
<h2>Throughput Is the Collateral Story</h2>
<p>The day after the benchmark post, CoreWeave&#8217;s 8-K disclosed a proposed $3.0 billion offering of convertible senior notes due April 1, 2033, sold under Rule 144A to qualified institutional buyers, with an option for up to $500 million more and capped call transactions to limit dilution on conversion. A concurrent Equity Distribution Agreement adds at-the-market share sales and collared forward sales through a syndicate that includes Deutsche Bank, Goldman Sachs, J.P. Morgan, Morgan Stanley and Citigroup. Interest and conversion terms, the release states, are set at pricing.</p>
<p>The comparison worth making is internal. CoreWeave&#8217;s own press release lists the existing obligations the new notes will rank alongside: senior notes at 9.250%, 9.000%, 9.750%, 9.625% and 8.500%, and earlier convertibles at 1.75%. Converts price far below straight debt because the buyer is paid partly in equity optionality rather than cash coupon — cheaper carry now, potential dilution later, which the capped calls are bought to blunt. For a business whose costs are dominated by accelerators, the servicing capacity for any of it comes back to tokens per installed GPU.</p>
<p>That is the honest link between two documents filed a day apart, and it is a structural one rather than a causal one: a benchmark result is a performance claim, not a revenue disclosure, and nothing in the filings ties the offering to the MLPerf round. But the neocloud model runs on both halves at once — demonstrable output per accelerator to justify the capital, and access to capital to buy more accelerators. Software gains of the kind CoreWeave reported on already-deployed GB200 racks are the half that does not require either.</p>
<h2>Background</h2>
<p>CoreWeave, based in Livingston, New Jersey and listed on Nasdaq as CRWV, is a specialist cloud provider built around NVIDIA accelerators for AI training and inference — a category often called a &#8220;neocloud,&#8221; distinguished from general-purpose hyperscalers by its narrow focus and its heavy reliance on debt and equity markets to fund hardware. The company was recently named a Visionary in the Gartner Magic Quadrant for Cloud AI Infrastructure.</p>
<p>MLPerf, administered by the MLCommons consortium, has become the closest thing the industry has to an audited comparison of AI serving performance, which is why vendors submit and why the categories matter. Inference — running a trained model to answer requests — is now the larger and more cost-sensitive half of the AI workload, because a model is trained once but served continuously. That shift is what makes tokens per accelerator, rather than raw chip specifications, the metric operators and their lenders increasingly watch.</p>
<section class="jain-sources" aria-label="Sources">
<h2>Sources</h2>
<p>Source: <a href="https://news.google.com/rss/articles/CBMiyAFBVV95cUxPa0lGcE9vY3V0VFRFUG9lNVRlV3hrOVgzeS1scWJnZU5CZHM2RXlUaTNjaTk0TnQ5TG5PTnlldUdUNDN5YlJzT214U0xFbFlndjMtSFRfSjFzeTJ6cm5POVY0YTQ0eVNSNUh4bE1XdFNrdGtCZ1JscGdyUTIyZHo1ajZxcTdHNGJMVnZiWV9XcVJTYWktVV95SjNkN0ZBYzhWS2xIcW95eWgzcGFPUXlKQk1rYkxweUpnN3I4MDVTWXNmZmMwdVlWRw?oc=5">MLPerf&reg; Inference v6.1 Results: CoreWeave Leads Providers</a> &mdash; CoreWeave&#8217;s September 16, 2026 post detailing its Datacenter Closed, Available submissions across four NVIDIA Blackwell platforms. See also <a href="https://news.google.com/rss/articles/CBMickFVX3lxTE5EQnRiYTgzdlJNMk10Z01wY3daTFRjRm5NWjZ6aUw4X0NhZkZtdWlqMWxMc3ZqeVVUX0MtMl9pTFI0X0pTdEZWenB5NHg1VVpVQi1RSE5tOF82REJGMUFjbUx5WVg3RUxxY0VKa2tSMHp5UQ?oc=5">NVIDIA Vera Rubin NVL72 Delivers Leading Performance in MLPerf Inference v6.1 Debut</a>, NVIDIA&#8217;s account of the same benchmark round.</p>
<p>Primary sources: <a href="https://www.sec.gov/Archives/edgar/data/1769628/000176962826000429/crwv-20260917.htm">CoreWeave, Inc. Form 8-K filed September 17, 2026</a> (Items 7.01 and 8.01, disclosing the proposed convertible notes offering and the Equity Distribution Agreement); <a href="https://www.sec.gov/Archives/edgar/data/1769628/000176962826000429/ex9911.htm">Exhibit 99.1 &mdash; CoreWeave Announces Proposed $3.0 Billion Convertible Senior Notes Offering</a>; and <a href="https://www.sec.gov/Archives/edgar/data/1769628/000176962826000429/crwv2026convertpresentat.htm">Exhibit 99.2 &mdash; CoreWeave Investor Presentation, September 2026</a>. Full benchmark tables are published by MLCommons at <a href="https://www.mlcommons.org">mlcommons.org</a>.</p>
</section>
</div>
<aside class="jain-rail">
<section class="jain-gaps" aria-label="What the release does not say">
<p class="jain-gaps-kicker">⚠ What They Aren’t Saying</p>
<h2>What the Release Doesn&#8217;t Say</h2>
<ul>
<li><strong>Price.</strong> CoreWeave frames per-GPU throughput as mapping directly to inference economics, but publishes no GPU-hour pricing alongside the benchmark. Without it, tokens per accelerator cannot be converted into cost per token by a prospective customer.</li>
<li><strong>The composition of the 19.8%.</strong> The company has not broken out how much of the DeepSeek-R1 gain came from software tuning versus the move from a 64-accelerator to a 72-accelerator submission, nor detailed what else changed between the two configurations.</li>
<li><strong>Fleet coverage.</strong> CoreWeave has not said what share of its deployed base runs the optimised serving stack, or whether customers on older contracts receive these gains automatically.</li>
<li><strong>Next generation.</strong> Neither CoreWeave nor NVIDIA has stated, in this material, when Vera Rubin NVL72 becomes available to CoreWeave customers, at what capacity, or what it does to the useful life assumptions on Blackwell racks bought this year.</li>
<li><strong>Financing terms.</strong> The interest rate, initial conversion rate and cap on the capped calls for the $3.0 billion notes are, by CoreWeave&#8217;s own statement, determined at pricing. The size of the at-the-market programme and any use of proceeds beyond the capped calls and &#8220;general corporate purposes&#8221; are undisclosed.</li>
<li><strong>Power and capacity.</strong> Rack-scale results of this density imply substantial power and liquid-cooling commitments; CoreWeave has not tied the benchmark to contracted megawatts, site locations or delivery schedules.</li>
</ul>
</section>
<section class="jain-faq">
<h2>Frequently Asked Questions</h2>
<h3>What did CoreWeave announce?</h3>
<p>On September 16, 2026, CoreWeave published its MLPerf Inference v6.1 submissions, claiming leading throughput among cloud providers across four NVIDIA platforms and four model families, including the highest per-GPU result of any v6.1 Datacenter Closed submission on GPT-OSS-120B.</p>
<h3>What is MLPerf Inference?</h3>
<p>It is a benchmark suite run by MLCommons that measures how fast systems serve trained AI models. Results are published in rounds; v6.1 results were published on September 16, 2026, and the full tables are available at mlcommons.org.</p>
<h3>What do &quot;Datacenter Closed&quot; and &quot;Available&quot; mean?</h3>
<p>Closed means every submitter runs the same reference implementation, making results comparable rather than a contest in custom code. Available means the system can actually be purchased or rented, as opposed to preview or research hardware.</p>
<h3>Which models did CoreWeave benchmark?</h3>
<p>Four: Qwen3-VL-235B-A22B, a multimodal model that handles images as well as text; DeepSeek-R1-671B, a large mixture-of-experts reasoning model; GPT-OSS-120B, an open-weight reasoning model; and Llama 2 70B, a widely deployed large language model.</p>
<h3>What is the headline per-GPU number?</h3>
<p>On a single NVIDIA GB300 NVL72 rack, CoreWeave reported 16,635 tokens per second per GPU on GPT-OSS-120B in the offline scenario and 16,118 in the server scenario — which it says were the highest per-GPU figures of any v6.1 Datacenter Closed submission on that model, on any silicon.</p>
<h3>What is the 19.8% figure?</h3>
<p>CoreWeave compared its 72-GPU v6.1 submission with its 64-GPU v6.0 submission on NVIDIA GB200 NVL72 and calculated that derived per-GPU server throughput on DeepSeek-R1-671B rose 19.8% in the five months between benchmark rounds, from software and operational tuning rather than new hardware.</p>
<h3>Is the per-GPU metric verified by MLCommons?</h3>
<p>No. CoreWeave states in its own footnote that per-GPU throughput is a derived metric — total system throughput divided by accelerator count — and that the result is not verified by MLCommons. The underlying system-level submissions are the verified figures.</p>
<h3>Why does a software-only gain matter so much?</h3>
<p>Accelerators are bought once and depreciate on a fixed schedule. If output per accelerator rises without new capital spending, cost per token served falls across the asset&#8217;s remaining life and the installed base becomes more valuable rather than less.</p>
<h3>What is a GB300 NVL72?</h3>
<p>An NVIDIA rack-scale system in which 72 accelerators share a single NVLink domain, a very high-bandwidth interconnect that lets the chips exchange data far faster than standard networking. The deployment unit is the rack, not the individual server.</p>
<h3>What rack-level throughput did CoreWeave report?</h3>
<p>On one GB300 NVL72 rack it reported over 1.16 million tokens per second on GPT-OSS-120B in the server scenario and over 1.19 million offline, plus 944,902 tokens per second server and 1,136,100 offline on Llama 2 70B.</p>
<h3>What did NVIDIA announce in the same round?</h3>
<p>NVIDIA published a blog post stating that its next-generation Vera Rubin NVL72 delivered leading performance in its MLPerf Inference v6.1 debut. CoreWeave&#8217;s own submissions were all on the current Blackwell and Blackwell Ultra generations.</p>
<h3>What did CoreWeave file with the SEC the following day?</h3>
<p>An 8-K dated September 17, 2026 disclosing a proposed $3.0 billion offering of convertible senior notes due 2033, with an option for up to $500 million more, plus an Equity Distribution Agreement for at-the-market and collared forward share sales through eleven banks.</p>
<h3>What are capped call transactions?</h3>
<p>Privately negotiated derivatives a company buys alongside convertible notes to offset dilution if the notes convert into stock. The offset applies up to a cap; above that level, dilution is not neutralised. CoreWeave says it will fund them from note proceeds.</p>
<h3>What does CoreWeave&#x27;s existing debt look like?</h3>
<p>Its September 17 release lists senior notes at 9.250% due 2030, 9.000% and 9.750% due 2031, 9.625% and 8.500% due 2032, and convertible notes at 1.75% due 2031 and 2032. The new notes will rank alongside them as senior unsecured obligations.</p>
<h3>Should buyers treat these results as a price quote?</h3>
<p>No. Throughput is one input into cost per token; the other is what the capacity costs per hour, which the benchmark does not cover. Buyers should also confirm which silicon generation produced a given figure and whether it is a submitted or derived number.</p>
<h3>Does this make CoreWeave cheaper than other clouds?</h3>
<p>The results support a claim about output per accelerator, not about price. Without published GPU-hour rates and matched configurations, higher throughput cannot be converted into a lower bill; it establishes the numerator, not the denominator.</p>
</section>
</aside>
</div>
<p><script type="application/ld+json">{"@context": "https://schema.org", "@graph": [{"@type": "NewsArticle", "headline": "Everyone's Watching New AI Silicon. CoreWeave Found 19.8% in Racks It Already Had.", "description": "CoreWeave published MLPerf Inference v6.1 results on four NVIDIA Blackwell platforms, including 16,635 tokens per second per GPU on GPT-OSS-120B. The more consequential figure is a 19.8% per-GPU gain booked in five months on hardware already in the field \u2014 and a $3.0 billion convertible note filed the next day.", "image": ["/wp-content/uploads/2026/09/coreweave-mlperf-inference-v6-1-gb300-nvl72-per-gpu-throughput.webp"], "author": {"@type": "Organization", "name": "jain.com Editorial"}, "datePublished": "2026-09-17T19:31:59.011966+00:00"}, {"@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "What did CoreWeave announce?", "acceptedAnswer": {"@type": "Answer", "text": "On September 16, 2026, CoreWeave published its MLPerf Inference v6.1 submissions, claiming leading throughput among cloud providers across four NVIDIA platforms and four model families, including the highest per-GPU result of any v6.1 Datacenter Closed submission on GPT-OSS-120B."}}, {"@type": "Question", "name": "What is MLPerf Inference?", "acceptedAnswer": {"@type": "Answer", "text": "It is a benchmark suite run by MLCommons that measures how fast systems serve trained AI models. Results are published in rounds; v6.1 results were published on September 16, 2026, and the full tables are available at mlcommons.org."}}, {"@type": "Question", "name": "What do \"Datacenter Closed\" and \"Available\" mean?", "acceptedAnswer": {"@type": "Answer", "text": "Closed means every submitter runs the same reference implementation, making results comparable rather than a contest in custom code. Available means the system can actually be purchased or rented, as opposed to preview or research hardware."}}, {"@type": "Question", "name": "Which models did CoreWeave benchmark?", "acceptedAnswer": {"@type": "Answer", "text": "Four: Qwen3-VL-235B-A22B, a multimodal model that handles images as well as text; DeepSeek-R1-671B, a large mixture-of-experts reasoning model; GPT-OSS-120B, an open-weight reasoning model; and Llama 2 70B, a widely deployed large language model."}}, {"@type": "Question", "name": "What is the headline per-GPU number?", "acceptedAnswer": {"@type": "Answer", "text": "On a single NVIDIA GB300 NVL72 rack, CoreWeave reported 16,635 tokens per second per GPU on GPT-OSS-120B in the offline scenario and 16,118 in the server scenario \u2014 which it says were the highest per-GPU figures of any v6.1 Datacenter Closed submission on that model, on any silicon."}}, {"@type": "Question", "name": "What is the 19.8% figure?", "acceptedAnswer": {"@type": "Answer", "text": "CoreWeave compared its 72-GPU v6.1 submission with its 64-GPU v6.0 submission on NVIDIA GB200 NVL72 and calculated that derived per-GPU server throughput on DeepSeek-R1-671B rose 19.8% in the five months between benchmark rounds, from software and operational tuning rather than new hardware."}}, {"@type": "Question", "name": "Is the per-GPU metric verified by MLCommons?", "acceptedAnswer": {"@type": "Answer", "text": "No. CoreWeave states in its own footnote that per-GPU throughput is a derived metric \u2014 total system throughput divided by accelerator count \u2014 and that the result is not verified by MLCommons. The underlying system-level submissions are the verified figures."}}, {"@type": "Question", "name": "Why does a software-only gain matter so much?", "acceptedAnswer": {"@type": "Answer", "text": "Accelerators are bought once and depreciate on a fixed schedule. If output per accelerator rises without new capital spending, cost per token served falls across the asset's remaining life and the installed base becomes more valuable rather than less."}}, {"@type": "Question", "name": "What is a GB300 NVL72?", "acceptedAnswer": {"@type": "Answer", "text": "An NVIDIA rack-scale system in which 72 accelerators share a single NVLink domain, a very high-bandwidth interconnect that lets the chips exchange data far faster than standard networking. The deployment unit is the rack, not the individual server."}}, {"@type": "Question", "name": "What rack-level throughput did CoreWeave report?", "acceptedAnswer": {"@type": "Answer", "text": "On one GB300 NVL72 rack it reported over 1.16 million tokens per second on GPT-OSS-120B in the server scenario and over 1.19 million offline, plus 944,902 tokens per second server and 1,136,100 offline on Llama 2 70B."}}, {"@type": "Question", "name": "What did NVIDIA announce in the same round?", "acceptedAnswer": {"@type": "Answer", "text": "NVIDIA published a blog post stating that its next-generation Vera Rubin NVL72 delivered leading performance in its MLPerf Inference v6.1 debut. CoreWeave's own submissions were all on the current Blackwell and Blackwell Ultra generations."}}, {"@type": "Question", "name": "What did CoreWeave file with the SEC the following day?", "acceptedAnswer": {"@type": "Answer", "text": "An 8-K dated September 17, 2026 disclosing a proposed $3.0 billion offering of convertible senior notes due 2033, with an option for up to $500 million more, plus an Equity Distribution Agreement for at-the-market and collared forward share sales through eleven banks."}}, {"@type": "Question", "name": "What are capped call transactions?", "acceptedAnswer": {"@type": "Answer", "text": "Privately negotiated derivatives a company buys alongside convertible notes to offset dilution if the notes convert into stock. The offset applies up to a cap; above that level, dilution is not neutralised. CoreWeave says it will fund them from note proceeds."}}, {"@type": "Question", "name": "What does CoreWeave's existing debt look like?", "acceptedAnswer": {"@type": "Answer", "text": "Its September 17 release lists senior notes at 9.250% due 2030, 9.000% and 9.750% due 2031, 9.625% and 8.500% due 2032, and convertible notes at 1.75% due 2031 and 2032. The new notes will rank alongside them as senior unsecured obligations."}}, {"@type": "Question", "name": "Should buyers treat these results as a price quote?", "acceptedAnswer": {"@type": "Answer", "text": "No. Throughput is one input into cost per token; the other is what the capacity costs per hour, which the benchmark does not cover. Buyers should also confirm which silicon generation produced a given figure and whether it is a submitted or derived number."}}, {"@type": "Question", "name": "Does this make CoreWeave cheaper than other clouds?", "acceptedAnswer": {"@type": "Answer", "text": "The results support a claim about output per accelerator, not about price. Without published GPU-hour rates and matched configurations, higher throughput cannot be converted into a lower bill; it establishes the numerator, not the denominator."}}]}]}</script></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
