tensorflow / tensorflow/tensorboard

Profiler fails to capture GPU / job

Open
#3,256 3 comments 0 reactions 1 assignee View on GitHub

@davidsoergel is already working on this.

Since Feb 17, 2020.

core:frontend plugin:profile stat:awaiting tensorflower type:bug
Dominant language
TypeScript
Stars
7.2k
Forks
1.7k
Avg merge
4d 22h
Merged PRs (30d)
1

Description

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)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.