Keep the game on the largest-L3 die only when that die has 8 cores, and reserve no recorder core there.

cache_die moved the process to the logical processors of the largest L3 cache whenever the L3 sizes differed. That is
right for a two-die X3D desktop part with 8 cores a die, but it also held the game to the 4 large cores of a mobile
part whose 8 small cores share a smaller L3, and to the 6 cores of a 12-core X3D part, where the recording thread's
reserved core then left the game 5. The die is now used only when it has 8 or more physical cores (perf.c
cpu_placement logs when one is passed over). And while the process runs on that die alone, RECORDER_CORE=auto
reserves no core for the recording thread, since the game's threads already have the die to themselves; =1 still
reserves one.

Checked: all runtime files compile. This PC has a single-die processor (one L3), where neither rule applies: a run
still reserves the recording core (logical processors 14 and 15 of 16) and logs no cache die.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-11 17:22:20 -05:00
parent 01164679d4
commit 2cccdb8823
4 changed files with 25 additions and 5 deletions

View File

@@ -74,7 +74,8 @@
# timer_1ms = 1
# The thread that records the GPU work (the first to spend half a second doing it, not the one that submits first) keeps
# the highest scheduling priority (recorder_prio), and a core of its own that the process's other threads stay off
# (recorder_core: auto = with 12 or more logical processors, 1 always, 0 never). That is a fast core, with both of its
# (recorder_core: auto = with 12 or more logical processors, unless the game runs on the cache die below, 1 always,
# 0 never). That is a fast core, with both of its
# logical processors: on Windows the highest-numbered core of the fastest efficiency class; on Linux the performance
# core that clocks highest on a hybrid CPU (else the core of the highest capacity or clock), and none when fewer than
# four cores are that fast. The log names the thread and its logical processors.
@@ -96,7 +97,8 @@
# dyn_res_target = 16.7
# dyn_res_step = 45
# Processors. On a processor whose dies have L3 caches of different sizes (AMD's two-die X3D processors, with 3D
# V-Cache on one die) the game runs on the die with the larger cache: 1 = on, 0 = Windows places the threads.
# V-Cache on one die) the game runs on the die with the larger cache when that die has 8 cores or more: 1 = on,
# 0 = Windows places the threads.
# cache_die = 1
# One logical processor of each physical core, so no two busy threads share a core: 1 = on, 0 = all of them.
# one_per_core = 0