Skip to content

Stage 1 deprecation: remove user-facing static inference surface#4880

Open
shanmugamr1992 wants to merge 2 commits into
NVIDIA:mainfrom
shanmugamr1992:deprecate-static
Open

Stage 1 deprecation: remove user-facing static inference surface#4880
shanmugamr1992 wants to merge 2 commits into
NVIDIA:mainfrom
shanmugamr1992:deprecate-static

Conversation

@shanmugamr1992
Copy link
Copy Markdown
Contributor

Deletes the user-facing static-inference entry points in favor of the already-existing DynamicInferenceEngine, which subsumes both static and continuous-batching workloads. The shared StaticInferenceContext / InferenceParams param-bag is kept for the model code (T5, BERT, Mamba, LLaVA, hybrid, MTP, MLA, rotary/relative embeddings, SSM), which will be migrated in a separate follow-up.

Removed:

  • megatron/core/inference/engines/static_engine.py (StaticInferenceEngine)
  • megatron/core/inference/engines/mcore_engine.py (MCoreEngine alias)
  • megatron/core/inference/text_generation_server/{text_generation_server, run_mcore_engine,tokenization}.py and endpoints/ (legacy Flask server)
  • examples/inference/gpt/gpt_static_inference.py and its launcher
  • examples/inference/t5/simple_t5_batch_inference.py
  • tools/run_text_generation_server.py and hybrid wrappers
  • 9 static functional test directories (gpt/moe/hybrid) + 3 recipe YAMLs
  • tests/unit_tests/inference/engines/test_static_engine.py
  • tests/unit_tests/test_inference.py (legacy Flask server test)
  • 8 shell launcher scripts that invoked the deleted tools

Updated:

  • engines/init.py drops the StaticInferenceEngine re-export
  • tools/run_inference_performance_test.py: drop --engine-type static path
  • examples/multimodal/run_text_generation.py: --use-mcore-inference now raises NotImplementedError pointing at DynamicInferenceEngine
  • examples/inference/README.md, mixtral/README.md, mamba/README.md rewritten to point at gpt_dynamic_inference.py / tools/run_dynamic_text_generation_server.py

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.

For MRs into `dev` branch The proposed review process for `dev` branch is under active discussion.

MRs are mergable after one approval by either eharper@nvidia.com or zijiey@nvidia.com.

Deletes the user-facing static-inference entry points in favor of the
already-existing DynamicInferenceEngine, which subsumes both static and
continuous-batching workloads. The shared StaticInferenceContext /
InferenceParams param-bag is kept for the model code (T5, BERT, Mamba,
LLaVA, hybrid, MTP, MLA, rotary/relative embeddings, SSM), which will
be migrated in a separate follow-up.

Removed:
- megatron/core/inference/engines/static_engine.py (StaticInferenceEngine)
- megatron/core/inference/engines/mcore_engine.py (MCoreEngine alias)
- megatron/core/inference/text_generation_server/{text_generation_server,
  run_mcore_engine,tokenization}.py and endpoints/ (legacy Flask server)
- examples/inference/gpt/gpt_static_inference.py and its launcher
- examples/inference/t5/simple_t5_batch_inference.py
- tools/run_text_generation_server.py and hybrid wrappers
- 9 static functional test directories (gpt/moe/hybrid) + 3 recipe YAMLs
- tests/unit_tests/inference/engines/test_static_engine.py
- tests/unit_tests/test_inference.py (legacy Flask server test)
- 8 shell launcher scripts that invoked the deleted tools

Updated:
- engines/__init__.py drops the StaticInferenceEngine re-export
- tools/run_inference_performance_test.py: drop --engine-type static path
- examples/multimodal/run_text_generation.py: --use-mcore-inference now
  raises NotImplementedError pointing at DynamicInferenceEngine
- examples/inference/README.md, mixtral/README.md, mamba/README.md
  rewritten to point at gpt_dynamic_inference.py /
  tools/run_dynamic_text_generation_server.py

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@shanmugamr1992 shanmugamr1992 requested review from a team as code owners May 19, 2026 22:27
@copy-pr-bot
Copy link
Copy Markdown

copy-pr-bot Bot commented May 19, 2026

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.

@svcnvidia-nemo-ci svcnvidia-nemo-ci marked this pull request as draft May 19, 2026 22:27
@github-actions
Copy link
Copy Markdown
Contributor

This PR has been automatically converted to draft because all PRs must start as drafts.

When you are ready for review, click Ready for Review to begin the review process. This will:

  1. Add the oncall reviewer (optional reviewer)
  2. Add required review teams based on your changes

See the contribution guide for more details.

@shanmugamr1992 shanmugamr1992 marked this pull request as ready for review May 19, 2026 22:28
@svcnvidia-nemo-ci svcnvidia-nemo-ci requested a review from a team May 19, 2026 22:28
…te-static

# Conflicts:
#	tests/functional_tests/test_cases/moe/gpt_static_inference_cuda_graphs_pad_tp4_pp1_ep4_16B_logitsmatch/model_config.yaml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants