Skip to content

Document scheduler memory fencing flags - #2242

Open
shawnwang18 wants to merge 1 commit into
mainfrom
agent/document-scheduler-memory-fencing
Open

Document scheduler memory fencing flags#2242
shawnwang18 wants to merge 1 commit into
mainfrom
agent/document-scheduler-memory-fencing

Conversation

@shawnwang18

Copy link
Copy Markdown

What changed

  • Document the experimental scheduler memory-fencing threshold flag.
  • Explain the threshold values and the optional slack-windows control.

Why

OpenXLA commit openxla/xla@26d6634 introduced scheduler memory fencing to limit peak memory when the latency-hiding scheduler keeps large buffers live by deferring their users.

Impact

JAX/XLA users can discover how to enable and tune the feature when latency-hiding scheduling causes excessive peak GPU memory use or OOMs.

Validation

  • Reviewed the rendered Markdown structure.
  • Ran git diff --check.

@copy-pr-bot

copy-pr-bot Bot commented Jul 29, 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.

@shawnwang18
shawnwang18 marked this pull request as ready for review July 29, 2026 01:07
@shawnwang18
shawnwang18 requested a review from instinct79 July 29, 2026 01:07
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