Skip to content

OSS TorchRec Internal MPZCH modules (#3017) #3089

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

lizhouyu
Copy link
Contributor

Summary:

Major changes

  • Copy the following files from fb to corresponding location in the torchrec repository
    • fb/distributed/hash_mc_embedding.py → torchrec/distributed/hash_mc_embedding.py
    • fb/modules/hash_mc_evictions.py → torchrec/modules/hash_mc_evictions.py
    • fb/modules/hash_mc_metrics.py → torchrec/modules/hash_mc_metrics.py
    • fb/modules/hash_mc_modules.py → torchrec/modules/hash_mc_modules.py
    • fb/modules/tests/test_hash_mc_evictions.py → torchrec/modules/tests/test_hash_mc_evictions.py
    • fb/modules/tests/test_hash_mc_modules.py → torchrec/modules/tests/test_hash_mc_modules.py
  • Create a test_hash_zch_mc.py file in torchrec/distributed/tests folder following the test_quant_mc_embedding.py in torchrec/fb/distributed/tests.
    • trimmed quantization and inference codes, and only kept the training part.
    • rewire the related packages from torchrec.fb to torchrec
  • Update BUCK files in related folders
  • Update the affected repos to use torchrec modules instead of the modules in torchrec.fb
  • Update /modules/hash_mc_metrics.py
    • Replace the tensorboard module with a local file logger in hash_mc_metrics.py module
  • Update the license declaration headers for the four OSS files

ToDos after landing this Diff

  • Clean the duplicated hash_mc_modules.py file in the fb folder for safe landing.

Differential Revision: D76476676

@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 Jun 12, 2025
@facebook-github-bot
Copy link
Contributor

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

Summary:
Pull Request resolved: pytorch#3089

Pull Request resolved: pytorch#3017

### Major changes
- Copy the following files from `fb` to corresponding location in the `torchrec` repository
  - `fb/distributed/hash_mc_embedding.py → torchrec/distributed/hash_mc_embedding.py`
  - `fb/modules/hash_mc_evictions.py → torchrec/modules/hash_mc_evictions.py`
  - `fb/modules/hash_mc_metrics.py → torchrec/modules/hash_mc_metrics.py`
  - `fb/modules/hash_mc_modules.py → torchrec/modules/hash_mc_modules.py`
  - `fb/modules/tests/test_hash_mc_evictions.py → torchrec/modules/tests/test_hash_mc_evictions.py`
  - `fb/modules/tests/test_hash_mc_modules.py → torchrec/modules/tests/test_hash_mc_modules.py`
- Create a `test_hash_zch_mc.py` file in `torchrec/distributed/tests` folder following the `test_quant_mc_embedding.py` in `torchrec/fb/distributed/tests`.
  - trimmed quantization and inference codes, and only kept the training part.
  - rewire the related packages from `torchrec.fb` to `torchrec`
- Update `BUCK` files in related folders
- Update the affected repos to use `torchrec` modules instead of the modules in `torchrec.fb`
- Update `/modules/hash_mc_metrics.py`
  - Replace the tensorboard module with a local file logger in `hash_mc_metrics.py` module
- Update the license declaration headers for the four OSS files

### ToDos after landing this Diff
- Clean the duplicated `hash_mc_modules.py` file in the `fb` folder for safe landing.

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

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

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