Skip to content

Setting to use torch dynamo compiling path in eager #2045

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

Closed
wants to merge 1 commit into from

Conversation

IvanKobzarev
Copy link
Contributor

Summary:
1/ Refactoring to use is_torchdynamo_compiling() from torchrec.pt2.checks instead of code duplication

2/ We have alternative path of logic is_torchdynamo_compiling(). Our tests are not testing it without compilation, so it is error prone to not catch some shape mismatch or etc. =>
We need a tool how to cover it with eager tests without compilation. =>
Introducing global setting to force using is_torchdynamo_compiling() path for eager for test coverage and debug.

Enabling this path for test_pt2_multiprocess, that first eager iteration will be done on is_torchdynamo_compiling path.

Differential Revision: D57860075

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label May 28, 2024
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D57860075

IvanKobzarev pushed a commit to IvanKobzarev/torchrec that referenced this pull request May 28, 2024
Summary:

1/ Refactoring to use is_torchdynamo_compiling() from torchrec.pt2.checks instead of code duplication

2/ We have alternative path of logic is_torchdynamo_compiling(). Our tests are not testing it without compilation, so it is error prone to not catch some shape mismatch or etc. =>
We need a tool how to cover it with eager tests without compilation. => 
Introducing global setting to force using is_torchdynamo_compiling() path for eager for test coverage and debug.


Enabling this path for test_pt2_multiprocess, that first eager iteration will be done on is_torchdynamo_compiling path.

Differential Revision: D57860075
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D57860075

IvanKobzarev pushed a commit to IvanKobzarev/torchrec that referenced this pull request May 28, 2024
Summary:

1/ Refactoring to use is_torchdynamo_compiling() from torchrec.pt2.checks instead of code duplication

2/ We have alternative path of logic is_torchdynamo_compiling(). Our tests are not testing it without compilation, so it is error prone to not catch some shape mismatch or etc. =>
We need a tool how to cover it with eager tests without compilation. => 
Introducing global setting to force using is_torchdynamo_compiling() path for eager for test coverage and debug.


Enabling this path for test_pt2_multiprocess, that first eager iteration will be done on is_torchdynamo_compiling path.

Differential Revision: D57860075
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D57860075

IvanKobzarev pushed a commit to IvanKobzarev/torchrec that referenced this pull request May 28, 2024
Summary:

1/ Refactoring to use is_torchdynamo_compiling() from torchrec.pt2.checks instead of code duplication

2/ We have alternative path of logic is_torchdynamo_compiling(). Our tests are not testing it without compilation, so it is error prone to not catch some shape mismatch or etc. =>
We need a tool how to cover it with eager tests without compilation. => 
Introducing global setting to force using is_torchdynamo_compiling() path for eager for test coverage and debug.


Enabling this path for test_pt2_multiprocess, that first eager iteration will be done on is_torchdynamo_compiling path.

Differential Revision: D57860075
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D57860075

Summary:
Pull Request resolved: pytorch#2045

1/ Refactoring to use is_torchdynamo_compiling() from torchrec.pt2.checks instead of code duplication

2/ We have alternative path of logic is_torchdynamo_compiling(). Our tests are not testing it without compilation, so it is error prone to not catch some shape mismatch or etc. =>
We need a tool how to cover it with eager tests without compilation. =>
Introducing global setting to force using is_torchdynamo_compiling() path for eager for test coverage and debug.

Enabling this path for test_pt2_multiprocess, that first eager iteration will be done on is_torchdynamo_compiling path.

Reviewed By: PaulZhang12, gnahzg

Differential Revision: D57860075
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D57860075

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants