Skip to content

Conversation

@zou3519
Copy link
Contributor

@zou3519 zou3519 commented Apr 18, 2018

Picks up from #5216

cc @apaszke @ssnl

@zou3519 zou3519 merged commit 2d09799 into pytorch:master Apr 18, 2018
@zou3519 zou3519 deleted the docs-fixes3 branch April 18, 2018 21:26
weiyangfb pushed a commit to weiyangfb/pytorch that referenced this pull request Apr 18, 2018
not show correct timings: the reported CPU time reports the amount of time
used to launch the kernels but does not include the time the kernel
spent executing on a GPU unless the operation does a synchronize.
In this case, the CUDA-mode autograd profiler may be helpful.

This comment was marked as off-topic.

spent executing on a GPU unless the operation does a synchronize.
In this case, the CUDA-mode autograd profiler may be helpful.

.. warning::

This comment was marked as off-topic.

Of course the reality is much more complicated and your script might not be
in one of those two extremes depending on the part of the model you're
evaluating. If the profiler outputs don't help, you could try looking at
the result of :func:`torch.autograd.profiler.emit_nvtx()` with ``nvprof``.

This comment was marked as off-topic.

Jorghi12 pushed a commit to wsttiger/pytorch that referenced this pull request May 10, 2018
weiyangfb pushed a commit to weiyangfb/pytorch that referenced this pull request Jun 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants