Repository navigation
Conversation
Every thread the threadCreate wrapper starts registers with the core it woke up on; main registers at the first report. Each menu and stream summary is followed by a `threads:` line: the process's core mask, each core's load from the title's threads, and for each thread its start core, core mask, priority and share of each core. The spawners of the video, audio and input threads name them in the registry. This is the probe before any thread is placed on another core. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Collaborator
Author
|
Closing without merging. The probe answered its question: the app's threads already run on cores 0 to 2, nearly idle, and the system's core 3 is the busy one (73 to 90 percent, serving socket calls). Nothing here ships. The finding is recorded in docs/improvements.md. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The clock sweep (docs/NOTES.md, 2026-11-02) found latency CPU-bound at stock clocks. libnx's newlib glue creates every pthread on the process's default core, so the title's threads may all share core 0 while cores 1 and 2 idle. This PR is the probe that answers it before any thread is moved.
pf-nx-sys: a thread registry fed by thethreadCreatewrapper. Each thread records the core it woke up on; main registers at the first report.report()reads each live thread's core mask, priority and per-core CPU ticks (InfoType_ThreadTickCount), and the process's core mask.pf-nx-app: aThreadProbeseam (Lifecycle::thread_probe). The spawners of the video, audio and input threads name them, and athreads:line follows each 10 s menu and stream summary.Next, once a handheld log shows the placement: give the threads explicit cores (0–2, core 3 untouched) and compare stats at stock clocks against the clock-sweep table.