mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-18 15:19:58 -04:00
Merge storage write-backs of up to 16 MiB instead of copying them back whole
Ranges just above the old 4 MiB limit were copied back over PCIe at the end of every submission. A larger snapshot pool keeps the extra merges from allocating on the replay thread. NX2NAVI_WB_MERGE_MAX sets the limit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HtayeqEG2x5woYzWuEQBGV
This commit is contained in:
@@ -483,3 +483,7 @@
|
||||
# the next refresh and show their stand-in until then. Lower spreads streaming over more frames (smaller hitches, a
|
||||
# frame or two of pop-in); higher loads sooner.
|
||||
# pool_create_budget = 16
|
||||
# Written storage-buffer ranges up to this size in MiB (1 to 16) go back to game memory as a merge: copied within video
|
||||
# memory and only the words that changed written over PCIe. Larger ones are copied back whole at the end of every
|
||||
# submission. Raising it from 4 to 16 took a 5.5 MiB range off the plain copies (about 46 MiB a frame in the field).
|
||||
# wb_merge_max = 16
|
||||
|
||||
Reference in New Issue
Block a user