Document applied read cancellation evidence and final world recording
This commit is contained in:
@@ -47,3 +47,12 @@ The [sanitized Linux CI result](../benchmarks/culling-empty-2026-10-04/linux-app
|
||||
includes its source/workflow provenance and independently checks live registration
|
||||
and the applied shortcut. CPU timings can include JIT folding of this empty loop;
|
||||
they are not per-check costs or estimates of game speed.
|
||||
|
||||
The final candidate JAR (`c506982631880604513de8ef85e3b4461fbb898702e60b4a6f74ca3b3d4a687f`)
|
||||
then recorded 579 frame intervals and 2,408 integrated-server tick durations over
|
||||
120 seconds, with zero excluded frames and matching CSV counts/means. Its actual
|
||||
frame report retained custom graphics, render/simulation distances 12/12, DH radius
|
||||
128 at MEDIUM/MEDIUM quality, two workers at runtime ratio 0.5, compact headers,
|
||||
and both the culling shortcut and scoped terrain-read fix enabled. No captured
|
||||
visual setting changed. This verifies integration; it is not a repeated hardware
|
||||
performance comparison.
|
||||
|
||||
@@ -34,3 +34,17 @@ reads with an interrupt already set, cancelled
|
||||
futures, exceptional completion identity, and recognition by DH's shutdown
|
||||
exception utility. The private fixture does not enter release packs. This is a
|
||||
correctness check, not an FPS, throughput or Mac shutdown benchmark.
|
||||
|
||||
The [sanitized Linux CI result](../benchmarks/terrain-read-2026-10-04/linux-applied-hooks.json)
|
||||
includes source/workflow provenance and the original mod checksum. The CI JAR
|
||||
matches the local candidate byte-for-byte. Windows and hosted Apple Silicon
|
||||
macOS 26 compile the fixture and pass the portable build/metrics checks; applied
|
||||
read interruption is exercised on Linux, not a live macOS game.
|
||||
|
||||
The exact candidate also completed a 120-second local world recording, saved,
|
||||
and reloaded that world in the same client. After the first save, thread inspection
|
||||
found no remaining DH generation workers and no background workers blocked on a
|
||||
future. After reload, two generation workers existed and neither was waiting in
|
||||
blending metadata; no background metadata-scan wait was present at that snapshot.
|
||||
This is one software-rendered lifecycle observation, not proof that every
|
||||
shutdown race, world or platform is covered.
|
||||
|
||||
Reference in New Issue
Block a user