You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and to send this info to Tensorboard. In the Tensorboard there is only few information available, like total memory consumption graph (without no detalization like in listing above), and for this training it is like 2 GB GPU memory used. And it cannot see, which operations take so much memory.
Why pprof is not seeing any internal memory usage and shows little kB memory used? How can I obtain detailed memory profiling for neural tangents like in pprof?
Tnank you!
The text was updated successfully, but these errors were encountered:
I'm admittedly not familiar with pprof. To double check, is the issue only present when you use Neural Tangents, or when profiling other codebases as well? If the latter, it may be better to ask in https://github.com/google/pprof/issues or https://github.com/google/jax.
Good day!
I'm trying to use memory profiler
pprof
as described here:https://jax.readthedocs.io/en/latest/device_memory_profiling.html
I'm trying to train Myrtle NTK infinite network on CIFAR with architecture taken from Colab notebook:
https://colab.research.google.com/github/google/neural-tangents/blob/main/notebooks/myrtle_kernel_with_neural_tangents.ipynb
The problem is that when I check output of the profiler, it's memory consumption looks very small:
The only way I've managed to obtain some data is by using
and to send this info to Tensorboard. In the Tensorboard there is only few information available, like total memory consumption graph (without no detalization like in listing above), and for this training it is like 2 GB GPU memory used. And it cannot see, which operations take so much memory.
Why
pprof
is not seeing any internal memory usage and shows little kB memory used? How can I obtain detailed memory profiling for neural tangents like inpprof
?Tnank you!
The text was updated successfully, but these errors were encountered: