Battle.net games: Warzone, Diablo, WoW optimization on Windows

Battle.net hosts some of the most CPU-intensive games. The launcher itself adds overhead. Here's the optimization stack for Battle.net titles.

Battle.net launcher overhead

The launcher keeps a background process running even when a game is open. Bnet.exe and Agent.exe both consume CPU and memory.

After launching your game, you can close the launcher from the system tray — most games keep running. Exception: some games require the launcher to stay open for DRM validation.

Per-game process priority

Warzone (Call of Duty):

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\cod.exe\PerfOptions
CpuPriorityClass = 3
IoPriority = 3
GpuPriority = 8

World of Warcraft:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\Wow.exe\PerfOptions
CpuPriorityClass = 3
IoPriority = 3
GpuPriority = 8

Battle.net cache

The launcher caches game data in:

%programdata%\Battle.net\
%localappdata%\Battle.net\

These can grow large. Safe to clear — the launcher recreates them.

WoW specifically

WoW is CPU-bound on crowded servers (raids, cities). Core parking off and Ultimate Performance plan matter here more than for most games. Win32PrioritySeparation=38 helps with the raid frame rate consistency.

Warzone specifically

Large open map, many assets. Shader compilation stutters are normal on first few sessions. After shader cache is built, performance stabilizes.

Full optimization for all Battle.net titles at https://terweb.lt/