Compile forward function in baseline backward benchmarks #3300
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the backward benchmark for
torch.compile
are compiling theoutput.backward(grads)
function.This PR changes the benchmarks to compile the corresponding forward function.
The benchmarking results are at: http://nv/emR
Earlier, I was observing similar performance for eager and torchcompile for these backward benchmarks.
The files
*_bwd.py
are changed in this PR. We observe improved performance with torchcompile as compared to eager now. Note, that, the results from weekly will have more data points than the CI pipeline.Question:
test_gelu_bwd_reduction.py
reduces the gradient of the input. I am not sure what would be the right function to compile here :/Thanks to @xwang233 for help with running the CI pipeline!