Skip to content
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

Add performance-optimized example for llama2 70b LoRA #12055

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

vysarge
Copy link
Collaborator

@vysarge vysarge commented Feb 5, 2025

What does this PR do ?

This PR adds an example script for llama2 70b LoRA tuning (tp4pp1cp1 on H100) including optimized configs used in MLPerf 4.1 submission, plus supporting changes.

Collection: llm

Changelog

  • Added example script scripts/llm/performance/mlperf_lora_llama2_70b.py
  • Enabled use of atomic GEMM settings for TP overlap
  • Added a custom datamodule for downloading MLPerf-processed govreport data from HF
  • Added a wrapper around LlamaModel which wraps configure_model to reduce memory consumption

Usage

  • You can potentially add a usage example below
python scripts/llm/performance/mlperf_lora_llama2_70b.py --help

GitHub Actions CI

The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.

The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".

Before your PR is "Ready for review"

Pre checks:

  • Make sure you read and followed Contributor guidelines
  • Did you write any new necessary tests?
  • Did you add or update any necessary documentation?
  • Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
    • Reviewer: Does the PR have correct import guards for all optional libraries?

PR Type:

  • New Feature
  • Bugfix
  • Documentation

If you haven't finished some of the above items you can still open "Draft" PR.

Who can review?

Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.

Additional Information

  • Related to # (issue)

…ludes te's fp8_model_init and torch no_grad, update TE overlap configs to allow atomic gemm + empty entries

Signed-off-by: Valerie Sarge <[email protected]>
@vysarge vysarge force-pushed the vsarge/lora_recipe_perf branch from b01cbc9 to 3b9525a Compare February 5, 2025 00:55
Comment on lines +250 to +252
self.tp_comm_overlap_cfg = {
key: value for key, value in self.tp_comm_overlap_cfg.items() if value is not None
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we need to have this given row 249?

Comment on lines +271 to +281
"LORA_A2A": "1",
"CUDA_DEVICE_MAX_CONNECTIONS": "1",
"CUBLAS_FORCE_XMMA_KERNEL_INIT": "DEVICE",
"CUDNN_FRONTEND_ATTN_DP_WORKSPACE_LIMIT": "0",
"NVTE_FP8_DPA_BWD": "1",
"NVTE_RS_STRIDED_ATOMIC": "2",
"NCCL_MIN_CTAS": "32",
"NCCL_MIN_P2P_NCHANNELS": "32",
"NCCL_NCHANNELS_PER_NET_PEER": "32",
"NCCL_NVLS_ENABLE": "0",
"TORCH_NCCL_AVOID_RECORD_STREAMS": "1",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you add description on the env vars?

Please refer this PR.
#11991

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.

2 participants