Blizzard Spent Big on WoW: Forever Launch: 70,480 Cores, 251 TB RAM

Blizzard provisioned 3,924 virtual machines with 70,480 CPU cores and 251,136 GB of memory for the launch of World of Warcraft: Forever. That is 251 TB of RAM across a single game launch. The company has not disclosed what it spent, but the raw allocation is the largest publicly described for a Blizzard title launch.

Media and players praised the launch night as one of the smoothest in Blizzard's history. That verdict matters. Blizzard launches are usually chaos. This time, the company simply paid the infrastructure bill up front.

What does the hardware actually look like?

The per-instance math is straightforward. 3,924 virtual machines with 70,480 cores and 251 TB of memory works out to 18 cores and 64 GB of memory per instance. Blizzard could also be using a mixture of 16-core and 32-core nodes with slightly less memory per node. The company has not said which configuration applies.

In consumer terms, the allocation equals roughly 8,810 mainstream processors, or 7,848 high-end gaming systems with 32 GB of memory each. That is an estimate, not a confirmed count.

Blizzard does not specify the exact hardware behind the game. Tom's Hardware, which first reported the figures, offers a translation: if the cores map to AMD's 128-core EPYC Bergamo or 96-core Genoa processors, the fleet would fit in 275 to 365 2U server nodes. That would occupy eight to ten 42U server racks. The estimate carries clear caveats, since Blizzard confirms none of it.

How does this compare with 2009?

The historical contrast is the sharpest data point in the story. In 2009, Blizzard said it ran World of Warcraft on 10 data centers worldwide. That infrastructure held 13,250 server blades, 75,000 CPU cores and 112.5 TB of memory.

WoW: Forever uses 6% fewer CPU cores than that 2009 fleet. It carries 2.2 times more memory. Modern processors are far faster than chips from 17 years ago, so the trade makes sense: by today's standards, the bottleneck is memory capacity and bandwidth, not core count. Fewer cores, double the memory, and the workload still runs.

What did it cost, and who paid?

A ballpark estimate puts ten 42U server racks with EPYC chips at a minimum of $15 million, even at today's elevated memory pricing. That figure is an analyst-style estimate from Tom's Hardware, not a Blizzard number.

There is a second possibility. Microsoft owns Blizzard now, so the company could be tapping its parent's existing Azure platform. That compute is not free. Blizzard would, however, benefit from cost pricing and priority allocation of Azure's capacity. Blizzard has not confirmed either path, and the source reports no procurement details.

What does the launch prove?

The lesson is narrow but real. A high-profile launch does not have to collapse when the operator invests in compute ahead of demand. Blizzard put 251 TB of memory to work and got a clean night. Whether that investment was $15 million of owned racks or discounted Azure capacity, the commercial logic held.

The caveat is obvious. One smooth launch on 3,924 virtual machines does not set a budget baseline for the industry, and Blizzard's silence on cost leaves the economics unverified. If memory pricing stays high, expect rivals to study this launch closely before matching it — and to weigh whether rented Azure capacity beats a $15 million rack build.