Skip to content

Remove torch cuda empty cache#5678

Draft
shurkat-nvidia wants to merge 2 commits into
NVIDIA:mainfrom
shurkat-nvidia:remove-torch-cuda-empty-cache
Draft

Remove torch cuda empty cache#5678
shurkat-nvidia wants to merge 2 commits into
NVIDIA:mainfrom
shurkat-nvidia:remove-torch-cuda-empty-cache

Conversation

@shurkat-nvidia

Copy link
Copy Markdown
Contributor
  • I, the PR author, have personally reviewed every line of this PR. (I have written every line of this PR.)

What does this PR do?

The PR removes an expensive torch.cuda.empty_cache() call within save_checkpoint_and_time(). This call took multiple seconds on every checkpoint and also increased the size of the generate_state_dict() function by multiple seconds. To avoid OOM errors, the code also modifies the Nemotron3 Super script to 1) use SHM to avoid expensive rebuild_cuda_tensor() calls during the IPC handoff and 2) garbage collect the torch allocator at 80% GPU allocation with a lower overhead than a raw empty_cache() call, and to use larger blocks to prevent fragmentation in the first place.

⚠️ For major changes (either in lines of code or in its impact), please make sure to first share a design doc with the team. If you're unsure what's the best way to do so, contact @NVIDIA/mcore-oncall.

Issue tracking

For PRs from open-source community contributors:

  • New features: a linked issue is required. Please open a feature request and reference it here before submitting the PR.
  • Small updates (bug fixes, minor improvements): a linked issue is recommended and will accelerate the PR review process.

Linked issue:

Contribution process

Pre-checks

  • (N/A) I have added relevant unit tests
  • (N/A) I have added relevant functional tests
  • (N/A) I have added proper typing to my code Typing guidelines
  • (N/A) I have added relevant documentation
  • I have run the autoformatter.sh on my PR

Code review

Feel free to message or comment @NVIDIA/mcore-oncall to help accelerate your merge into main. The less complex your PR is, the faster it will be approved and merged!

All PRs start as draft. If you open a non-draft PR, it will be automatically converted to draft.

Step 1: Mark PR as "Ready for Review"

  1. When your PR is ready, click Ready for Review.
  2. An oncall reviewer is auto-assigned and expert reviewers are notified based on your changes.
    • Some PRs may jump straight to step 2. This is determined by .github/CODEOWNERS.

⚠️ Only mark as ready once merge-conflicts are resolved and the CI is passing.
Final Review might get declined if these requirements are not fulfilled.

Step 2: Final Review

For PRs that change megatron/core, once all expert reviewers have approved, the Final Review label is applied automatically and final reviewers are assigned.

For PRs outside megatron/core, this step is skipped.

Step 3: Approved

Once all required reviewers have approved, the Approved label is applied automatically.

Merge

Any member of mcore-engineers will be able to merge your PR.

@copy-pr-bot

copy-pr-bot Bot commented Jul 6, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@shurkat-nvidia shurkat-nvidia force-pushed the remove-torch-cuda-empty-cache branch from adbf098 to ddbde1f Compare July 6, 2026 18:01
torch.cuda.empty_cache() was added as a workaround for out-of-memory
errors on some models. With async-shm checkpointing, some of the memory
pressure is reduced. Remaining memory fragmentation and pressure can be
reduced by properly configuring the torch allocator.

Signed-off-by: Skand Hurkat <shurkat@nvidia.com>
 - Update checkpointing to use nvrx with shm.

 - Provide PYTORCH_ALLOC_CONF environment variable to initiate garbage
   collection. Use larger blocks to avoid fragmentation due to
   splitting.

Signed-off-by: Skand Hurkat <shurkat@nvidia.com>
@shurkat-nvidia shurkat-nvidia force-pushed the remove-torch-cuda-empty-cache branch from ddbde1f to da16039 Compare July 6, 2026 18:54
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.

1 participant