Skip to content

Document new GPU brokerage filters: vram, architecture, CUDA version#77

Open
EdwardKaravakis wants to merge 4 commits into
mainfrom
feat/gpu-brokerage-new-filters
Open

Document new GPU brokerage filters: vram, architecture, CUDA version#77
EdwardKaravakis wants to merge 4 commits into
mainfrom
feat/gpu-brokerage-new-filters

Conversation

@EdwardKaravakis
Copy link
Copy Markdown
Member

Summary

Updates the GPU hardware check section of the brokerage documentation to reflect the new two-stage logic introduced in panda-server PR #714 (ATLASPANDA-1684):

  • Describes CRIC as the GPU capability gate (queue must have a gpu entry)
  • Describes worker node GPU monitoring (MV_WORKER_NODE_GPU_SUMMARY) as the source for all attribute checks
  • Documents three new gpu_spec fields:
    • vram — minimum GPU memory in MB (e.g. 40960 for 40 GB)
    • architecture — GPU microarchitecture generation or list (e.g. "Ampere" or ["Ampere", "Hopper"])
    • version — minimum CUDA version (e.g. >=12.0)
  • Removes the old statement about CRIC-only model matching and queues being skipped when model info is absent from CRIC

Related PRs

  • panda-server #714 (brokerage logic)
  • panda-database #132 (MV schema)
  • panda-client (companion PR for --architecture help text)

Update the GPU hardware check section to reflect the new two-stage
brokerage logic (ATLASPANDA-1684):
- CRIC as GPU capability gate
- WN GPU monitoring as source for all attribute checks
- New gpu_spec fields: vram (min VRAM in MB), architecture (microarch
  generation), version (min CUDA version)
Add driver_version (NVIDIA kernel driver minimum version) to the gpu_spec
parameter table and the two-stage attribute matching description.
Add shorthand attribute table (vram, cuda, uarch, driver, model keys),
ART header examples, and JSON prun examples. Update vram description
to show operator-prefixed string format consistent with other attributes.
@EdwardKaravakis EdwardKaravakis marked this pull request as ready for review May 11, 2026 13:49
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