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
tensorboard profiler will only find profile information if pointed to the exact subdirectory where log is written ( ie single run)
therefore code needs to be changed to %tensorboard --logdir=$logs from %tensorboard --logdir=logs (to include the timestamp ie logs/ )
when this is done, profile tab is visible (and can select profile in the dropdown inactive/...
profile information is now visible, but on the overview page it warns
No step marker observed and hence the step time is unknown. This may happen if (1) training steps are not instrumented (e.g., if you are not using Keras) or (2) the profiling duration is shorter than the step time. For (1), you need to add step instrumentation; for (2), you may try to profile longer.
all timings are reported as zero on overview page
The text was updated successfully, but these errors were encountered:
This bug is caused by tensorflow.python.profiler.internal._pywrap_profiler.ProfilerSession().export_to_tb() putting profiler data in the wrong place. This bug was introduced into tensorflow/tensorflow/python/profiler/internal/profiler_wrapper.cc a long time ago (around v2.12 release). The invocation happens in tensorflow/python/profiler/profiler_v2.py around line 150 in tensorflow v2.15.1. Please fix this so that profiler starts working again.
Environment information (required)
colab
/~https://github.com/tensorflow/tensorboard/blob/master/docs/tensorboard_profiling_keras.ipynb
Issue description
tensorboard profiler will only find profile information if pointed to the exact subdirectory where log is written ( ie single run)
therefore code needs to be changed to
%tensorboard --logdir=$logs
from%tensorboard --logdir=logs
(to include the timestamp ie logs/ )when this is done, profile tab is visible (and can select profile in the dropdown
inactive
/...profile information is now visible, but on the overview page it warns
all timings are reported as zero on overview page
The text was updated successfully, but these errors were encountered: