docs(tested): the cloth gate with every lifted chunk at -O2, against -O1, six interleaved pairs (#1485) #1630
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!1630
Loading…
Reference in a new issue
No description provided.
Delete branch "enum/Longshot:tested/cloth-o2-runs"
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?
Type: docs · Risk: low · Tested on: Windows 11, RTX 4070 · Needs: none
TL;DR
Twelve measured runs for the tested configurations catalogue: the game with all of its translated code compiled at
-O2, against the usual-O1, on an RTX 4070 with a Ryzen 9 7900X on Windows. In six interleaved timed pairs the-O2build was 10.3% faster in the Market and 6.9% faster in Hyrule Field, and the same within the spread at the Zora's Domain arrival. Records only: no code changes.Breakdown
-O2, and readers of the tested configurations catalogue.-O2/-O3numbers from Linux only, where they showed no fps change.docs/tested/, one a run.tests/test_tested_configurations.py(the record format).Why
Item 4 of the wiki's performance page proposes the cloth and physics code at
-O2, as an estimate; its "ruled out" list has "all game code at-O3on its own: no fps" from a Linux RTX 3090. These runs measure the Windows side for #1485 (Zora's Domain slows down near King Zora). See #1485, #1493.What changed
Twelve run records in the tested configurations' format, one file a run, six for each side. Nothing else changes.
docs/tested/2026-11-18-cloth60-o2-enum-a1.mdto-a6.md(the-O1side: what players run) and-b1.mdto-b6.md(every lifted chunk at-O2,LONGSHOT_CHUNK_OPT=all, withHOS_FPS_CLOTH_60=1from #1628).The build the records name,
perf/cloth-above-60 @ 8aadf550, is #1628's code before its documentation and switch-table row were added (#1628's0663d20fhas the same code). The gate's own runs (-O1, the gate on against off) are on #1628 and show no fps change, so the difference here is the compiler setting.Measurements
Verdict: all lifted chunks at
-O2: +10.3% in the Market and +6.9% in Hyrule Field (5 of 6 runs above the best-O1run at both), within the spread at the Zora's Domain arrival.Hardware: Windows 11 Pro (26300), RTX 4070 12 GB (NVIDIA 616.56), Ryzen 9 7900X, 64 GB
Scene: teleport arrivals: Market (child), Hyrule Field (adult), Zora's Domain (child); output 2560x1440 in a 1280x720 window, Quality preset Auto (tier 4, the game's own upscaler), frame generation off, cap 240
Method: one game session a run in the job queue's timing mode, each spot settled 12 s and measured over 20 s by the game's frame counter, hands off; interleaved A1 B1 ... A6 B6 after a warm-up of each; the median of six. Runs 4 to 6 record the CPU busy outside the game (1.0 to 1.8 cores, both sides).
How to reproduce:
dev_packs.py packof #1628's branch twice over one base, the second withLONGSHOT_CHUNK_OPT=all; the owner's save; the control bridge'steleportto the three destinations.Baseline: the before column is the same branch built as players build it (
-O1,HOS_FPS_CLOTH_60unset); main has no-O2build to compare.Flags and settings
None.
Testing
Tested:
python -I -B tests/test_tested_configurations.py: the record checks pass; its one failure (test_cli_ascii_pipe_emits_the_arrow_containing_source_as_utf8, a Windows line-ending case) fails on main too. The runs themselves are what the records describe.Not tested: other PCs; the King Zora stairs as timed runs (the bridge can't walk there; hand readings are on the wiki, marked as such).
Must be tested:
Risks
What could break: nothing; records only.
Turning it off: revert the commit.
Compatibility: Nothing changes.
Issues
See #1485
Checklist
Everyone
type(scope): description) of the status line's type.can't be run by hand is in Testing's Not testable by hand, with why.
in Risks.
main.python -I -B tests/run_all.pypasses (any failure that also fails onmainis named). (Docs only: the check that reads these files,tests/test_tested_configurations.py, was run; its one failure also fails on main.)third_party/untouched (a new folder with aPROVENANCE.mdinstead).When it applies
Assisted-by:/Co-Authored-By:trailers.docs/tested/for each new measured run (format indocs/tested-configurations.md).🤖 Generated with Claude Code
WIP: docs(tested): the cloth gate with every lifted chunk at -O2, against -O1, six interleaved pairs (#1485)to docs(tested): the cloth gate with every lifted chunk at -O2, against -O1, six interleaved pairs (#1485)View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.