Skip to content

Conversation

@caic99
Copy link
Member

@caic99 caic99 commented May 15, 2025

This PR adds feature using torch.autocast with the accuracy of torch.bfloat16 when training on nvidia GPUs.
By adding the decorator to ModelWrapper.forward, torch downcasts the data type for tensor computing and storage. This change expects a 37% peak memory reduction compared with training under float32.

Todo:

  • Evaluate the impact on accuracy.
  • Make it configurable.

Note:

  • The element-wise operations of pytorch automatically upcast to the highest accuracy of the operands. Changes in repflow_layer.py makes the function output matches with the input if the input tensor is downcasted, even if tensors of higher accuracy like the parameters are involved.
  • For unknown reasons, the silut_forward_script function fails to keep the data type of the output tensor as bfloat16 when input tensor is of that type. Using raw silut function or using torch.compile can avoid the problem, so I believe the problem is related to torch.jit.script. So I have to manually cast the output data type to match with the input tensor.

Test results:
I trained 1 million steps on mptrj dataset, and the result shows that training under BF16 somehow affects the accuracy. This observation is consistent with other MLIP models: when training under BF16 accuracy, it might requires more training steps, and followed by fine-tuning in FP32 to keep the accuracy.

Metric BF16 FP32
Energy MAE (eV) 8.649451 × 10^-1 8.084421 × 10^-1
Energy RMSE (eV) 1.931963 × 10^0 1.765754 × 10^0
Energy MAE/Natoms (eV) 3.495069 × 10^-2 3.300770 × 10^-2
Energy RMSE/Natoms (eV) 8.879076 × 10^-2 8.778768 × 10^-2
Force MAE (eV/Å) 1.158567 × 10^-1 1.103375 × 10^-1
Force RMSE (eV/Å) 3.550471 × 10^-1 3.164068 × 10^-1
Virial MAE (eV) 1.111046 × 10^0 1.051787 × 10^0
Virial RMSE (eV) 3.856514 × 10^0 3.535781 × 10^0
Virial MAE/Natoms (eV) 4.698042 × 10^-2 4.510412 × 10^-2
Virial RMSE/Natoms (eV) 1.490477 × 10^-1 1.467897 × 10^-1

Summary by CodeRabbit

Summary by CodeRabbit

  • Bug Fixes

    • Improved consistency of tensor data types during computations to prevent potential errors and ensure reliable results.
    • Ensured output tensors maintain the same data type as inputs for consistent processing.
  • New Features

    • Enabled automatic mixed precision with bfloat16 precision on CUDA devices for enhanced performance during model execution.

Copilot AI review requested due to automatic review settings May 15, 2025 09:06
@caic99 caic99 marked this pull request as draft May 15, 2025 09:06
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR optimizes training memory usage by leveraging torch.autocast with torch.bfloat16 and ensuring tensor type consistency in various computational routines.

  • Added explicit type casting for operator outputs in utils.py and repflow_layer.py to match the input tensor data types.
  • Introduced torch.autocast on the forward method in train/wrapper.py to enable bfloat16 precision during training.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
deepmd/pt/utils/utils.py Cast the output of silut_forward_script to x.dtype to handle type mismatches.
deepmd/pt/train/wrapper.py Added torch.autocast decorator for bfloat16 operations on CUDA.
deepmd/pt/model/descriptor/repflow_layer.py Applied explicit casts on bias values and a_sw to ensure dtype consistency.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 15, 2025

📝 Walkthrough

"""

Walkthrough

The changes introduce explicit tensor data type casting in arithmetic operations within model descriptor and utility functions to ensure dtype consistency. A global flag BF16_AUTOCAST is added to control automatic mixed precision. The forward method of the ModelWrapper class is decorated to enable bfloat16 autocasting on CUDA devices conditionally based on this flag.

Changes

File(s) Change Summary
deepmd/pt/model/descriptor/repflow_layer.py Added explicit dtype casting for bias tensors in optim_angle_update and optim_edge_update functions.
deepmd/pt/train/wrapper.py Added import of BF16_AUTOCAST; decorated ModelWrapper.forward with @torch.autocast(device_type="cuda", dtype=torch.bfloat16, enabled=BF16_AUTOCAST).
deepmd/pt/utils/utils.py Modified SiLUTFunction.forward to cast output tensor to the input's dtype before returning.
deepmd/pt/utils/env.py Added global boolean constant BF16_AUTOCAST initialized to False and included it in __all__ exports.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant ModelWrapper
    participant CUDA
    User->>ModelWrapper: Call forward(input)
    activate ModelWrapper
    ModelWrapper->>CUDA: Enable autocast (bfloat16) if BF16_AUTOCAST=True
    ModelWrapper-->>User: Return output (with AMP if enabled)
    deactivate ModelWrapper
Loading

Suggested reviewers

  • iProzd
    """

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9025d0b and 0a770e4.

📒 Files selected for processing (2)
  • deepmd/pt/train/wrapper.py (2 hunks)
  • deepmd/pt/utils/env.py (2 hunks)
✅ Files skipped from review due to trivial changes (1)
  • deepmd/pt/utils/env.py
🚧 Files skipped from review as they are similar to previous changes (1)
  • deepmd/pt/train/wrapper.py
⏰ Context from checks skipped due to timeout of 90000ms (30)
  • GitHub Check: Test Python (6, 3.12)
  • GitHub Check: Test Python (6, 3.9)
  • GitHub Check: Test Python (5, 3.12)
  • GitHub Check: Test Python (5, 3.9)
  • GitHub Check: Test Python (4, 3.12)
  • GitHub Check: Test Python (4, 3.9)
  • GitHub Check: Test Python (3, 3.12)
  • GitHub Check: Test Python (3, 3.9)
  • GitHub Check: Test Python (2, 3.12)
  • GitHub Check: Test Python (2, 3.9)
  • GitHub Check: Build wheels for cp310-manylinux_aarch64
  • GitHub Check: Build wheels for cp311-win_amd64
  • GitHub Check: Test Python (1, 3.12)
  • GitHub Check: Build wheels for cp311-macosx_arm64
  • GitHub Check: Test Python (1, 3.9)
  • GitHub Check: Build wheels for cp311-macosx_x86_64
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Build C library (2.14, >=2.5.0rc0,<2.15, libdeepmd_c_cu11.tar.gz)
  • GitHub Check: Build C library (2.18, libdeepmd_c.tar.gz)
  • GitHub Check: Build C++ (clang, clang)
  • GitHub Check: Test C++ (false)
  • GitHub Check: Build C++ (rocm, rocm)
  • GitHub Check: Test C++ (true)
  • GitHub Check: Build C++ (cuda120, cuda)
  • GitHub Check: Build C++ (cuda, cuda)
  • GitHub Check: Build C++ (cpu, cpu)
  • GitHub Check: Analyze (python)
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Analyze (c-cpp)
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 43e0288 and babd11c.

📒 Files selected for processing (3)
  • deepmd/pt/model/descriptor/repflow_layer.py (3 hunks)
  • deepmd/pt/train/wrapper.py (1 hunks)
  • deepmd/pt/utils/utils.py (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (30)
  • GitHub Check: Test Python (6, 3.12)
  • GitHub Check: Test Python (6, 3.9)
  • GitHub Check: Test Python (5, 3.12)
  • GitHub Check: Test Python (5, 3.9)
  • GitHub Check: Test Python (4, 3.12)
  • GitHub Check: Build wheels for cp310-manylinux_aarch64
  • GitHub Check: Test Python (4, 3.9)
  • GitHub Check: Build wheels for cp311-win_amd64
  • GitHub Check: Test Python (3, 3.12)
  • GitHub Check: Build wheels for cp311-macosx_arm64
  • GitHub Check: Test Python (3, 3.9)
  • GitHub Check: Build C++ (clang, clang)
  • GitHub Check: Build wheels for cp311-macosx_x86_64
  • GitHub Check: Build C++ (rocm, rocm)
  • GitHub Check: Test Python (2, 3.12)
  • GitHub Check: Test Python (2, 3.9)
  • GitHub Check: Build C++ (cuda120, cuda)
  • GitHub Check: Analyze (python)
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Test C++ (false)
  • GitHub Check: Test Python (1, 3.12)
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Build C library (2.14, >=2.5.0rc0,<2.15, libdeepmd_c_cu11.tar.gz)
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Build C++ (cuda, cuda)
  • GitHub Check: Test C++ (true)
  • GitHub Check: Test Python (1, 3.9)
  • GitHub Check: Build C++ (cpu, cpu)
  • GitHub Check: Analyze (c-cpp)
  • GitHub Check: Build C library (2.18, libdeepmd_c.tar.gz)
🔇 Additional comments (4)
deepmd/pt/utils/utils.py (1)

96-96: Excellent fix for dtype consistency in SiLUT function.

This change ensures the output tensor from silut_forward_script maintains the same data type as the input tensor x. This addresses the issue with torch.jit.script not preserving the bfloat16 data type, which is crucial for the mixed precision training feature being implemented.

deepmd/pt/train/wrapper.py (1)

139-139:

❓ Verification inconclusive

Good implementation of bfloat16 autocast for the forward method.

Adding the @torch.autocast decorator with bfloat16 precision should reduce memory usage by approximately 37% as mentioned in the PR objectives.

Since this feature is currently hardcoded to be enabled, it would be good to make it configurable as mentioned in the PR objectives:


🏁 Script executed:

#!/bin/bash
# Check if the GPU supports bfloat16
python -c "import torch; print(f'CUDA available: {torch.cuda.is_available()}'); print(f'Current device: {torch.cuda.get_device_name(0)}'); print(f'bfloat16 supported: {torch.cuda.is_bf16_supported()}')"

Length of output: 341


Make bfloat16 autocast configurable and verify GPU support manually

The @torch.autocast(device_type="cuda", dtype=torch.bfloat16, enabled=True) decorator is correctly applied, but since it’s hardcoded to enabled=True, we should make it driven by a configuration flag or function parameter as outlined in the PR objectives. Also, please confirm that your target GPU actually supports bfloat16 on CUDA.

Suggested changes:

  • Introduce a Boolean config or argument (e.g. use_bf16_autocast) to toggle the autocast decorator.
  • Apply the decorator conditionally, for example:
    if use_bf16_autocast:
        wrapper = torch.autocast(device_type="cuda", dtype=torch.bfloat16)
    else:
        wrapper = lambda fn: fn
    @wrapper
    def forward(...):
        ...
  • Manually verify bfloat16 support on your hardware:
    python - << 'EOF'
    import torch
    print("CUDA available:", torch.cuda.is_available())
    print("Device:", torch.cuda.get_device_name(0))
    print("bfloat16 supported:", torch.cuda.is_bf16_supported())
    EOF
  • Document the fallback behavior (e.g. float32) for platforms without bfloat16.
deepmd/pt/model/descriptor/repflow_layer.py (2)

427-432: Good dtype consistency improvement in tensor operations.

Explicitly casting the bias tensor to match the data type of sub_angle_update ensures consistent precision during arithmetic operations, which is essential for stable mixed precision training.


466-470: Good dtype consistency improvement in tensor operations.

Explicitly casting the bias tensor to match the data type of sub_node_update ensures consistent precision during arithmetic operations, which is essential for stable mixed precision training.

@codecov
Copy link

codecov bot commented May 15, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.69%. Comparing base (43e0288) to head (0a770e4).
⚠️ Report is 84 commits behind head on devel.

Additional details and impacted files
@@            Coverage Diff             @@
##            devel    #4741      +/-   ##
==========================================
- Coverage   84.69%   84.69%   -0.01%     
==========================================
  Files         697      697              
  Lines       67474    67477       +3     
  Branches     3540     3541       +1     
==========================================
  Hits        57147    57147              
  Misses       9197     9197              
- Partials     1130     1133       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@caic99
Copy link
Member Author

caic99 commented May 19, 2025

By setting model.descriptor.precision: "bfloat16", all the calculation process in descriptor is performed in bfloat16. The memory reduction is about 50%.
I'll test the performance gain with a larger batch size, which is available through the modifications of #4744.

@caic99 caic99 closed this May 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant