Skip to content

Add InferenceConfigContainer and InferenceSetupConfig for arg-free init#2

Open
shanmugamr1992 wants to merge 1 commit into
remove_legacy_builder-train-refactorfrom
inference_container_config
Open

Add InferenceConfigContainer and InferenceSetupConfig for arg-free init#2
shanmugamr1992 wants to merge 1 commit into
remove_legacy_builder-train-refactorfrom
inference_container_config

Conversation

@shanmugamr1992

Copy link
Copy Markdown
Owner

Introduce a declarative, serializable InferenceSetupConfig (mirroring the inference argparse group) and an InferenceConfigContainer so inference entry points can drive the refactored initialize_megatron() without constructing a training-shaped PretrainConfigContainer.

  • Add InferenceSetupConfig (megatron/training/config/inference_config.py) with a to_inference_config() mapper that produces the runtime megatron.core.inference.config.InferenceConfig from the built model.

  • Add InferenceConfigContainer holding only inference-relevant configs.

  • Add inference_cfg_from_args() / inference_cfg_container_from_args() helpers.

  • Make get_inference_config_from_model_and_args() delegate to the mapper so the declarative config is the single source of truth.

  • I, the PR author, have personally reviewed every line of this PR.

What does this PR do ?

⚠️ 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

  • I have added relevant unit tests
  • I have added relevant functional tests
  • I have added proper typing to my code Typing guidelines
  • 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.

Introduce a declarative, serializable InferenceSetupConfig (mirroring the
inference argparse group) and an InferenceConfigContainer so inference entry
points can drive the refactored initialize_megatron() without constructing a
training-shaped PretrainConfigContainer.

- Add InferenceSetupConfig (megatron/training/config/inference_config.py) with a
  to_inference_config() mapper that produces the runtime
  megatron.core.inference.config.InferenceConfig from the built model.
- Add InferenceConfigContainer holding only inference-relevant configs.
- Add inference_cfg_from_args() / inference_cfg_container_from_args() helpers.
- Make get_inference_config_from_model_and_args() delegate to the mapper so the
  declarative config is the single source of truth.

@maanug-nv maanug-nv left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

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.

2 participants