Repository navigation
Numa detection 1.0 - #1148
Open
Dym03 wants to merge 2 commits into
Open
Numa detection 1.0#1148Dym03 wants to merge 2 commits into
Dym03 wants to merge 2 commits into
Conversation
Dym03
force-pushed
the
numa_detection_1.0
branch
2 times, most recently
from
October 22, 2026 10:46
ef852ac to
e49b666
Compare
Dym03
force-pushed
the
numa_detection_1.0
branch
from
October 22, 2026 11:03
e49b666 to
1527b98
Compare
This branch has not been deployed
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.
This PR introduces basic NUMA detection using information scraped from the filesystem without using any external dependencies. Not sure about the compatibility with non Nvidia devices, as I had no chance testing it on such devices.
In a case of non compatibility, external library hwlocality could be used, and this library should support it.
Current state:
In dashboard new screen was added showing basic information about the numa nodes detected. This could be reworked into something more sofisticated, but more about this later. Into this view user can jump either straight from the WorkerList or from the WorkerInfo screen using the "n" key.
NUMA node information was also added into the worker info command
With even more information in the json output mode
This is yet work in progress not in this PR, as I am not sure if this is what is wanted. But this is how I imagined the #474 issue's output would be.
In this PR AI was used to generate most of the code, but I have checked the code and tested the product.
I would like to know your stand on the design of the Dashboard part, and also maybe know what informations are the most usefull for someone using the NUMA nodes. From my point of view the cpu indices are the most important part.