NVIDIA-NeMo / NVIDIA-NeMo/DataDesigner

Support Scaling Data Designer on SLURM

Open
#160 0 comments 0 reactions 2 assignees View on GitHub

@eric-tramel is already working on this.

Since Dec 24, 2025.

enhancement in-progress on-roadmap
Dominant language
Python
Stars
2.3k
Forks
211
Avg merge
2d 6h
Merged PRs (30d)
40

Description

When Data Designer is used on a SLURM-managed GPU cluster, it should be able to automatically manage model servers required to run generation and preview jobs.

What this feature should do

  • Automatically spin up and tear down model servers on SLURM
  • Launch model servers (e.g. via vLLM) as SLURM jobs when needed.
  • Shut them down when they are no longer in use.

Support interactive preview workflows

  • Allow users to interactively query models for Data Designer preview jobs.
  • Support streaming responses.
  • Keep model servers alive for the duration of an interactive session, then clean them up.

Support large-scale batch generation

  • Scale model servers up and down to efficiently execute Data Designer jobs.
  • Execute work within a user-defined GPU budget for the job.
  • Users explicitly specify how many GPUs they are making available to a Data Designer job.
  • Data Designer uses only those GPUs and does not require manual placement or provisioning.

Data Designer determines how to:

  • Split work across models.
  • Scale model replicas.
  • Assign GPUs to each model instance.
  • Provide a simple user-facing configuration

Users specify:

  • Which models they want to use.
  • The total number of GPUs available to the job (and optionally per-model GPU needs).
  • Data Designer handles model lifecycle, scaling, and GPU utilization automatically.

Outcome

From the user’s perspective, running Data Designer on SLURM should require no manual model orchestration. Users declare their model needs and GPU budget, and Data Designer automatically provisions, scales, and cleans up model servers within those constraints.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.