-
Notifications
You must be signed in to change notification settings - Fork 240
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
[DOC] Add in docs about memory debugging [skip ci] #10104
Conversation
Signed-off-by: Robert (Bobby) Evans <[email protected]>
build |
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.
Looks good. Just a few nits.
docs/dev/README.md
Outdated
@@ -241,6 +242,11 @@ port 5005. | |||
|
|||
You can also use [Compute Sanitizer](compute_sanitizer.md) to debug CUDA memory errors. | |||
|
|||
### Memory Debugging | |||
Java's garbage collector does not play nicely with CUDA memory allocations or with off heap memory. | |||
There are a number of tools that we have developed that can help do |
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.
There are a number of tools that we have developed that can help do | |
There are a number of tools that we have developed that can help to |
docs/dev/mem_debug.md
Outdated
close to the actual allocator as possible. But just be careful. | ||
|
||
Also know that the address here should correspond to the address in the leak debugging if and only | ||
if it was a DeviceMemoryBuffer that was allocated. In this case, where it is a `cudf::column` the |
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.
if it was a DeviceMemoryBuffer that was allocated. In this case, where it is a `cudf::column` the | |
if it was a `DeviceMemoryBuffer` that was allocated. In this case, where it is a `cudf::column` the |
docs/dev/mem_debug.md
Outdated
|
||
We also don't have a way to | ||
[log exactly what was spilled](https://github.com/NVIDIA/spark-rapids/issues/10103) | ||
and what was read back it. We can probably guess that this is happening from other logs, but it |
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.
and what was read back it. We can probably guess that this is happening from other logs, but it | |
and what was read back. We can probably guess that this is happening from other logs, but it |
@jbrennan333 please take another look |
build |
This fixes #9987
any feedback is appreciated.