-
-
Notifications
You must be signed in to change notification settings - Fork 719
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
Add cuDF spilling statistics to RMM/GPU memory plot #8148
Merged
hendrikmakait
merged 26 commits into
dask:main
from
charlesbluca:cudf-spilling-dashboard
Dec 18, 2023
Merged
Changes from all commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
7fc10ce
Initial exposure of cuDF logging information
charlesbluca 04137ef
Initial plot of GPU to CPU nbytes
charlesbluca d38de06
Refactor RMM plot to include spilled memory
charlesbluca eeddf1e
Fix memory limit on x axis
charlesbluca 043835c
Remove unused dashboard plot
charlesbluca 0ac3344
Allow MemoryColor colors to be overridden
charlesbluca 698be13
Merge remote-tracking branch 'origin/main' into cudf-spilling-dashboard
charlesbluca bb49135
Linting
charlesbluca 628fe39
Merge remote-tracking branch 'origin/main' into cudf-spilling-dashboard
charlesbluca 50e626a
Add cudf diagnostics test
charlesbluca 98e283e
Merge remote-tracking branch 'origin/main' into cudf-spilling-dashboard
charlesbluca 008cca8
Merge remote-tracking branch 'origin/main' into cudf-spilling-dashboard
charlesbluca 082ddef
Resolve bokeh test failures
charlesbluca 87f8020
Merge remote-tracking branch 'origin/main' into cudf-spilling-dashboard
charlesbluca 4453b8b
Merge remote-tracking branch 'origin/main' into cudf-spilling-dashboard
charlesbluca b60173d
Make cudf spilling monitoring optional and disabled by default
charlesbluca 7426548
Merge remote-tracking branch 'origin/main' into cudf-spilling-dashboard
charlesbluca 1890136
Modify cudf spilling test
charlesbluca 5eafddc
Test cuDF spill tests in separate process
charlesbluca 21e106b
Remove global cuDF spilling settings from build.sh
charlesbluca 3cc4b94
cuDF metrics test is flaky
charlesbluca 98dbfc7
Merge remote-tracking branch 'origin/main' into cudf-spilling-dashboard
charlesbluca a5fce3c
Merge remote-tracking branch 'upstream/main' into cudf-spilling-dashb…
charlesbluca b2fdfc6
Shouldn't need dask-cuda worker for test
charlesbluca f96b8a4
Merge remote-tracking branch 'upstream/main' into pr/charlesbluca/8148
charlesbluca 936f0f6
Merge remote-tracking branch 'upstream/main' into cudf-spilling-dashb…
charlesbluca 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
Oops, something went wrong.
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.
Assuming these variables don't come up when deciding GPU to CPU spilling and can probably be ignored in that case, not sure what the best way to do this is? First thought was to just use a context manager to override config when initializing the
MemoryColor
, not sure if that will screw up AMM behavior down the line