Raise the pipeline cache's size limit to 1024 MB, and leave never-drawn list pipelines to their first draw on a machine short of memory.

The limit was 512 MB, and a file over it starts the run empty until a play file replaces it. With the pipeline list of 0.9.1 one run builds more than that: on an RTX 2080 Ti (#722) pipeline-cache.bin held 551 MB and the play file the run then wrote 541 MB, so both were dropped at every start, 7,247 of 8,531 pipelines were built again each time (17 s of the boot) and 541 MB were written in every session. Seven of the players' logs read here have a file over 512 MB, five of them between 517 and 691 MB. At 1024 MB those are read, the play file is folded in once and the loop ends; a start that still finds both files over the limit now says so.

pipe_seed_boot (auto, 1, 0) decides whether the boot builds the pipelines of the shared list that the install has never drawn. Each is a pipeline the driver holds for the whole run: the boot's pipeline stage went from about 1.6 GB of commit on 0.8.0 to 3.9-4.4 GB on NVIDIA cards with the list (1.5-1.8 GB on AMD's driver), and 0.3-0.6 GiB of video memory. auto, the default, builds them as before except on a machine that starts with less commit free than the game takes in play, the start's own memory warning: there they are made at their first draw from the pipeline cache and recorded as the install's own. Mesh pipelines are built at boot either way. Compiled; not run in the game.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-12 15:13:40 -05:00
parent afe44e0e54
commit 823e0cdcd4
4 changed files with 66 additions and 10 deletions

View File

@@ -188,8 +188,10 @@
# build_reserve_mb = 64
# 1: the log says how many pipelines came from pipeline-cache.bin; 2 also logs every compute pipeline built. 0: off.
# pipe_feedback = 1
# pipeline-cache.bin larger than this (MB) starts empty and is rewritten (0: no limit).
# pipeline_cache_max_mb = 512
# pipeline-cache.bin larger than this (MB) starts empty and is rewritten (0: no limit). With the pipeline list of
# 0.9.1 and later a full cache is about 550 MB on an NVIDIA card, so the limit has to stay well above that: under
# it the cache is thrown away at every start and the pipelines are built again each time. Default: 1024.
# pipeline_cache_max_mb = 1024
# 1: the pipelines a run compiles go into pipeline-cache-play.bin, a small file of its own, so pipeline-cache.bin
# (hundreds of MB) is not written again while you play; the small file is folded into the large one at a start once
# it has grown. 0: one file, written whole whenever a run made a new pipeline.
@@ -211,6 +213,13 @@
# Count the shared pipeline list that comes with the release (seed-pipeline-keys.bin) as known pipelines, so a new
# install builds them at the start instead of at their first draw. 0: only the pipelines this install drew.
# pipe_seed = 1
# Whether the start builds the pipelines of that list which this install has never drawn. They take 2 to 4 GB of
# memory (commit) on an NVIDIA card and about 1.5 GB on an AMD one for the whole run, drawn or not.
# auto (default): built at the start, except on a PC that starts with less memory free than the game takes in play
# (the start's "this machine has ... MB of memory left for the game" warning): there each is made at its first
# draw, from the pipeline cache, and built at the start from then on.
# 1: always built at the start. 0: never; a first visit to an area can then hold a frame for a moment.
# pipe_seed_boot = auto
# 1: the start waits until every known pipeline is built. Default 0: with the graphics pipeline library the start
# builds them for at most 20 seconds and the rest in the background while you play.
# prewarm_full = 0