Skip to content

[DO NOT MERGE] H100 hang: candidate fix C2, no managed memory in k-means/IVF-PQ training (workstream B4) - #2823

Closed
bdice wants to merge 4 commits into
NVIDIA:mainfrom
bdice:b4-verify-c2
Closed

bdice wants to merge 4 commits into
NVIDIA:mainfrom
bdice:b4-verify-c2

Conversation

@bdice

@bdice bdice commented Oct 11, 2026

Copy link
Copy Markdown
Contributor

Workstream B4 (#2783). Candidate fix C2: balanced k-means (build_hierarchical/build_fine_clusters) and IVF-PQ train_per_cluster use device memory plus explicit host copies instead of managed memory. Same CI config as #2816/#2817, with 2x H100 12.9.2. Do not merge.

bdice added 4 commits October 10, 2026 22:44
…VF-PQ training

build_hierarchical, build_fine_clusters and IVF-PQ train_per_cluster used
managed memory for small arrays that are read or written on the host
(mesocluster labels and sizes, per-mesocluster row ids, cluster sizes and
offsets). Allocate them from the workspace resource and copy them to or from
host vectors explicitly, with a stream sync before the host reads them.
This removes the managed allocations and the CPU/GPU page migrations they
cause on every balanced k-means fit and IVF-PQ build.
@copy-pr-bot

copy-pr-bot Bot commented Oct 11, 2026

Copy link
Copy Markdown

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@bdice

bdice commented Oct 11, 2026

Copy link
Copy Markdown
Contributor Author

/ok to test caab490

@bdice

bdice commented Oct 11, 2026

Copy link
Copy Markdown
Contributor Author

Closing: this was a diagnostic PR for the H100 hang (workstream B of #2783). The root cause (pageable host memory treated as device memory on HMM systems) is fixed in #2829.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant