-
Notifications
You must be signed in to change notification settings - Fork 10.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Numa #1556
Merged
Merged
Numa #1556
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
6fc5f17
detect NUMA systems and pin work threads to nodes (linux)
zrm 0d23f8c
disable mmap prefetch/readahead for NUMA systems
zrm 9d058c2
avoid sending finalize op to thread pool if it does nothing
zrm 2c1b5ae
silence robot
zrm 8502d51
fix args
zrm bf83dcb
make --numa a param
zrm b71dfe6
recommendation that n_nodes evenly divide n_threads did not warrant s…
zrm adaad10
lower synchronization overhead
zrm c31d51d
statically allocate
zrm 2f5bb46
move numa state to g_state
zrm 4b94582
add description for --numa
zrm 90a0e65
Merge branch 'master' into HEAD
ggerganov d0e3596
ggml : minor style changes
ggerganov 67ba34e
ggml : minor style + try fix sanitizer build
ggerganov 8f98035
Merge branch 'master' into HEAD
ggerganov 0fe4b00
llama : allow to initialize backend with NUMA support
ggerganov 875a1e1
llama : avoid ggml include in llama-util.h
ggerganov 4a555b4
ggml : style / formatting
ggerganov 81a40e9
ggml : fix handling of ops with n_threads > n_tasks > 1
ggerganov 9aec2b7
server : utilize numa parameter
ggerganov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, sorry for this comment. I have limit experiences of NUMA node and processes placement optimization to utilize NUMA node's memory access locality. But I am sure such locality helps to improve end to end latencies.
I want to understand what the optimization exactly made by this PR.
which part does this job ?
when I/O compute overlap , disabling prefetch surely gave bad performance in latencies and throughput. But why is this related to NUMA nodes ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we use mmap to implement pin memory allocation for streams/weights inputs ?
I am a little confused when you talk about page (paged memory) and mmap (which maps memory from device to DRAM and ready to be read by DMA)
Thank you if you can help to clarify my concerns. Happy to learn your solutions.