Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update device_memory_profiling.md #23964

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update device_memory_profiling.md #23964

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/device_memory_profiling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ jax.profiler.save_device_memory_profile("memory.prof")
If we first run the program above and then execute

```shell
pprof --web memory.prof
pprof --http=: memory.prof
```

`pprof` opens a web browser containing the following visualization of the device
Expand Down Expand Up @@ -128,7 +128,7 @@ If we simply visualize the device memory profile at the end of execution
`anotherfunc` accumulates more device memory allocations:

```shell
pprof --web memory9.prof
pprof --http=: memory9.prof
```

![Device memory profile at end of execution](_static/device_memory_profile_leak1.svg)
Expand All @@ -142,7 +142,7 @@ across loop iterations, we can identify why the memory usage of the
program increases over time:

```shell
pprof --web --diff_base memory1.prof memory9.prof
pprof --http=: --diff_base memory1.prof memory9.prof
```

![Device memory profile at end of execution](_static/device_memory_profile_leak2.svg)
Expand Down