mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-18 06:59:57 -04:00
Merge the two performance changes into the 0.7.0 release line: a signalled event wakes only its own waiters, and a thread of its own writes the log.
One conflict, the list of setting names, which keeps both sides' additions. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -621,6 +621,17 @@
|
||||
# Log kernel services that block longer than this many ms, with the service number (0: off). A stalled frame shows up as
|
||||
# time in the replay; this says whether the guest was waiting in a service, and which one.
|
||||
# svc_slow_ms = 0
|
||||
# 1: every signalled event and every thread that ends wakes all the game threads that wait for any event, as before;
|
||||
# each takes one of the game's virtual cores to find that its own event is not the one, often from a thread that was
|
||||
# working. 0 (default): only the threads that wait for that event or thread are woken. With trace = sched the
|
||||
# "sched:" line counts both ("signals woke ..., left ... asleep").
|
||||
# sync_wake_all = 0
|
||||
# 1 (default): a thread of its own writes the log lines, to the log file and the console, so a write that stalls (a
|
||||
# busy disk, a virus scanner, a console that scrolls) no longer holds the thread that logged, which is often the one
|
||||
# that draws the frame. A crash, a fatal error and the end of the game write out what is still queued first. 0: each
|
||||
# line is written by the thread that logs it, as before. Either way a "log: ... writes of the log took over 2 ms" line
|
||||
# counts the slow writes and says whose time they took.
|
||||
# log_async = 1
|
||||
# 1: the frame-time summary also splits the replay by op kind (draw, bind, transfer), which says where a stalled frame
|
||||
# went. The clock reads cost a fraction of a millisecond a frame, so it is off by default.
|
||||
# replay_time = 0
|
||||
|
||||
Reference in New Issue
Block a user