perf(vk): an update that changes the translator keeps the driver's pipelines and the notes #1927
No reviewers
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!1927
Loading…
Reference in a new issue
No description provided.
Delete branch "madebyjordan/Longshot:perf/pipelines-outlive-translator"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
What was wrong: every Longshot update that changed the shader translator made the first start compile every Vulkan pipeline from scratch: 83 minutes on my RX 6700 XT, and hours on many AMD PCs. That's because the driver's pipeline cache (
longshot_vk_pipelines.bin) and the pipeline notes (longshot_pipelines.bin, which pipelines play drew) were dropped with the program cache. Yet a new translator gives most programs byte-identical SPIR-V (99.6% between a stable and a nightly, #1649), so nearly every pipeline in that cache was still good. Translator changes are frequent, which makes this the biggest cost of an update after the build itself. nightly-649 and nightly-665 were already one: #1448 moved the translator's stamp, so a player updating to either compiles every pipeline cold. This stops it at the next translator change.What this changes:
gpu/vk/pcache_stamp.h) is carried to another translator, within a bound:longshot_vk_pipelines.base) is that size when a precompile had finished for the translator being left and its pipelines had reached the file (the.builtrecord's fourth word,kBuiltWhole). Only then is it the size of one whole set of pipelines. A start that gave up on the build after two crashed in it leaves the record without that word.vkMergePipelineCachesonly adds), so this bounds the growth that issue 388's drop was for.gpu/vk/vk_draw.cpp) get a stamp of their own (kNotesFormat,notes_stamp) instead of the program cache's.key_inputs: the vertex shader's loads, and, without EDS3 blend, the write masks). So every place that keeps a pipeline built from a note under the note's key now checks that the key still holds (note_key_holds): the start's notes build, the load at a create call, and the programs' loader. A note whose key is another translator's is passed over and counted (notes passed overin the log), keeps no shader modules loaded, and play notes it again. Its old key is freed for whichever state makes that key now (note_new_locked), and readers take a key's last note.tests/test_notes_format.pyfingerprints what a note holds (PipeNote,NvnStateand the NVN types in it,nvn_va_stincluded) and fails untilkNotesFormatis raised with any change to it..builtrecord (so the warm runs, finding most pipelines in the cache), the module identifiers and the prediction's files.The launcher side: LongshotLauncher MagicBeanDev/LongshotLauncher#220 keeps the pipeline side across an update to another translator. Today it keeps nothing then, so the game would have nothing to carry.
Builds on #1926 (merged), whose
pipelines_stamp_okthis uses.Read first:
gpu/vk/pcache_stamp.h(judge,check, the base), and ingpu/vk/vk_draw.cpp:notes_stamp,notes_stamp_ok,notes_restampandnote_key_holds.Testing
Tested: Windows 11 Home 26200, AMD Radeon RX 6700 XT, Ryzen 5 5600.
3c639b12on mainb62932a9; this head adds only main's9dd41326, a lift change that touches no renderer file):.builtrecord with its fourth word, and the next start trusted it.another translator's (2082 MB, 2082 MB when a precompile last finished alone) carried. The base is 2,183,937,832 bytes, exactly the main and play files. It prepared in 31 s and played with the right picture.0b355428; a test-only translator, never committed, adding anOpNopto about 42% of the fragment shaders):notes passed overpath did not run in the game. Its game-free tests cover it.longshot.exe --prepare-shaders --compile-shaders most, asmake_game.pyruns it), on head5257fd3f. This is a real translator change: nightly-622 to current main, which has #1448.cache/was seeded with a copy of my prepared nightly-622 folder's caches.pipeline cache: another translator's (1839 MB, no precompile finished for it yet) carried;prepared 38809 shader programs ... in 124.4 s;precompile: 38024 noted pipelines ... (0 and 0 not made ...) in 7.2 s, withthe pipeline cache not written: nothing new(every pipeline a hit).test_pipelines_outlive_cache_format: another translator's build carries the pipeline cache and keeps the notes; past the bound the cache is dropped and the notes kept; notes stamped as before are stamped anew by their own translator, whether opened for play or only read, and kept by the next; another translator's legacy notes are dropped once.test_pcache_stamp: the verdict and the base's life: the play files counted, a base only from a finished precompile, growth before one not dropped, at most 8 carries without one, a carry cut short finished and not counted twice, a failed base write, a file that won't go, and a base not taken beside another stamp.test_pcache_stamp,test_warm_bounded: a.builtrecord without its fourth word gives no base, and the start that gave up never writes that word.test_pipelines_outlive_cache_format,test_note_refs_once: a key only a passed-over note holds can be noted again, once; both readers take the later note; a preparation that only walks the notes restamps them.test_notes_format(new): the layout fingerprint, and the three places checkingnote_key_holds.test_pipelines_outlive_cache_formatalso runs the realnote_key_check.kNotesFormat. Thetest_pcache_stampadditions don't compile there (noBase, nojudge).note_key_holds; a note's layout changed (two members ofnvn_vs_stswapped); the play files not counted; a base taken from an unfinished cache; the stamp moved after a failed base write; a resumed carry counted twice; a half-done carry's base refused; a stale base taken; a held file moving the stamp; unlimited unfinished carries;note_key_checkalways true; and, for the second review's fixes, nine more (the fourth word ignored, written by the start that gave up or without a save; a passed-over key not freed, freed forever or ignored bypipeline_note; either reader keeping the first note; the walk not restamping).tests/run_all.py --strict, whatmise run testruns; Windows, llvm-mingw), on this head and on main9dd41326: 712 passed, 155 failed, 48 skipped here; 710, 156, 48 on main. All 155 also fail on main (tools this PC lacks, and Windows-only differences). Main's one extra failure istest_longshot_ctl, a process-timing check this PR doesn't touch, andtest_notes_formatis new here. Checks that follow the change:test_fsr4_own_cache's fixture now drops by the bound;test_loaded_modules_drop,test_program_load_wait,test_precompile_pipeline_cleanup,test_note_refs_onceandtest_state_list_part_recordgain the new calls and stand-ins.3c639b12. Linux has not been built (Still to test).note_key_holds);Still to test:
another translator's ... carriedand a preparation of minutes (by hand, as this needs an older build's caches)Measurements
Verdict: after a translator change the launcher's preparation takes about 2¼ minutes instead of 83: the driver's pipelines are carried, so only the programs are translated again. A carried cache 1.38 times its base costs about 0.7 GB of RAM and 2.5 s at start, with no measurable VRAM cost.
Setup: Windows 11, RX 6700 XT, Ryzen 5 5600; the launcher's preparation over a folder prepared by nightly-622, AMD's own driver cache cold (a new folder path); the real translator change from nightly-622 to main
f1f2dc5b. One run each, since the gap is 37×. The before is nightly-622's own run: main still drops these files at a translator change, as #1926 covers format changes only.fb14ba0b(nightly-622, a translator or format change)5257fd3fThis translator change added nothing to the cache. One that rewrites more SPIR-V compiles those programs' pipelines: 40 minutes when about 42% of the fragment shaders changed (Testing).
Why these numbers still hold on main
9dd41326: the before is nightly-622's own run, not a run of the merge base. Main still drops the pipeline cache at a translator change and compiles every pipeline, and the commits since touch neither that path nor the compile. A 37-times gap doesn't depend on the exact before.The cost of a carried cache near its bound (head
0b355428on maine6196f0f; the same PC; timing mode, V-Sync off, the same spot of thehyrule-fieldteleport; 3 interleaved pairs after a discarded warm-up of each; medians):The fps difference by pair was -2.4, -8.8 and +1.4, so three pairs can't tell it from run-to-run noise.
Risks
note_key_holdsguards every such place, andtest_notes_formatholds the list. No in-game run has moved a key yet, so this path is covered by game-free tests only. Pipelines built only into the driver's cache (the warm) are found by their contents, so a stale note there costs one useless build at most..builtrecord and ignores the fourth.make_game.pyseed_pipelines, which compares a notes file's first 8 bytes) would need its seed stamped withnotes_stamp. No build ships a seed today: neither the downloaded tools nor any build script has one.Checklist
Ready for review
main; the title is a Conventional Commit.mise run testpasses (any failure that also fails onmainis named).main, or Measurements says why there is nothing to measure.third_party/untouched; nothing GPL-incompatible.When it applies
mainand passes here.tests/that reads changed source is updated, not weakened.Assisted-by:/Co-Authored-By:trailers.Ready to merge
main, measured again or a comment says why the numbers still hold.🤖 Generated with Claude Code
A translator change dropped the driver's pipeline cache (longshot_vk_pipelines.bin) and the pipeline notes with the program cache, so every such update compiled every pipeline again cold (hours on AMD) and the preparation no longer knew which ones play had drawn. Yet a new translator gives most programs the same SPIR-V (99.6% of them between a stable and a nightly), whose pipelines the driver's cache still had. The pipeline cache (pcache_stamp.h): another translator's files are carried within a bound. A cache that holds one translator's pipelines alone is always carried; the first carry records its size as the base (longshot_vk_pipelines.base, beside the stamp it was written with, and taken only beside that stamp); from then on, while the file holds pipelines no one hits again, it is carried while at most half as large again as its base and dropped past that, the base with it. A Vulkan pipeline cache cannot be pruned (no enumeration; vkMergePipelineCaches only adds), so this bounds the growth issue 388's drop was for. The base is a file of its own so builds from before it read the stamp file as ever; one that drops by its stamp leaves a base no later start takes. The notes (vk_draw.cpp): stamped by their own layout (kNotesFormat, notes_stamp) instead of the program cache's stamp. A note holds what the game asked, its program found by the guest code's key; but its pipeline key mixes in what the translator made (key_inputs: the vertex loads, and without EDS3 blend the write masks), so a note built under another translator could hand a draw a pipeline made for another state. Every place that keeps a pipeline built from a note under its key now checks the key holds (note_key_holds: the start's notes build, the load at a create call, the programs' loader), passing over and counting the notes whose key is another translator's ("notes passed over" in the log; 0 under one translator). A notes file of this translator stamped as before is read and stamped anew; tests/test_notes_format.py fails until kNotesFormat is raised with any change to what a note holds. What still starts over with the translator: the program file, the prepare record, the .built record (so the warm runs, finding most pipelines in the cache), the module identifiers and the prediction's files. scripts/devtools/packs.py copies the base with the other caches; checks that read the changed source follow it (test_fsr4_own_cache's fixture drops by the bound, stand-ins gain the notes' stamp and note_key_holds). Assisted-by: Claude Code (Claude Opus 5.5)Tested in game: Windows 11, RX 6700 XT: the launcher's preparation (--prepare-shaders --compile-shaders most) of a dev runtime of this branch with the translator's stamp moved (a test-only constant in vk_state.h, no SPIR-V change), over a copy of my prepared nightly-622 caches, AMD's own driver cache cold: 'another translator's (1839 MB) carried', 38809 programs translated in 127.9 s, 38024 noted pipelines from the cache in 6.9 s (nothing new compiled): about 2 1/4 minutes against 83 for nightly-622.
Recommendation: Request changes. The growth bound excludes play-cache files and can lose its base when metadata writes fail, so it does not reliably bound the cache carried across updates. The additional memory cost is also unmeasured.
The change carries Vulkan pipeline caches and compatible pipeline notes across translator updates, potentially avoiding lengthy recompilation. It adds cache-growth accounting and note-key checks, but the accounting misses play files and does not handle failed metadata writes; the resulting memory and startup costs need measurement.
Does it help: Unproven. The PR reports one Windows RX 6700 XT run at about 2¼ minutes versus 83 minutes for nightly-622, using a synthetic stamp change with identical SPIR-V. This is encouraging, but it is not repeated against the specified base or a real translator change, and warm startup, RAM and VRAM costs are missing.
Other systems: Windows AMD preparation was reported; Linux, Windows NVIDIA, Steam Deck and real translator changes remain untested. Play-cache generations contribute to the cache merged at startup but are excluded from the growth decision. The launcher must also preserve the files; its companion PR is required.
Switches: None added, changed or removed. The carry policy is on by default and has no switch; a revert is the stated way back.
Reviewed:
060284843bagainsta104182b40: Read AGENTS.md, CONTRIBUTING.md, the PR template, standards, the commits and the production diff, including pcache_stamp.h in full. Inspected portions of the changed renderer code, callers and tests; the very large renderer files, all changed tests and scripts were not read in full. The requested review checklist file is absent. Tooling's external rules and overlapping PRs could not be inspected in this offline review.; nothing run (a code review).Checked and fine:
Blocking (to change before merge)
Testing: No code or tests were run, as requested. The author's reported source checks, syntax checks and single hardware preparation run were considered as reported evidence.
Overlaps and merge order: Stacked on Longshot #1926, which the author says must merge first; LongshotLauncher #220 supplies the launcher side. Other overlaps were not checked.
Automated code review by BeanBot (gpt-6.1-terra), on the pull request's opening. Nothing was run; a maintainer decides.
@ -22,1 +32,4 @@inline const char* kPlayPrefix = "longshot_vk_pipelines_play_";inline const char* kBaseFile = "longshot_vk_pipelines.base";/// How far the main file may have grown past its base and still be carried to another translator (3/2: half as large again)Please measure RAM, VRAM and warm-start costs for this default against the base, including a grown carried cache. The reported preparation time does not establish whether the extra resident cache is acceptable on affected systems.
@ -67,0 +126,4 @@std::error_code size_ec;const uintmax_t main = std::filesystem::file_size(dir + kMainFile, size_ec);d.main = size_ec ? 0 : (uint64_t)main;d.base = have ? read_base(dir, kept) : 0;This measures only the main file, but startup also merges the play-generation files. A small main file plus large play files can pass the bound and load a much larger cache. Please include the carried generations in the decision and cover that case.
@ -67,0 +134,4 @@write_base(dir, Base{d.base, stamp});write(dir, stamp);d.carried = true;return d;Please handle failure of these writes as a single failure-safe transition. If the base write fails but the stamp write succeeds, the next update treats the mixed cache as having no base and can carry it as though it held one translator.
WIP: perf(vk): an update that changes the translator keeps the driver's pipelines and the notesto perf(vk): an update that changes the translator keeps the driver's pipelines and the notes@fix
I didn't change this pull request: what the review asks needs the author (runs, measurements or decisions, which can't be done here).
Left for the author
Nothing was pushed.
Automated fix by BeanBot (gpt-6.1-terra), asked for by HumanBean. Nothing was run; a maintainer decides.
060284843b736e1be462736e1be4625f447a9d3b@fix
I didn't change this pull request: what the review asks needs the author (runs, measurements or decisions, which can't be done here).
Left for the author
Nothing was pushed.
Automated fix by BeanBot (gpt-6.1-terra), asked for by HumanBean. Nothing was run; a maintainer decides.
@fix
I didn't change this pull request: what the review asks needs the author (runs, measurements or decisions, which can't be done here).
Left for the author
Nothing was pushed.
Automated fix by BeanBot (gpt-6.1-terra), asked for by HumanBean. Nothing was run; a maintainer decides.
5f447a9d3b5257fd3fceRebased onto main
f1f2dc5b(head5257fd3f), now that #1926 has merged. BeanBot's three points on the older head:In the game on this head (Windows 11, RX 6700 XT, the launcher's preparation path, AMD's own cache cold): a real translator change, nightly-622's caches to current main. The cache was carried, 38,809 programs translated in 124.4 s, and 38,024 noted pipelines came from the cache in 7.2 s with nothing compiled. That's 133 s in all, against 83 minutes for nightly-622. The same folder started again took 23 s.
Linux and NVIDIA still need the Test Farm. nightly-649 and nightly-665 already contain #1448, so players updating to them have already recompiled once. This PR protects the next translator change.
5257fd3fce0b35542811@review
The ChatGPT usage limit is reached (it resets Nov 25th, 2026 1:04 AM), so this review is paused. It runs by itself once the limit lifts (tried again every 30 minutes); nothing needs asking again.
Automated code review by BeanBot (gpt-6.1-terra), asked for by HumanBean. Nothing was run; a maintainer decides.
Recommendation: Request changes. The carry can establish its size bound from a cache that was never fully built or saved, and some notes can be lost or remain permanently stale. The reported preparation speedup is promising, but its baseline and the memory cost need controlled measurements.
The change preserves driver pipelines and notes across translator updates, potentially avoiding lengthy cold compilation. It adds cache-lifetime metadata and retains stale notes, increasing startup memory and storage until the cache or notes are reset.
@fixwill do (4)gpu/vk/pcache_stamp.h:97: The .built stamp does not prove the cache contains a finished precompile. (more on the line)gpu/vk/vk_draw.cpp:1924: Stale notes are still inserted into noted by their old keys. (more on the line)gpu/vk/vk_draw.cpp:12179: This reader accepts legacy notes but never restamps them. (more on the line)gpu/vk/pcache_stamp.h:42: Reduce the carry bound or discard accumulated stale cache data sooner if the measurements show an unacceptable cost.For the author (2) (a run, a measurement or a decision)
gpu/vk/pcache_stamp.h:42: Measure cold and warm startup, RAM and VRAM with a carried cache near the bound against a fresh cache, including affected Linux and NVIDIA systems. (more on the line)Checks: Still running:
CI / Website build and checks (pull_request).More: does it help, other systems, switches, what was read
Does it help: Unproven against the requested baseline: the author reports 133 seconds versus 83 minutes on an RX 6700 XT, but these are single runs on different builds, with the before run using nightly-622 rather than the merge-base build. The reported cache hits are strong evidence for the mechanism.
Other systems: Windows AMD preparation was exercised; Linux and NVIDIA remain untested. A changed translator with moved note keys has not been tested in play. Carried caches affect startup time, RAM and potentially VRAM; their near-bound costs are unmeasured. The launcher must preserve these files for updates to benefit.
Switches: No switches added, changed or removed.
Reviewed:
0b35542811againste6196f0f54: Read the repository rules, PR template, standards, commit messages, pcache_stamp.h and test_notes_format.py; inspected the production diff and surrounding cache, precompile and notes-reader paths. Skimmed the remaining changed tests and pack-script change. The full large production files, generated files and translations were not read in full. docs/review-checklist.md and ../Tooling were absent.; nothing run (a code review).Checked and fine:
Testing: No code, tests or project scripts were run, as requested. The author reports an in-game Windows AMD preparation and a suite run; the website check is still running.
Overlaps and merge order: LongshotLauncher#220 must preserve the pipeline files across translator updates for the launcher update path to benefit; coordinate its merge with this change.
Automated code review by BeanBot (gpt-6.1-terra), asked for by HumanBean. Nothing was run; a maintainer decides.
@ -23,0 +39,4 @@/// How far the cache may have grown past its base and still be carried to another translator (3/2: half as large again)constexpr uint64_t kCarryGrowthNum = 3, kCarryGrowthDen = 2;/// How many translators a cache no precompile has finished for is carried through, having no size to be judged byconstexpr uint64_t kUnfinishedCarries = 8;L5 (minor): Measure cold and warm startup, RAM and VRAM with a carried cache near the bound against a fresh cache, including affected Linux and NVIDIA systems. The author estimates 2.8 GB versus 1.9 GB of cache on the tested PC, but the resulting working-set and startup costs are unknown.
@ -47,0 +94,4 @@/// Whether a precompile got to its end for `kept`: the cache then holds every noted pipelineinline bool finished_for(const std::string& dir, uint64_t kept) {FILE* f = fopen((dir + kBuiltFile).c_str(), "rb");L1: The .built stamp does not prove the cache contains a finished precompile. precompile_warm writes it after two interrupted starts without building the notes, and precompile_run writes it before its subsequent cache save. After either case, a translator update can record a partially populated cache as the base; finishing the missing pipelines later can exceed 1.5 times that base and make the following update discard the useful cache. Write and use a separate completion record only after a successful full cache save.
@ -1869,2 +1921,4 @@const bool same = notes_stamp_ok(head[0]) && head[1] == sizeof(PipeNote);if (same) notes_restamp(path, head[0]);if (same) cut_part_record(path, sizeof head, sizeof(PipeNote));if (same && known) {L2: Stale notes are still inserted into noted by their old keys. If a translator change makes an old note's key invalid and a different current state uses that key, the old note is passed over during precompile, but play cannot record the current state because noted already contains the key. That pipeline then remains absent from future precompiles and can repeatedly compile during play. Remove or replace invalid notes when their keys are checked, and test a moved key reused by another state.
@ -12121,7 +12177,7 @@ std::vector<NoteRef> pipe_notes_refs(bool* whole) {FILE* f = fopen(pipe_notes_path().c_str(), "rb");if (!f) return refs;uint64_t head[2] = {0, 0};L3: This reader accepts legacy notes but never restamps them. For example, a create-mode warm that only reads references can finish on the old translator, yet the next translator rejects and loses those notes. Restamp an accepted legacy header after closing this reader and cover this reader in the migration test.
0b3554281173a55f53f0Pushed
73a55f53, rebased on main9dd41326. I checked BeanBot's review of0b355428against the code rather than taking each point as given..builtdoesn't prove the cache is whole: real, fixed. A start that gives up after two crashed builds writes that record without building anything, so a partly filled cache could become the base, and the update after it would compile everything cold. I didn't add the separate completion file it suggested, since it would need the same removal at every place.builtis removed. The record now gains a fourth word only once the file holds the pipelines. A record without it, including every existing one, is carried with no size, which is the safe direction.Also tested in the game: a real SPIR-V change to about 42% of the fragment shaders carried the cache, compiled only what changed in 40 minutes, and played with the right picture. No in-game run has moved a pipeline key yet, so that path rests on its game-free tests, and the description says so.
CI:
Guide screenshotsfails on this head and on main9dd41326with the same 8settings-graphics.pngreview items. They come from menu changes already on main, and this PR changes none of those files.Left before merge: the Test Farm on Linux, NVIDIA and the Steam Deck, and a fresh review of this head.
@Beanstalk Please test this on Linux (NVIDIA and AMD RADV), Windows NVIDIA and the Steam Deck: a game folder prepared by nightly-622, then updated to this branch, which is a real translator change. Expect the log to say
another translator's ... carried, a preparation of minutes rather than a full compile, the right picture in play, and no crash. Please also report RAM and the time to the first frame against a fresh cache where the run can.Beanstalk test farm · 🔄 testing (0 of 4 reports so far)
Commit
73a55f5· approved by madebyjordan (reviewed) · dashboard⚠️ Note: The farm cannot seed nightly-622 caches or perform the requested update, so it cannot verify the carry log, preparation time, or carried-cache costs against a fresh cache.
⚠️ Note: Cold and warm driver-cache scenarios run only on Linux; Windows gets the ordinary startup and play comparison. RAM is measured during gameplay, not peak preparation memory.
Started at 09:30 UTC. Run 2: re-planned by madebyjordan.
Estimate: done in about 1 h 15 min, from the queue and the testers online now; some jobs can't start yet.
linux+nvidialinux+radvwindows+nvidiasteamdeckWhat was tested
What will be tested · AI plan (
gpt-6.1-terra)The requested update from a nightly-622-prepared folder cannot be reproduced, so this alternative compares ordinary startup and play against main on Linux NVIDIA, Linux RADV, Windows NVIDIA, and Steam Deck. Linux runs also compare starts with cold and warm driver caches; these are not fresh game caches. The plan measures startup time and gameplay RAM, and fails on crashes, substantial startup or frame-time regressions, or a changed gameplay picture. It takes about 30–35 minutes per Linux tester and about 10–12 minutes per Windows tester, excluding builds.
kokiri-start, then teleport to Hyrule Field, take the picture field to compare with main, measure field for 20 s (after 5 s warm-up); 1 run on each side.kokiri-start(each start with an empty driver shader cache, Linux only for now), then teleport to Kokiri Forest, take the picture forest-cold to compare with main, measure forest for 20 s (after 5 s warm-up); 1 run on each side.kokiri-start(each side's driver shader cache kept across its starts, filled first by an unmeasured start, Linux only for now), then teleport to Kokiri Forest, take the picture forest-warm to compare with main, measure forest for 20 s (after 5 s warm-up); 1 run on each side.The Test Farm can't seed an older build's caches, so it can't test the carry itself. I've asked it for its alternative, an ordinary start-up and play comparison against main on Linux, NVIDIA and the Steam Deck. The carry on Linux and NVIDIA is now a separate by-hand item in Still to test.
@Beanstalk test it anyway
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.