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.

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

Profiler fails to capture GPU / job #3256

Open
OverLordGoldDragon opened this issue Feb 15, 2020 · 3 comments
Open

Profiler fails to capture GPU / job #3256

OverLordGoldDragon opened this issue Feb 15, 2020 · 3 comments

Comments

@OverLordGoldDragon
Copy link

OverLordGoldDragon commented Feb 15, 2020

Following the workaround here, I tried profiling via both tensorflow.keras.callbacks.TensorBoard and with tensorflow.python.eager.profiler.Profiler - but the resulting trace only displays /host:CPU (img below); I understand there should also be /job and /gpu sections, which is also evident from the significant gap between model.train_on_batch() iterations.

Any fixes/workarounds?


Note: I'm also getting the following in Anaconda Powershell Prompt:

W0215 15:19:47.154924 14124 core_plugin.py:215] Unable to get first event timestamp for run .: 
No event timestamp could be found

image


Note 2: TF 2.0.0 (stable) captures GPU, but I'm still not seeing /job: (also I still had to use the JSON workaround; TensorBoard PROFILE was empty)

@ProNoobLi
Copy link

Check your terminal. Does it say anything about libcupti?? If so, you miss it, tensorboard cannot capture gpu trace.

@mathpluscode
Copy link

Check tensorflow/tensorflow#35860, if you have errors about libcupti

@tongda
Copy link

tongda commented Mar 2, 2020

I have same issue, even after fix the libcupti problem.

My saved_model is exported by tf version 2.0.0, and tensorboard is 2.1.0. Since my profile is captured by tensorflow-serving, the tensorflow-serving version is 2.1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants