[codex] docs: expand Nemotron-Parse tuning guidance#2131
Open
lbliii wants to merge 2 commits into
Open
Conversation
Signed-off-by: Lawrence Lane <llane@nvidia.com>
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
engine_kwargstuning withgpu_memory_utilizationandmax_num_batched_tokensvllm.LLMPDFPartitioningStagefanout behavior with Ray Data and its relationship topdfs_per_taskTaskPerfUtilsaggregation exampleWhy
PR #2054 added vLLM engine passthrough, additive inference metrics, Ray Data fanout, and broader engine-startup retry handling. The published Nemotron-Parse guide described none of those behaviors, leaving users without a supported tuning or observability path.
User impact
Users can tune vLLM memory and batching, understand backend-specific metrics, measure throughput correctly under parallel execution, and diagnose retry exhaustion without masking non-retryable GPU or configuration errors.
Validation
npm run checkfromfern/: 0 errorsfern docs broken-links: no errors in the changed page; 22 existing errors remain in older API-reference pagesgit diff --checktest_stages.pyandtest_vllm_utils.pyCloses #2128
Parent tracking issue: #2118