mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-18 04:49:57 -04:00
Say in perf_census.h that the census charge assumes the walk held the replay up, and say in the ini when the walk line is left out.
The review of c05e6528 found two texts that said more than the code or the logs do. - runtime/perf_census.h stated as fact that the replaying thread's write-watch queries wait for the walk's address-space lock. The verifier's caveat stands: in the session the charge is based on, the presenting thread's 600-frame memory report (vk_memory.c vk_mem_census) ran at the same frames as the walks, and the log cannot tell which of the two held the 63 replay hitches up. The comment now says they sat beside such a walk, that the charge assumes the walk held them up, and that a play-test with mem_census = 0 checks it. - nx2navi.ini.example's mem_census paragraph said the "mem: process" line comes every 600 frames. Since c05e6528, vk_memory.c heap_log leaves its own walk out at a frame where perf.c census_check walked (every 3600th frame, and a commit census on growth that falls on a 600th), and the commit census lines stand in for it; the paragraph says so. Comment and settings text only. perf.c compiles with the dev flags; census_charge_check passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -1007,10 +1007,11 @@
|
||||
# fps or more with Link on the floor. Each pass slows the game for its few seconds. 0 is off.
|
||||
# floor_watch = 0
|
||||
# 1: with trace = perf, walks of the process's address space count its private and write-combined memory every 600
|
||||
# frames (the "mem: process" line) and where its committed memory lies every 3600 frames, and when the process's own
|
||||
# commit (without the video memory Windows charges to it) rose 1 GiB over the highest it was, at most once a minute
|
||||
# (the "commit census" lines). Each walk holds the address-space lock for 100-260 ms and delays the next frame by as
|
||||
# much, so they are off unless asked for: leave it off in a run whose smoothness is judged.
|
||||
# frames (the "mem: process" line; at every 3600th frame, and any other where the commit census walks, that walk
|
||||
# stands in for it) and where its committed memory lies every 3600 frames, and when the process's own commit (without
|
||||
# the video memory Windows charges to it) rose 1 GiB over the highest it was, at most once a minute (the "commit
|
||||
# census" lines). Each walk holds the address-space lock for 100-260 ms and delays the next frame by as much, so they
|
||||
# are off unless asked for: leave it off in a run whose smoothness is judged.
|
||||
# mem_census = 0
|
||||
# 1: with trace = perf, the process's handles counted by kind (events, sections, threads, files...) at the 600-frame
|
||||
# report when their number grew by 16 or more since the last count (the "mem: handles" line). It reads the system's
|
||||
|
||||
Reference in New Issue
Block a user